Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.236 Home All releases ←olderv2.1.235 v2.1.237newer→
Claude Code v2.1.236

AWS self-hosted environments documented as supported, with auth and session limits

You'll notice
Useful3 Signal4
Documentation

Self-hosted environments on AWS are documented as supported, with auth and session-length limits spelled out.

What

The bundled platform availability reference no longer lists self-hosted environments on Claude Platform on AWS as "Not available". The self-hosted sandbox row now marks them supported and spells out how workers authenticate, how long a session can run unattended, and what a self-hosted session on AWS cannot do.

Details
  • Workers authenticate either with IAM/SigV4 credentials or with an API key issued from the AWS Console that carries the AnthropicSelfHostedEnvironmentAccess managed policy.
  • API keys generated in the Anthropic Console do not work against the AWS endpoint, so an existing Anthropic Console environment key has to be replaced with one of the two AWS methods.
  • A session runs autonomously for at most 6 hours before it needs reauthentication; sending any user-role event continues it.
  • Self-hosted environments on AWS cannot attach memory stores, and an attempt to do so is rejected at session create rather than failing later.
Evidence

` AnthropicSelfHostedEnvironmentAccess managed policy , AnthropicSelfHostedEnvironmentAccess`

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.236 →