Skip to content

Verify access

Complete these checks after networking, DNS, certificates, and the administrator password have been configured.

Use the Elasticsearch and Kibana hostnames provided for your deployment.

Before you begin

Make sure:

  • network access is configured;
  • DNS resolves correctly;
  • TLS certificates are configured when required;
  • the Elasticsearch administrator password has been reset;
  • you are testing from a network that is allowed to access the platform.

1. Verify DNS

Resolve each service hostname.

nslookup <service-hostname>

For public access, confirm the hostname resolves to the expected public platform endpoint.

For private access, confirm it resolves to the Private Endpoint private IP address.

2. Verify HTTPS connectivity

Confirm that the service hostname is reachable on HTTPS.

nc -vz <service-hostname> 443

A successful connection confirms that the network path to the endpoint is available.

3. Verify TLS

Test the certificate using the exact service hostname.

SERVICE_HOSTNAME="<service-hostname>"

openssl s_client \
  -connect "${SERVICE_HOSTNAME}:443" \
  -servername "${SERVICE_HOSTNAME}" \
  -verify_return_error </dev/null

Confirm the result includes:

Verify return code: 0 (ok)

Do not disable certificate verification to bypass a TLS error.

4. Verify Elasticsearch

Connect to the Elasticsearch endpoint.

curl --fail-with-body --user "<administrator-user>" \
  "https://<elasticsearch-hostname>/"

Enter the password when prompted.

A successful request returns the Elasticsearch product response.

5. Verify Kibana

Open the Kibana URL provided for the deployment in a browser.

Confirm that:

  1. the page loads without a DNS or certificate error;
  2. the Kibana sign-in page appears;
  3. you can sign in with an authorized account;
  4. Kibana loads successfully after authentication.

6. Verify Fleet when used

If your deployment uses Elastic Agent or Fleet, open the Fleet endpoint or Fleet interface and confirm it is reachable using the hostname provided for the deployment.

Detailed agent onboarding is covered under platform operations and data onboarding.

If verification fails

Use the failed step to identify where to troubleshoot:

Failure Check
Hostname does not resolve DNS configuration
Hostname resolves to wrong address DNS configuration
Port 443 cannot be reached Network path, firewall, routing, or Private Endpoint
Certificate validation fails TLS certificate, hostname, or certificate trust
Elasticsearch returns authentication error Username or password
Kibana loads but sign-in fails User authentication or permissions

For additional assistance:

  • AI chat: https://copilot.ivedha.cloud
  • Support portal: https://support.ivedha.com/

Provide the deployment reference from your Your deployment is ready notification.

Platform ready for use

When these checks succeed, the initial deployment and access configuration are complete.

Next step

Continue to the operations overview to configure access, onboard data, monitor capacity, and manage the platform.