Workspaces

Inference and resource requests on Claude Platform on AWS target a workspace. You pass the workspace's ID in the anthropic-workspace-id header on these API calls. Workspace IDs use the tagged format wrkspc_ followed by an alphanumeric identifier (for example, wrkspc_01AbCdEf23GhIj). See Obtain your workspace ID if you don't have it yet.

Workspace scoping

Workspaces are bound to a single AWS region. A workspace created in us-west-2 can only be accessed through the us-west-2 endpoint. Usage, quotas, cost, files, batches, and Skills all roll up per workspace, giving you per-region breakdowns in the Claude Console.

Workspaces also serve as the primary IAM resource for Claude Platform on AWS. You grant or deny access to specific workspaces through AWS IAM policies using the workspace ARN. The ARN's resource segment is the same wrkspc_-prefixed ID you pass in the anthropic-workspace-id header:

arn:aws:aws-external-anthropic:{region}:{account-id}:workspace/{workspace-id}

For example:

arn:aws:aws-external-anthropic:us-west-2:123456789012:workspace/wrkspc_01AbCdEf23GhIj

See IAM policies for policy examples.

Managing workspaces

Create additional workspaces, rename a workspace, or archive a workspace from the AWS Console Workspaces page or with the Admin API workspace endpoints. A new workspace is bound to the AWS region of the endpoint you call to create it (see Workspace scoping). With the Admin role, you can also create, rename, and archive workspaces from the Claude Console Workspaces page.