cloud-setup
Configures Elastic Cloud authentication and environment defaults. Use when setting up ECAPIKEY, configuring Cloud API access, or when another cloud skill requires credentials.
- Installs
- 2.7K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/elastic/agent-skills --skill cloud-setup- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cloud-setup automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Cloud Environment Setup
Configure Elastic Cloud authentication and preferences. All other cloud/* skills depend on this setup.
Workflow
Setup Progress:
- [ ] Step 1: Verify API key
- [ ] Step 2: Set defaults
- [ ] Step 3: Validate connection
Step 1: Verify API key
Check whether EC_API_KEY is already set:
echo "${EC_API_KEY:?Not set}"
If not set, instruct the user to set it. Never ask the user to paste an API key into the chat — secrets must not appear in conversation history.
If the user indicates they do not have an Elastic Cloud account yet, propose starting a free trial at Elastic Cloud free trial. The trial provides 14 days of full access to Elastic Cloud Serverless with no credit card required. Once the user has registered and logged in, proceed with API key generation below.
Direct the user to:
- Generate a key at Elastic Cloud API keys. Only Organization owners can create and manage Cloud API keys.
- When creating this key, include Project Admin privileges or higher (Org Owner) so it can create and manage serverless projects.
- Create a
.envfile in the project root (recommended — works in sandboxed agent shells):
EC_API_KEY=your-api-key
All cloud/* scripts auto-load .env from the working directory — no manual sourcing needed.
Alternatively, export directly in the terminal:
export EC_API_KEY="your-api-key"
Terminal exports might not be visible to sandboxed agents running in a separate shell session. Prefer the .env file
when working with an agent.
Remind the user that storing secrets in local files is acceptable for development, but for production or shared environments, use a centralized secrets manager (for example, HashiCorp Vault, AWS Secrets Manager, 1Password CLI) to avoid secrets sprawl.
Step 2: Set defaults
Export the base URL and default region:
export EC_BASE_URL="https://api.elastic-cloud.com"
export EC_REGION="gcp-us-central1"
Ask the user if they want a different region. To list available regions:
curl -s -H "Authorization: ApiKey ${EC_API_KEY}" \
"${EC_BASE_URL}/api/v1/serverless/regions" | python3 -m json.tool
Step 3: Validate connection
Confirm the API key works by calling the regions endpoint:
curl -sf -H "Authorization: ApiKey ${EC_API_KEY}" \
"${EC_BASE_URL}/api/v1/serverless/regions" > /dev/null && echo "Authenticated." || echo "Authentication failed."
If validation fails, check:
- The API key is valid and not expired
- Network connectivity to
api.elastic-cloud.com
Examples
First-time setup
User: set up my cloud environment
Agent: Check if EC_API_KEY is set in your terminal. If not, generate a key at
https://cloud.elastic.co/account/keys and run:
export EC_API_KEY="your-key"
Then confirm and I'll validate the connection.
Setup with custom region
User: set up cloud with eu region
Agent: [runs setup, sets EC_REGION to user's preferred EU region]
Guidelines
- Never receive, echo, or log API keys, passwords, or any credentials in the chat. Instruct the user to manage secrets in their terminal or using files directly.
- Always validate the connection after setting the key.
- Default region is
gcp-us-central1— only change if the user requests a different region. - This skill is a prerequisite. Other cloud skills should refer here when
EC_API_KEYis missing.
Environment variables
| Variable | Required | Description |
|---|---|---|
EC_API_KEY | Yes | Elastic Cloud API key |
EC_BASE_URL | No | Cloud API base URL (default: https://api.elastic-cloud.com) |
EC_REGION | No | Default region (default: gcp-us-central1) |
Troubleshooting
| Problem | Fix |
|---|---|
401 Unauthorized | API key is invalid or expired — generate a new one |
connection refused | Check network access to api.elastic-cloud.com |
FAQ
What does the cloud-setup skill do?
Configures Elastic Cloud authentication and environment defaults. Use when setting up ECAPIKEY, configuring Cloud API access, or when another cloud skill requires credentials.
How do I install cloud-setup?
Run npx skills add https://github.com/elastic/agent-skills --skill cloud-setup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cloud-setup/ (personal) or .claude/skills/cloud-setup/ (project).
Which AI agents can use cloud-setup?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cloud-setup safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cloud-setup?
It is published by elastic in elastic/agent-skills. It has 2,744 recorded installs.
More from elastic/agent-skills
elasticsearch-esql
elastic/agent-skills
Execute ESQL (Elasticsearch Query Language) queries, use when the user wants to query Elasticsearch data, analyze logs, aggregate metrics, explore data, or create charts and dashboards from ESQL results.
elasticsearch-onboarding
elastic/agent-skills
Help developers new to Elasticsearch get from zero to a working search experience. Guide them through understanding their intent, mapping their data, and building a search experience with best practices baked in. Use this when the user shows intent to build search-related functionality, asks about Elasticsearch-related concepts for their use case, or expresses the need for help getting started with Elasticsearch.
kibana-dashboards
elastic/agent-skills
Create and manage Kibana Dashboards and Lens visualizations. Use when you need to define dashboards and visualizations declaratively, version control them, or automate their deployment.
security-case-management
elastic/agent-skills
Create, search, update, and manage SOC cases via the Kibana Cases API. Use when tracking incidents, linking alerts to cases, adding investigation notes, or managing triage output.
kibana-alerting-rules
elastic/agent-skills
Create and manage Kibana alerting rules. Use when creating, updating, or managing rule lifecycle (enable, disable, mute, snooze), choosing metric threshold rule types and params, or read-only find/list with tag filters.
kibana-agent-builder
elastic/agent-skills
Create and manage Kibana Agent Builder agents and custom tools. Use when asked to create, update, delete, test, or inspect agents or tools in Agent Builder, or when the user wants to understand what agents or tools already exist.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.