Skip to content
Hugin
A person seen from behind walks between rows of black server cabinets with blue indicator lights.

Hugin News

AWS lists April 27 for Sonnet 4.5 retirement in two Bedrock GovCloud regions

1 min read

AI-generated editorial illustration for Hugin.

This record was prepared on the date shown and recovered after a publishing interruption.

Amazon schedules the end of Claude Sonnet 4.5 on Bedrock for April 27, 2027, in its two GovCloud regions and tells customers to migrate before then. Public extended access starts January 27 there. The same table lists January 8 for extended access and April 8 for retirement in a separate group that includes commercial US East and US West regions.

amazon-bedrockawsgovcloudmodel-lifecycledevelopers
source receipt
1
source host
1
read time
1min
primary source
Linked

For a customer running Claude Sonnet 4.5 on Amazon Bedrock, the retirement date depends on the AWS region serving the model. The public schedule lists April 27, 2027, for both GovCloud regions and April 8, 2027, for the other regions listed for that version.

Which dates go with your region

For us-gov-east-1 and us-gov-west-1, AWS lists October 27, 2026, as the date Sonnet 4.5 entered its Legacy stage. Public extended access begins January 27, 2027. End of life follows on April 27.

The October 10 report covered the other regional line for the same model ID, anthropic.claude-sonnet-4-5-20250929-v1:0. That line still includes us-east-1, us-east-2, us-west-1 and us-west-2. It gives October 8, 2026, for entry into Legacy, January 8, 2027, for public extended access and April 8 for end of life. The AWS table does not say when the GovCloud line was added.

What customers can check

AWS's policy for models launched on Bedrock before September 7, 2026, says new customers cannot use a Legacy model and existing customers may lose access after 15 days of inactivity. Active users can continue during public extended access. AWS tells customers to expect higher prices during that phase but gives no Sonnet 4.5 rate in the lifecycle table.

Customers can check their own region by calling GetFoundationModel or ListFoundationModels there and reading the modelLifecycle field. AWS says customers need to update their application code before the relevant end-of-life date. Requests to that version will fail on or soon after that date unless the customer and provider have a private arrangement for continued access. Migration does not happen automatically. These dates govern Bedrock usage.

Source links