bolt-spin

You can provision a disposable Elastic deployment by choosing Serverless, Elastic Cloud Hosted, or Docker as the target, then running the tool to automatically generate a per-engagement cluster with isolated credentials written to a local .env file.

The best way to isolate demo data is to provision per-engagement credentials and endpoints for each run, which prevents cross-demo data leakage. You can also reuse existing deployments or clone environments to run multiple demos in a shared cluster while preserving isolation.

Yes, you can use Docker to provision a local Elastic environment instead of Elastic Cloud Hosted. The tool supports Serverless, Elastic Cloud Hosted, and Docker-based local environments, allowing you to choose the target that best fits your demo infrastructure.

To validate connectivity and check cluster health, the provisioning process automatically produces a provision log. This log records the cluster health status, endpoints, and provisioning details, ensuring the deployment is fully operational and documented.

Yes, provisioning a demo cluster generates per-engagement credentials. These credentials, along with the necessary endpoints, are written directly to a per-engagement .env file in the workspace to ensure each demo remains isolated and accessible.

You should not use a disposable Elastic deployment for persistent production workloads, as it is designed specifically for temporary demos. The tool ensures isolation and produces a provision log for temporary engagements rather than supporting long-term data retention.