AWS Elasticsearch on private internal IP

Within AWS Elasticsearch service, i've created a new domain and set the defaults for creating a new elastic search + kibana service.

When choosing the subnet, i chose the subnet that is our internal zone.

Elasticsearch creates a URL to access Kibana, which when i try to open, doesn't open as the site cannot be accessed. AWS Elasticsearch provides a URL like this:

I'm am within my organisation and i cannot access this URL.

If i create an EC2 and install kibana and elasticsearch and put it in the same internal zone and subnet, i can access because i have a private IP.

How can i solve this problem?

Welcome !

We don't support here this service. You need to ask in AWS forums.

If you want to run the official elastic services on AWS have a look at and ?

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, APM, Logs UI, Infra UI, SIEM, Maps UI and what is coming next :slight_smile: ...

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.