AWS announced the implementation of Multi-Environment Access for the Claude Platform on AWS (CPonAWS). This allows users to access CPonAWS from production workloads on AWS, developer laptops, and external services on other cloud providers or on-premises CI/CD pipelines. Each environment can use different authentication methods while sharing a single subscription with workspace-level isolation.
Key facts
| Fact | Detail | The source says |
|---|---|---|
| Environments Supported | Production workloads on AWS, developer laptops, external services on other cloud providers or on-premises CI/CD pipelines | “You need Claude Platform on AWS (CPonAWS) inference from three environments: production workloads on AWS, developer laptops for local…” |
| Authentication Methods | Different authentication methods for each environment | “Each environment has different authentication requirements” |
| Isolation | Workspace-level isolation between production and development traffic | “all should share a single subscription with workspace-level isolation between production and development traffic” |
What happened
AWS has introduced Multi-Environment Access for the Claude Platform on AWS (CPonAWS), enabling users to access the platform from multiple environments including production workloads on AWS, developer laptops for local iteration, and external services on other cloud providers or on-premises CI/CD pipelines. Each environment can use different authentication methods, but all environments share a single subscription with workspace-level isolation between production and development traffic. For organizations with additional environments, AWS recommends creating a workspace per team or workload and repeating the cross-account role pattern for each.
In the Fathom Layer index
- Claude — AI Models & Intelligence
Source: Amazon Web Services