Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Model lifecycle (Legacy)

Amazon Bedrock is continuously working to bring the latest versions of foundation models that have better capabilities, accuracy, and safety. As we launch new model versions, you can test them with the Amazon Bedrock console or API, and migrate your applications to benefit from the latest model versions.

A model offered on Amazon Bedrock can be in one of these states: Active, Legacy, or End-of-Life (EOL). You can see the status of offered models in the console and in the tables below. Additionally, when you make a GetFoundationModel or ListFoundationModels call, the state of the model will be shown in the modelLifecycle field in the response. Once a model launches on Amazon Bedrock, it will remain on Amazon Bedrock for at least 12 months before the EOL date.

Active versions

Active — The model provider is actively working on this version. In most cases, model providers sunset a model after newer versions become available. For a list of currently active models and their supported regions, see Regional availability. For model specific details, see Model cards.

Legacy and end-of-life (EOL) models

Legacy — We will notify you when a model provider moves a model to the Legacy state. A model will be in the Legacy state for at least 6 months before the EOL date. While you can continue to use a Legacy model during this period, you should plan to transition to an Active model before the EOL date. New customers can't use Legacy models and existing customers may lose access to Legacy models after 15 days of inactivity.

For models with EOL dates after February 1, 2026: After a minimum of 3 months in the Legacy state, a model will enter the public extended access portion of the Legacy period. During this public extended access period, active users of a Legacy model can continue to use it until the EOL date (for a minimum of 3 months), but you should expect higher pricing, which will be set by the model provider. When the model first enters the Legacy state, we will notify you of the provider's chosen date to transition a model to public extended access (which will be at least 3 months from notification) and pricing changes (if any). We will also notify you before any further pricing changes during the public extended access period.

You can't create a new Provisioned Throughput for models in the Legacy state.

EOL — After the EOL date, a model will be marked EOL in the console and in the following table. On, or soon after the EOL date, the model is no longer available for use in all AWS Regions and requests made to this version will fail, unless there is a private arrangement between you and the provider for continued access. You will need to migrate to the latest model by updating your application code before the EOL date. Migration will not happen automatically.

Model lifecycle state can differ by AWS Region. The Regions column in the following tables lists only the Regions covered by a model's announced EOL date. A model can remain Active in other Regions, and the absence of a Region from a row doesn't mean the model will stay available there indefinitely. To check the current state for the Region you use, call ListFoundationModels or GetFoundationModel in that Region and read the modelLifecycle field.

Models with a scheduled EOL date

The following models are in the Legacy state with an announced EOL date. Migrate to an Active model before the EOL date.

Models that have reached EOL

The following models have passed their EOL date. They have been removed from the Regions listed, and requests to them fail. These entries are retained for reference, so that you can identify a model ID that no longer works and see when it reached EOL.

The public extended access date indicates when a Legacy model enters the public extended access portion of the Legacy period. During this phase, pricing may increase as set by the model provider. The model remains available until its EOL date.

Customized Models and Lifecycle Behavior

When a foundation model transitions to the Legacy state, customization capabilities become restricted. If you previously fine-tuned or customized the model before it entered the Legacy state, you may:

However, after the model is in Legacy state, you cannot create new fine-tuning jobs on that model. You cannot create new Provisioned Throughput (PT) endpoints. New customers cannot start using the legacy model and existing customers may lose access after 15 days of inactivity.

Because Legacy models are scheduled for retirement, customers are strongly encouraged to begin transitioning workloads and customized deployments to an Active model as soon as the Legacy announcement is made, and complete migration before the model's End-of-Life (EOL) date.