Skip to content

Sign in securely

Use only the URLs shown in deployment details. Complete networking, DNS, and TLS configuration before entering credentials.

First sign-in

  1. Open the Kibana URL by hostname.
  2. Confirm that the browser reports a valid certificate for that hostname.
  3. Obtain initial access through the approved credential or password-reset action exposed by the managed application. Do not request a password in email or chat.
  4. Sign in and confirm that Kibana loads without a certificate, redirect, or authorization error.
  5. Create or map named administrator accounts.
  6. Store recovery credentials in an approved secrets system and stop using a shared bootstrap account for daily work.

Elasticsearch client access

Use HTTPS and an individual user, API key, or other approved authentication method. Do not place secrets in source files or shell history.

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

Enter the password through the client prompt or an approved secret mechanism.

The built-in elastic user is a superuser and should be reserved for tasks that require full cluster access. Elastic recommends creating users with the minimum required privileges. See built-in users in self-managed clusters.

Continue with manage users and roles and ingest your first data.