Agent skill · elastic
cloud-provisioning
Provision and operate Elastic Cloud infrastructure: create, connect to, update, and delete Serverless projects (Elasticsearch, Observability, Security); manage traffic filters (IP and AWS PrivateLink network security); and manage the lifecycle of Elastic Cloud Hosted deployments. Use when creating or performing day-2 operations on serverless projects or hosted deployments, or restricting their network access.
What it needs
About 9k tokens when loaded.
What this skill does
Cloud Provisioning Provision and run Elastic Cloud infrastructure through the Cloud API: Serverless projects (create and day-2 operations), traffic filters (network security for those projects), and Elastic Cloud Hosted deployments. For configuring Cloud authentication and managing organization access, use the cloud-onboarding skill. <!-- begin-partial: cloud-preamble --> Environment Configuration This skill operates the Elastic Cloud control plane through the elastic CLI. If the elastic CLI is not installed, tell the user what it is needed for. Do not guess credentials, bypass the CLI to call the HTTP API directly, or attempt other workarounds. Control-plane operations authenticate against the Elastic Cloud API (organization scope), not a single stack deployment. The elastic CLI reads this from its active context, which stores an Elastic Cloud API key in the OS keychain. If a control-plane call fails with an authentication error, the context is missing or lacks a Cloud API key — instruct the user to add one, and never ask the user to paste an API key into the chat: "Configure an Elastic Cloud context for the elastic CLI, then re-run. Generate an Organization-level key at Elastic Cloud API keys and register it without echoing the secret in chat." This skill references control-plane operations in HTTP-shorthand form with the cloud: prefix (e.g., GET cloud:/api/v1/organizations, POST cloud:/api/v1/serverless/projects/elasticsearch). The Operations table at the end of this document maps each shorthand to the equivalent elastic cloud command — always use the CLI rather than calling the HTTP API directly. Discover the organization ID from GET cloud:/api/v1/organizations; do not ask the user for it. <!-- end-partial: cloud-preamble --> Critical principles Never display secrets in chat. Do not echo, log, or repeat passwords or API keys in conversation or agent thinking. Persist credentials into a CLI context (OS keychain) and direct the user there. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills elastic/provisioning--584ef5