Create an Amazon ES Public Domain

Amazon Es

Amazon Elasticsearch Service is a managed service that makes it easy to deploy, operate, and scale Elasticsearch in the AWS Cloud. Elasticsearch is a popular open-source search and analytics engine for use cases such as log analytics, real-time application monitoring, and clickstream analytics.

There are some basic steps to create ElasticSearch public domain in AWS which all are given below:-

Step 1:- Sign In

SignIn your AWS account.

Step 2:- Serch Service

Search Elasticsearch Service in the Find service tab then select it.

Find Service

Step 3:- Create a new domain

After selecting the Elasticsearch service, You will see this Amazon Elasticsearch Service dashboard then you will click on Create a new domain button.

step 4:- On the Create Elasticsearch domain page, choose Development and testing.

Deployment type

Step 5:- For the Elasticsearch version, choose the latest version and Next.

Select version

Step 6:- Enter a name for the domain. In this article, we use the domain name testarticle for the examples that we provide later in the article.

Domain name

Step 7:- For Data nodes, choose the t2.small.elasticsearch instance type. Use the default value of 1 instance.

Data Node

Step 8:- For Data nodes storage, use the default values.

Data node storage

Step 9:- For now, you can ignore the Dedicated master nodes, UltraWarm data nodes, Snapshot configuration, and Optional Elasticsearch cluster settings sections.

Master node

Step 10:- Select Next Button.

Next Button

Step 11:- For simplicity in this tutorial, we recommend a public access domain. For Network configuration, choose Public access.

Network Configuration

Step 12:- For Fine-grained access control, choose Create master user. Specify a username and password. But Now we ignore it because we are creating the public domain.

Fine-grained access control

Step 13:- For now, you can ignore Amazon Cognito Authentication.

Amazon Cognito Authentication

Step 14:- For Access policy, choose Custom access policy.

Access Policy

Step 15:- Leave the encryption settings at their default values, and choose Next.

Encryption

Step 16:- On the Review page, double-check your configuration and choose Confirm. New domains typically take 15–30 minutes to initialize but can take longer depending on the configuration. After your domain initializes, make note of its endpoint.

After confirming looks like this.

Successful

After Activation

Endpoint

Now, We will check our connectivity is proper established or not. So now will click on the Kibana link. If it’s open proper then it’s properly connected otherwise it’s not.

I am getting an error like this.

This error means permissions are not properly set. So we will change the policy.

Click on Actions then select modify access policy.

After clicking you will see this window.

Replace the policy then save it again.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "es:*",
      "Resource": "arn:aws:es:ap-south-1:1199126912345:domain/testarticle/*"
    }
  ]
}

After submit it will take some time for preparation. After some when it will be active then we will click again on the Kibana URL.

This time you will see that Kibana has been opened means our setup is ready for development.

That’s it for this time! I hope you enjoyed this post. As always, I welcome questions, notes, comments and requests for posts on topics you’d like to read. See you next time! Happy Coding !!!!!