Skip to content
AdminKit

Elasticsearch HTTP API

What is Elasticsearch HTTP API?

Elasticsearch exposes its search and cluster-administration functions through a JSON-over-HTTP API, by default on port 9200, Elastic's own documented default rather than an IANA-assigned port. Versions before 8.0 shipped with security disabled unless configured, which is why AdminKit's guide checks whether your own port 9200 is reachable without authentication.

By AdminKit team, Netbase JSC · Updated

Elasticsearch exposes its search, indexing and cluster-administration functionality through a RESTful HTTP API rather than a binary wire protocol — every request and response is plain JSON over HTTP, normally on port 9200, Elastic’s own documented default rather than an IANA-assigned port — IANA’s own port registry lists TCP/UDP 9200 as assigned to the long-obsolete WAP connectionless session service, not Elasticsearch, confirming the default is Elastic’s choice alone. Requests use the ordinary HTTP methods RFC 9110 defines — GET to search or read, PUT and POST to index, DELETE to remove a document or an entire index — so any HTTP client, down to a plain curl command, can drive a cluster it can reach. MDN’s reference on HTTP request methods summarizes those shared semantics, for example that a GET request should only retrieve data, which is why a single unauthenticated GET against an exposed cluster is enough to read from it. Before version 8.0, Elastic’s security features (authentication, role-based access control, TLS) were part of a separate tier and disabled by default, so a freshly started node answered any HTTP request on that port with no credential required at all. Elastic’s current security documentation describes self-managed clusters now configuring security automatically where possible, closing much of that earlier gap for new deployments. The ongoing risk is almost entirely inherited: clusters deployed on an older version, or ones where security was manually disabled during setup for convenience, that were never revisited — which is how researchers keep finding large, completely open Elasticsearch indices.

Elasticsearch’s history of open, unauthenticated instances mirrors other database wire protocols AdminKit tracks, like the MongoDB wire protocol and Redis protected mode, each of which shipped with weak defaults of its own.

AdminKit groups elasticsearch HTTP API under its machine protocols cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What port does the Elasticsearch HTTP API use by default?

Port 9200, a default Elastic documents itself rather than an IANA-assigned port, so an operator can change it freely.

Why were pre-8.0 Elasticsearch clusters often publicly exposed with no authentication?

Elastic's security features -- authentication, role-based access control, TLS -- were part of a separate tier that shipped disabled by default, so a freshly started node answered any HTTP request on that port with no credential required.

Does upgrading past Elasticsearch 8.0 automatically secure an existing cluster?

Not on its own -- new installs now configure security automatically where possible, but the ongoing risk is largely inherited from older or manually reconfigured clusters that were never revisited.