Install command
Provided
Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Provided
Copy snippet
Provided
Prerequisites
10 to clear
Platforms
4 listed
Difficulty
0/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
10 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens.
{
"aws": {
"env": {
"AWS_REGION": "${AWS_REGION:-us-east-1}",
"AWS_PROFILE": "${AWS_PROFILE}",
"FASTMCP_LOG_LEVEL": "${FASTMCP_LOG_LEVEL:-ERROR}"
},
"args": [
"awslabs.core-mcp-server@latest"
],
"command": "uvx"
}
}Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring.
aws sts get-caller-identity){
"aws": {
"env": {
"AWS_REGION": "${AWS_REGION:-us-east-1}",
"AWS_PROFILE": "${AWS_PROFILE}",
"FASTMCP_LOG_LEVEL": "${FASTMCP_LOG_LEVEL:-ERROR}"
},
"args": ["awslabs.core-mcp-server@latest"],
"command": "uvx"
}
}
Common usage pattern for this MCP server
Ask Claude: "Launch a new EC2 instance with custom tags"
Common usage pattern for this MCP server
Ask Claude: "Create an S3 bucket with versioning enabled"
Common usage pattern for this MCP server
Ask Claude: "Deploy a Lambda function with environment variables"
Common usage pattern for this MCP server
Ask Claude: "Set up CloudWatch alarms for application monitoring"
Common usage pattern for this MCP server
Ask Claude: "Create an RDS instance with automated backups"
Common usage pattern for this MCP server
Ask Claude: "Deploy a complete web application stack via CloudFormation"
Run aws configure to set access keys. Verify AWS_PROFILE matches profile in ~/.aws/credentials. Test with aws sts get-caller-identity command to confirm authentication.
Attach required IAM policy (AmazonEC2FullAccess, AmazonS3FullAccess, etc). Use AWS Policy Simulator to test permissions. Verify principal has necessary actions in IAM policy document.
Verify AWS_REGION environment variable matches resource location (us-east-1, eu-west-1, etc). Update with aws configure set region REGION_NAME. Check region in AWS Console matches CLI.
Validate with aws cloudformation validate-template --template-body file://template.yaml. Check resource types match AWS documentation exactly. Verify parameter types and AllowedValues constraints.
Implement exponential backoff for retries (wait 2^n seconds). Reduce concurrent requests to max 10. Request service quota increase at AWS Service Quotas console for sustained high usage.
Verify IAM credentials are valid and not expired. Check IAM policy permissions match required AWS service access. Ensure credential format is correct (access key ID and secret access key). For IAM roles, verify role trust relationships and assume role permissions.
Implement exponential backoff retry logic with jitter. Use AWS SDK built-in retry mechanisms. Monitor AWS service quotas and request rate limits. Implement request queuing and throttling to stay within service limits.
Check network connectivity and firewall settings. Verify AWS service endpoints are accessible. Increase request timeout values. Implement connection pooling and retry mechanisms with exponential backoff. Check VPC and security group configurations if using private endpoints.
Verify AWS credentials are valid and not expired. Check IAM user/role has required permissions. Ensure credentials are properly configured in environment variables or AWS credential files. For temporary credentials, verify session token hasn't expired.
Verify IAM policy includes required service permissions and resource ARNs. Check service-specific permissions (e.g., S3 bucket access, EC2 instance permissions). Review IAM policy conditions and resource restrictions. Use AWS IAM Policy Simulator to test permissions.
Implement exponential backoff retry logic with jitter. Use AWS SDK built-in retry mechanisms. Monitor service quotas and request rate limits. Consider using AWS service quotas API to check current usage and request increases if needed.
AWS Services MCP Server - MCP Servers side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
2 trust signals differ across this comparison (Package trust, Submitter).
| Field | Comprehensive AWS cloud services integration for infrastructure management, deployment, and monitoring Open dossier | Official AWS Labs MCP server for Amazon ECS that helps AI assistants containerize applications, deploy them to ECS, troubleshoot deployments, and explore ECS and ECR resources across the container application lifecycle. Open dossier | Official AWS Labs MCP server for Amazon EKS that gives AI code assistants real-time cluster state visibility and Kubernetes/EKS resource management, from cluster setup through deployment, troubleshooting, and optimization. Open dossier | Official AWS Labs MCP server that gives troubleshooting agents task-oriented access to Amazon CloudWatch metrics, alarms, logs, and PromQL queries for AI-assisted root-cause analysis and remediation recommendations. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | — | jaso0n0818 | jaso0n0818 | jaso0n0818 |
| Install risk | Low risk | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | first-party | source-backed | source-backed | source-backed |
| Author | AWS Labs | AWS Labs | AWS Labs | AWS Labs |
| Added | 2025-09-16 | 2026-06-21 | 2026-06-21 | 2026-06-20 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Scope AWS credentials to the intended accounts, regions, and services because infrastructure actions can affect production resources. | ✓The configuration above is read-only. Setting `ALLOW_WRITE=true` lets the server create and modify infrastructure (ECR repos, CloudFormation stacks, ECS services) and `ALLOW_SENSITIVE_DATA=true` exposes logs; enable these only deliberately. AWS documents this server as primarily for development, testing, and non-critical environments; keep write/sensitive-data disabled for production accounts and prefer non-production targets while evaluating it. This server acts on real infrastructure with your AWS credentials; scope the profile to the intended account, region, and resources, and run it only on a trusted host. | ✓The configuration above is read-only. Adding the `--allow-write` flag lets the server create, update, patch, and delete EKS/Kubernetes resources (including creating clusters via CloudFormation) and `--allow-sensitive-data-access` exposes logs and events; enable these only deliberately. This server acts on real infrastructure with your AWS credentials; scope the profile to the intended account, region, and clusters, and prefer non-production targets while evaluating it. Run it only on a trusted host, and review any generated manifests or CloudFormation actions before applying them. | ✓This server reads CloudWatch telemetry from your AWS account; scope the AWS credentials/profile to read-only CloudWatch access and the intended accounts and regions. It is designed for observability and troubleshooting (metrics, alarms, logs, PromQL) and does not modify resources, but it can issue many CloudWatch read APIs that may incur AWS request costs. Run it only on a trusted host, since it uses the local machine's AWS credentials to reach your account. Some PromQL tooling is region-limited and may require enabling OTel enrichment (`aws cloudwatch start-otel-enrichment`); review the server docs before relying on it. |
| Privacy notes | ✓AWS resource names, configuration, metrics, logs, ARNs, and account metadata may be exposed through tool calls and responses. | ✓Cluster, service, task, task-definition, and ECR metadata plus account/region identifiers can be returned through tool calls and exposed to the model. With sensitive-data access enabled, logs and deployment details may be returned; keep account identifiers, credentials, and log contents out of public prompts, issues, and screenshots. | ✓Cluster state, resource manifests, ARNs, and account/region metadata can be returned through tool calls and exposed to the model. With sensitive-data access enabled, pod logs and Kubernetes events may be returned; keep account identifiers, credentials, and log contents out of public prompts, issues, and screenshots. | ✓Metric values, alarm states and history, log group contents, namespaces, dimensions, ARNs, and account/region metadata can be returned through tool calls and exposed to the model. Queries and time ranges you ask about are sent to the CloudWatch APIs using your configured credentials; keep account identifiers and credentials out of public prompts, issues, and screenshots. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Configure Claude Code to run on Amazon Bedrock with correct AWS auth.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.