Cloud Onboarding

Stand up access to an Elastic Cloud organization end to end: configure the elastic CLI so it can operate the control plane, then manage identity and access, invite users, assign predefined or custom roles to Serverless projects, and manage Cloud API keys. For creating and operating projects and deployments, use the cloud-provisioning skill.

Environment Configuration

This skill configures the elastic CLI itself, so its setup lives here rather than being assumed. If the elastic CLI is not installed, tell the user what it is needed for.

Cloud control-plane access is authenticated by an Elastic Cloud API key (organization scope), stored in a CLI context. Register it without ever having the user paste the secret into the chat:

• Only Organization owners can create Cloud API keys. Direct the user to generate one at Elastic Cloud API keys with Project Admin privileges or higher so it can manage serverless projects.
• If the user has no Elastic Cloud account, propose the free Elastic Cloud trial (14 days, no credit card). Once registered, continue with key generation.
• Add the key to a context (the secret is stored in the OS keychain, not echoed): elastic config context add cloud --cloud-url https://api.elastic-cloud.com --cloud-api-key <KEY>, then make it active with elastic config current-context set cloud.

Do not guess credentials, bypass the CLI to call the HTTP API directly, or ask the user to reveal the key. This skill references control-plane operations in HTTP-shorthand form with the cloud: prefix (for example, GET cloud:/api/v1/organizations); the Operations table maps each to the equivalent elastic cloud command.