docs: Claude Sonnet 5 now on Bedrock InvokeModel + AWS platform migration guidance#1061
Merged
Merged
Conversation
…tion guidance Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: Two real changes for API users landed today. Sonnet 5 is now available on the legacy Bedrock InvokeModel surface — it was previously explicitly blocked ("not available on this surface"), which means anyone who hit that gate and moved on should know the door is open now. Sonnet 5 also gets the 1M-token context window on Bedrock, same as the other flagship models. The second change adds new migration guidance to the Claude Platform on AWS docs, explaining how to do a zero-downtime cutover from an existing Claude organization to the AWS-managed one (billing, auth, and rate limit differences spelled out explicitly). The rest of the 103-file diff is noise: a mass ZDR link refactor (the eligibility blurbs were standardized and the target URL moved from
build-with-claude/tomanage-claude/api-and-data-retention) plus the usual CDN image signature rotations in support articles.HIGHLIGHTS:
claude-on-amazon-bedrock-legacy.md— model was previously excluded fromInvokeModelonbedrock-runtime; now listed alongside Fable 5, Opus 4.8, Opus 4.7claude-platform-on-aws.md— new section covering gradual traffic cutover, billing (AWS Marketplace / Claude Consumption Units), auth (AWS credentials vs Claude Console API keys), and rate limit ramp-up advicemanage-claude/api-and-data-retention— no policy change, just centralization; the oldbuild-with-claude/api-and-data-retentionpath no longer holds per-feature eligibility detailCreated by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning