Skip to content

Deploy your first platform instance

This tutorial follows one non-production example from Marketplace selection to a searchable test document. Replace the fictional values with values approved for your organization.

Example choices

Decision Fictional tutorial value
Application resource group rg-docs-elastic-demo
Workload profile Observability
Capacity Small
Topology All-in-one
Machine learning Disabled
Access Public, only when organizational policy permits
Public domain Marketplace-assigned default
Maintenance window Approved non-business window

The example names are not deployment defaults or recommendations. Use private access instead when internet-reachable endpoints are not approved.

Before you begin

You need:

  • an approved Marketplace offer and plan;
  • purchasing, deployment, role-assignment, policy, and quota prerequisites;
  • an application resource-group name and approved Azure region;
  • a named network, identity, certificate, data, and support owner;
  • permission to create a disposable synthetic test index.

Complete Marketplace prerequisites and the planning worksheet first.

Create the managed application

  1. In the Azure portal, open the approved Marketplace offer.
  2. Confirm the publisher is iVedha and the product is iVedha Managed Elasticsearch Platform.
  3. Select the approved plan, then select Create.
  4. On Basics, select the approved subscription, resource group, and region.

  5. Enter an application name that follows your Azure naming policy.

  6. On the deployment profile step, select the approved workload, capacity, topology, and optional ML setting. For this example, use the choices in the preceding table.

  7. Configure the approved private domain. Enable public access only when the security owner approved it. If a custom public domain is enabled, record its DNS owner.

  8. Enter the approved maintenance occurrence, day, start time, time zone, and duration.

  9. Enter the approved support contact.

  10. On Review + create, resolve every validation error and review the configuration, price, terms, permissions, and managed-resource-group settings.

  11. Select Create once the review is correct.

Follow the readiness gates

Do not treat Azure acceptance as service readiness:

  1. Wait for Azure to accept the Marketplace request.
  2. Confirm the ARM deployment reports Succeeded.
  3. Open the managed application and wait for its managed reconciliation and health indicators to complete.
  4. Confirm that the Elasticsearch and Kibana URLs appear in the authoritative deployment details.
  5. Complete public or private connectivity, DNS, and TLS.
  6. Open Kibana and confirm an approved user can sign in.

Use follow deployment status for the meaning of each gate and navigate the managed application for the relevant Azure views.

Verify with synthetic data

After connectivity and authentication work:

  1. Follow ingest your first data.
  2. Confirm the document is returned by search.
  3. Open Kibana and confirm the data is visible.
  4. Delete the synthetic index.

The instance is ready for handover only after these checks succeed from an approved customer network.

Clean up the tutorial instance

If the instance is temporary, follow delete the application. Confirm required snapshots, audit records, DNS cleanup, and data-retention decisions before deletion.