# autonomous-cloud-orchestration

autonomous-cloud-orchestration walks your agent through AWS Bedrock AgentCore: picking the right service and wiring the deployment with the AWS CLI.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 131 installs · ★ 50 repo stars
- Author: qodex-ai
- License: LicenseRef-Proprietary · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qodex-ai/ai-agent-skills/tree/HEAD/skills/autonomous-cloud-orchestration/SKILL.md
- Updated: 2026-01-05
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/autonomous-cloud-orchestration

## What it does

Seven AgentCore services sit behind this skill: Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability. The `SKILL.md` holds a service table that points at per-service READMEs under `services/`, so the agent opens the doc it actually needs.

Workflows come as ordered steps. A Gateway target means uploading the OpenAPI schema to S3, creating a credential provider when the API uses key auth, linking schema and credentials to the target, then checking status and connectivity. Lambda targets lean on IAM roles, MCP servers on OAuth. Everything runs through AWS CLI commands.

Fresh AWS answers depend on AWS MCP tools being there. Without them the skill sends you to set up AWS MCP: the full server when `uvx` and AWS credentials exist, or the documentation-only MCP server with no auth otherwise.

## Requirements
- Works with: AWS

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add qodex-ai/ai-agent-skills --skill autonomous-cloud-orchestration -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/autonomous-cloud-orchestration/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/autonomous-cloud-orchestration/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add qodex-ai/ai-agent-skills --skill autonomous-cloud-orchestration -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/autonomous-cloud-orchestration/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add qodex-ai/ai-agent-skills --skill autonomous-cloud-orchestration -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/autonomous-cloud-orchestration/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install qodex-ai/ai-agent-skills skills/autonomous-cloud-orchestration
```

2. **Manually: put the files in place**
- File: `.github/skills/autonomous-cloud-orchestration/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add qodex-ai/ai-agent-skills --skill autonomous-cloud-orchestration -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/qodex-ai/ai-agent-skills --path skills/autonomous-cloud-orchestration
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/autonomous-cloud-orchestration/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add qodex-ai/ai-agent-skills --skill autonomous-cloud-orchestration -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qodex-ai/ai-agent-skills/tree/HEAD/skills/autonomous-cloud-orchestration/SKILL.md

## When to use it
- turn a REST API into MCP tools with Gateway
- give an agent memory that survives between sessions
- keep API keys in an Identity credential provider and attach them to a target
- trace agent runs and set CloudWatch alarms
- run agent code inside the Code Interpreter sandbox

## Example prompts
- Walk me through deploying our OpenAPI schema as a Gateway target and testing connectivity.
- Add conversation memory to this agent — which Memory setup and which `bedrock-agentcore-control` commands do I need?
- Enable Observability for the agent and tell me which metrics belong on the CloudWatch dashboard.

## Similar
- [amazon-bedrock](https://affpapa.org/en/nevibecode/skills/amazon-bedrock.md) — skill · 9500 installs
- [agents-build](https://affpapa.org/en/nevibecode/skills/agents-build.md) — skill · 2200 installs
- [aws-agentic-ai](https://affpapa.org/en/nevibecode/skills/aws-agentic-ai.md) — skill · 702 installs
- [aws-harness](https://affpapa.org/en/nevibecode/skills/aws-harness.md) — skill · ★ 301 repo stars
- [AWS Bedrock AgentCore](https://affpapa.org/en/nevibecode/mcp/aws-bedrock-agentcore.md) — MCP server · ★ 9939 repo stars
- [cloud-audit](https://affpapa.org/en/nevibecode/mcp/cloud-audit.md) — MCP server · ★ 75 repo stars

From the same set: [qodex-ai/ai-agent-skills](https://affpapa.org/en/nevibecode/by/qodex-ai/ai-agent-skills.md) — 42 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
