Connection & Setup

Learn how to connect ElasticDoctor to your Elasticsearch cluster across all supported versions

SSL Connection Notice

ElasticDoctor always connects to your Elasticsearch cluster without SSL certificate verification. This means SSL certificates are not validated during connection, allowing connections to clusters with self-signed certificates or custom certificate authorities.

What this means:

  • • Connections work with self-signed certificates
  • • No need to upload CA certificates
  • • SSL/TLS encryption is still used when you specify HTTPS
  • • Certificate hostname and validity are not verified

Supported Elasticsearch Versions

ES 5.x

Fully Supported

ES 6.x

Fully Supported

ES 7.x

Fully Supported

ES 8.x

Fully Supported

ES 9.x

Fully Supported

Auto-Detection

ElasticDoctor automatically detects your Elasticsearch version and uses the appropriate client library for optimal compatibility.

Connection Methods

Basic HTTP Connection

Connect to your Elasticsearch cluster using HTTP protocol (recommended for development).

Host: http://localhost:9200
Port: 9200
Protocol: HTTP

HTTPS Connection

Secure connection using HTTPS protocol. SSL certificate verification is disabled by default.

Host: https://your-cluster.com:9200
Port: 9200
Protocol: HTTPS
Verify SSL: false (always disabled)

Cloud Providers

Connect to managed Elasticsearch services from major cloud providers.

AWS Elasticsearch

Use your AWS domain endpoint with IAM authentication

Elastic Cloud

Connect using your cloud deployment URL

Google Cloud

Use GCP Elasticsearch service endpoint

Authentication Methods

Username & Password

Basic authentication using username and password credentials.

Security Note

Only read-only permissions are required. ElasticDoctor never modifies your cluster.

API Key Authentication

Enhanced security using Elasticsearch API keys (recommended for production).

Recommended

API keys provide fine-grained access control and can be easily revoked.

CA Certificate (Not Used)

CA certificates are not required since ElasticDoctor always connects without SSL certificate verification.

Certificate upload is disabled as SSL verification is not performed

Testing Your Connection

Before running a full diagnosis, ElasticDoctor tests your connection to ensure everything is configured correctly.

1

Connection Validation

Verifies that ElasticDoctor can reach your cluster

2

Authentication Check

Confirms that your credentials are valid

3

Version Detection

Automatically detects your Elasticsearch version

4

Permissions Validation

Ensures read access to necessary cluster information

Common Connection Issues

Connection Refused

Unable to connect to the Elasticsearch cluster.

Common Causes:

  • • Incorrect host or port
  • • Firewall blocking connections
  • • Elasticsearch service not running
  • • Network connectivity issues

Authentication Failed

Invalid credentials or insufficient permissions.

Common Causes:

  • • Incorrect username or password
  • • Expired API key
  • • Insufficient read permissions
  • • Certificate issues

SSL Certificate Error

Issues with SSL/TLS certificate validation.

Common Causes:

  • • Self-signed certificates
  • • Certificate authority not trusted
  • • Hostname mismatch
  • • Expired certificates

Next Steps

Run Your First Diagnosis

Now that you understand connections, try diagnosing your cluster

Start Diagnosis

Learn About Health Checks

Understand what ElasticDoctor checks in your cluster

View Health Checks

Still Having Connection Issues?

Our support team can help you troubleshoot connection problems and get you up and running quickly.

Contact SupportBest Practices Guide