Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.236 ·

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

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

You'll notice Improvements
JSON All of v2.1.236
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
DocumentationArea: what it touches
ImprovementsKind: in v2.1.236,
What probably matters to youSection of the release
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 →

Feedback