agentsSource-backedReview first Safety ✓ Privacy ✓
Bedrock Claude Code Platform Agent
Community reusable agent prompt for operating Claude Code on Amazon Bedrock using official setup docs: IAM credential chains, regional model IDs, inference profiles, enterprise network config, quota errors, and Bedrock-specific troubleshooting steps.
HarnessClaude Code
Review first — review before installing
Open the source and read safety notes before installing.
Safety notes
- Long-lived access keys in repositories are forbidden; prefer IAM roles and OIDC for CI.
- Bedrock model allowlists should match security-approved model IDs only.
- Cross-region failover can violate data residency—confirm before switching regions.
- IAM policy changes require cloud admin approval; this agent advises, not applies, policies.
Privacy notes
- Bedrock invocation logs and CloudTrail events may contain prompt metadata—configure retention.
- Customer content handling follows AWS Bedrock and Anthropic agreements for your account type.
- Support bundles should redact account IDs and role ARNs when shared externally.
Prerequisites
- AWS account with Bedrock model access enabled in the target region.
- IAM role, SSO profile, or OIDC chain configured for Claude Code Bedrock mode.
- Enterprise network or proxy requirements documented in Claude Code network-config guidance.
- List of security-approved Bedrock model IDs and regions for your organization.
Schema details
- Install type
- copy
- Troubleshooting
- No
Source repository stats
- Scope
- Source repo
Full copyable content
## Content
Bedrock Claude Code Platform Agent is a community-authored reusable prompt for teams
running Claude Code against Amazon Bedrock. It applies official Claude Code on Amazon
Bedrock and network-config documentation—not an official Anthropic support agent.
## Scope Note
This prompt operationalizes documented Bedrock configuration and troubleshooting steps
from code.claude.com. It does not replace AWS support or Anthropic enterprise onboarding.
## Agent Prompt
You are a Bedrock platform specialist for Claude Code. Help teams configure and debug
Bedrock-backed Claude Code using only official Anthropic and AWS documentation references.
Workflow:
1. **Mode confirmation.** Verify Claude Code is configured for Bedrock rather than the direct Anthropic API per setup docs.
2. **Identity.** Review IAM roles, AWS profiles, SSO, or CI OIDC chains; reject embedded long-lived keys in repos.
3. **Models and regions.** Match requested capabilities to approved Bedrock model IDs and enabled regions documented for Claude Code.
4. **Network.** Apply Claude Code network-config guidance for proxies, TLS inspection, and VPC endpoints reaching Bedrock.
5. **Quotas and throttling.** Interpret throttling and quota errors; recommend retries, limits increases, or model fallbacks.
6. **Enterprise policy.** Align managed Claude Code settings, logging, and zero-data-retention requirements with Bedrock usage.
7. **Runbook.** Provide verification steps and AWS admin escalation templates with evidence.
Output contract:
- Configuration summary: region, model IDs, credential source.
- Error diagnosis with IAM, quota, or network causes.
- Developer vs AWS admin remediation steps.
- Compliance notes on logging and residency.
## Features
- Maps Bedrock setup docs to repeatable troubleshooting workflows.
- Separates developer fixes from IAM or quota admin actions.
- Incorporates enterprise network-config requirements.
- Produces admin-ready escalation templates.
## Use Cases
- First Bedrock enablement for a platform engineering team.
- Debug AccessDeniedException during Claude Code sessions on AWS laptops.
- Standardize approved Bedrock model IDs across business units.
- Prepare cloud admin tickets with precise IAM policy diffs.
## Source Notes
Verified against Claude Code Amazon Bedrock and network-config documentation on
**2026-06-16**:
- Official docs describe configuring Claude Code to call Claude models through Amazon
Bedrock with AWS credentials rather than Anthropic API keys.
- Setup covers model selection, region availability, and authentication patterns
appropriate to enterprise AWS environments.
- Network-config documentation addresses corporate proxies and TLS requirements that
affect Bedrock endpoint reachability from developer machines and CI.
## Duplicate Check
Checked content/guides and content/agents for Bedrock Claude Code coverage.
claude-code-on-amazon-bedrock-setup is a one-time setup guide. No agents entry provides
ongoing Bedrock platform troubleshooting with IAM, quota, and network-config runbooks.
## Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude
Code Amazon Bedrock documentation and the public anthropics/claude-code repository.
No paid placement, referral, or affiliate relationship.
## Sources
- Claude Code on Amazon Bedrock - https://code.claude.com/docs/en/amazon-bedrock
- Claude Code network config - https://code.claude.com/docs/en/network-config
- Claude Code repository - https://github.com/anthropics/claude-codeAbout this resource
Content
Bedrock Claude Code Platform Agent is a community-authored reusable prompt for teams running Claude Code against Amazon Bedrock. It applies official Claude Code on Amazon Bedrock and network-config documentation—not an official Anthropic support agent.
Scope Note
This prompt operationalizes documented Bedrock configuration and troubleshooting steps from code.claude.com. It does not replace AWS support or Anthropic enterprise onboarding.
Agent Prompt
You are a Bedrock platform specialist for Claude Code. Help teams configure and debug Bedrock-backed Claude Code using only official Anthropic and AWS documentation references.
Workflow:
- Mode confirmation. Verify Claude Code is configured for Bedrock rather than the direct Anthropic API per setup docs.
- Identity. Review IAM roles, AWS profiles, SSO, or CI OIDC chains; reject embedded long-lived keys in repos.
- Models and regions. Match requested capabilities to approved Bedrock model IDs and enabled regions documented for Claude Code.
- Network. Apply Claude Code network-config guidance for proxies, TLS inspection, and VPC endpoints reaching Bedrock.
- Quotas and throttling. Interpret throttling and quota errors; recommend retries, limits increases, or model fallbacks.
- Enterprise policy. Align managed Claude Code settings, logging, and zero-data-retention requirements with Bedrock usage.
- Runbook. Provide verification steps and AWS admin escalation templates with evidence.
Output contract:
- Configuration summary: region, model IDs, credential source.
- Error diagnosis with IAM, quota, or network causes.
- Developer vs AWS admin remediation steps.
- Compliance notes on logging and residency.
Features
- Maps Bedrock setup docs to repeatable troubleshooting workflows.
- Separates developer fixes from IAM or quota admin actions.
- Incorporates enterprise network-config requirements.
- Produces admin-ready escalation templates.
Use Cases
- First Bedrock enablement for a platform engineering team.
- Debug AccessDeniedException during Claude Code sessions on AWS laptops.
- Standardize approved Bedrock model IDs across business units.
- Prepare cloud admin tickets with precise IAM policy diffs.
Source Notes
Verified against Claude Code Amazon Bedrock and network-config documentation on 2026-06-16:
- Official docs describe configuring Claude Code to call Claude models through Amazon Bedrock with AWS credentials rather than Anthropic API keys.
- Setup covers model selection, region availability, and authentication patterns appropriate to enterprise AWS environments.
- Network-config documentation addresses corporate proxies and TLS requirements that affect Bedrock endpoint reachability from developer machines and CI.
Duplicate Check
Checked content/guides and content/agents for Bedrock Claude Code coverage. claude-code-on-amazon-bedrock-setup is a one-time setup guide. No agents entry provides ongoing Bedrock platform troubleshooting with IAM, quota, and network-config runbooks.
Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude Code Amazon Bedrock documentation and the public anthropics/claude-code repository. No paid placement, referral, or affiliate relationship.
Sources
- Claude Code on Amazon Bedrock - https://code.claude.com/docs/en/amazon-bedrock
- Claude Code network config - https://code.claude.com/docs/en/network-config
- Claude Code repository - https://github.com/anthropics/claude-code
Source citations
Add this badge to your README
Show that Bedrock Claude Code Platform Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/bedrock-claude-code-platform-agent)How it compares
Bedrock Claude Code Platform Agent side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Bedrock Claude Code Platform Agent Community reusable agent prompt for operating Claude Code on Amazon Bedrock using official setup docs: IAM credential chains, regional model IDs, inference profiles, enterprise network config, quota errors, and Bedrock-specific troubleshooting steps. Open dossier | Vertex AI Claude Code Platform Agent Community reusable agent prompt for operating Claude Code on Google Vertex AI using official setup docs: GCP projects, service accounts, regions, VPC-SC constraints, billing alerts, and Vertex-specific Claude Code troubleshooting steps. Open dossier | Microsoft Foundry Claude Code Agent Community reusable agent prompt for operating Claude Code on Microsoft Foundry using official setup docs: Azure subscriptions, Entra ID auth, deployment names, enterprise network config, and Foundry-specific Claude Code troubleshooting steps. Open dossier | Enterprise Network Proxy Debugging Agent Community reusable agent prompt for debugging Claude Code behind corporate HTTP proxies and mTLS using official network-config docs: HTTP_PROXY variables, certificate trust, downloads reachability, and remote MCP URL failures. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | agents | agents | agents |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | kiannidev |
| Added | 2026-06-16 | 2026-06-16 | 2026-06-16 | 2026-06-16 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Long-lived access keys in repositories are forbidden; prefer IAM roles and OIDC for CI. Bedrock model allowlists should match security-approved model IDs only. Cross-region failover can violate data residency—confirm before switching regions. IAM policy changes require cloud admin approval; this agent advises, not applies, policies. | ✓Service account keys in repositories are high risk; prefer workload identity federation. Vertex endpoints and regions must match data residency commitments. Shared service accounts across teams complicate audit—prefer scoped identities. GCP org policy changes require admin approval; this agent advises, not applies, policies. | ✓Client secrets and connection strings must not be committed to repositories. Deployment names and API versions must match Foundry-supported Claude models only. Cross-subscription resources can break policy—keep Foundry resources in approved subscriptions. Azure RBAC changes require admin approval; this agent advises, not applies, policies. | ✓Do not paste proxy credentials or client private keys into shared chat logs. Disabling TLS verification globally is not an acceptable production fix. Split-tunnel VPN changes affect MCP SaaS endpoints—coordinate with security teams. Debugging commands should use read-only curl or openssl checks before changing production laptops. |
| Privacy notes | ✓Bedrock invocation logs and CloudTrail events may contain prompt metadata—configure retention. Customer content handling follows AWS Bedrock and Anthropic agreements for your account type. Support bundles should redact account IDs and role ARNs when shared externally. | ✓Cloud Logging may capture request metadata; configure exclusions for sensitive projects. Customer data handling follows Google Cloud and Anthropic terms for Vertex Claude models. Support cases should avoid attaching application default credential JSON files. | ✓Azure Monitor and Foundry logs may store request metadata; configure retention accordingly. Customer content handling follows Microsoft and Anthropic agreements for Foundry Claude. Support tickets should redact tenant IDs and subscription names when posted publicly. | ✓Proxy logs may capture Anthropic API paths and internal MCP hostnames. Packet captures for debugging must follow company retention and access policies. Support tickets should redact employee emails and internal gateway URLs when possible. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
More like this, weekly
A short, calm digest of reviewed Claude resources. Unsubscribe any time.