# Your AWS account. Answered in plain words.

Source: https://corespeed.io/integrations/aws

Connect AWS to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent calls any AWS API operation with your IAM credentials, looks up current AWS documentation, and signs short-lived S3 links. Writes, and reads that return a stored secret, are calls approvals can hold, and your IAM policy decides the rest.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect AWS after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Ask your account. Get the answer, not the console

Your agent finds the right AWS operation, calls it with your credentials, and explains what came back.

You ask your agent: "List the EC2 instances in us-west-2 and flag any that have been stopped for more than a week. Do not change anything."

It calls CoreSpeed:

- `aws__aws___search_documentation`: ok, 812 ms
- `aws__call_aws`: ok, 644 ms

It reads from: AWS.

### Instance review: Two instances to look at.

Ten instances are running. Two have been stopped for almost two weeks and still keep their volumes.

**Running**

- 10 instances across the api and web groups.

**Stopped for over a week**

- batch-worker-2: stopped October 28.
- load-test-1: stopped October 29.

_Illustrative account · Fictional data · Nothing changed_

All connectors: https://corespeed.io/docs/connectors

## From an API call to a clear answer

Requests you can make once AWS is connected. The data is fictional.

### Ask about any service

EC2 · us-west-2 · A read runs at once

- Operation: DescribeInstances
- Answer: 12 instances, 2 stopped
- Nothing changed

### Hold a write for a person

Stop an instance · A write waits for you

- Operation: StopInstances
- Policy: Ask before any write in production
- Waiting for you

### Share a file for 15 minutes

A link, not a key · Presigned S3 download

- Object: q3-usage.csv
- Expires: In 15 minutes
- No credential shared

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect AWS**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Which AWS services can my agent use?

Any AWS API operation in any region, as far as your IAM policy allows. One call is one API request, so the agent pages and repeats per region itself.

### Does my agent see my AWS access keys?

No. CoreSpeed signs calls with your IAM keys and refuses listed credential-issuing operations like STS AssumeRole. Other responses can contain secrets, so scope the IAM policy.

### Does a read change anything in my account?

No. Get, List, Describe and Head operations are reads. Writes, and reads that return a stored secret, are separate calls that approvals can hold. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/aws

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [Cloudflare for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/cloudflare): Audit DNS, check Workers and R2, and change Cloudflare settings from your agent, with the permissions you grant.
- [Daytona for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/daytona): Create Daytona sandboxes, run commands and read their files from your agent, with your own Daytona API key.
- [Google Cloud for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gcp): Debug Cloud Run from its logs, find idle spend, and read billing inside your agent, with your own Google account.
- [Okta for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/okta): Review who has access, check sign-ins in the System Log, and prepare offboarding in Okta from your agent.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- AWS MCP Server: https://docs.aws.amazon.com/aws-mcp/latest/userguide/what-is-mcp-server.html
- AWS access keys: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html
- Amazon S3 presigned URLs: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)