Understanding Amazon Bedrock mannequin lifecycle

Amazon Bedrock usually releases new basis mannequin (FM) variations with higher capabilities, accuracy, and security. Understanding the mannequin lifecycle is important for efficient planning and administration of AI purposes constructed on Amazon Bedrock. Earlier than migrating your purposes, you’ll be able to take a look at these fashions by means of the Amazon Bedrock console or API to judge their efficiency and compatibility.

This put up reveals you learn how to handle FM transitions in Amazon Bedrock, so you can also make certain your AI purposes stay operational as fashions evolve. We talk about the three lifecycle states, learn how to plan migrations with the brand new prolonged entry characteristic, and sensible methods to transition your purposes to newer fashions with out disruption.

Amazon Bedrock mannequin lifecycle overview

A mannequin provided on Amazon Bedrock can exist in one in all three states: Energetic, Legacy, or Finish-of-Life (EOL). Their present standing is seen each on the Amazon Bedrock console and in API responses. For instance, if you make a GetFoundationModel or ListFoundationModels name, the state of the mannequin will probably be proven within the modelLifecycle discipline within the response.

The next diagram illustrates the small print round every mannequin state.

The state particulars are as follows:

• ACTIVE – Energetic fashions obtain ongoing upkeep, updates, and bug fixes from their suppliers. Whereas a mannequin is Energetic, you should utilize it for inference by means of APIs like InvokeModel or Converse, customise it (if supported), and request quota will increase by means of AWS Service Quotas.
• LEGACY – When a mannequin supplier transitions a mannequin to Legacy state, Amazon Bedrock will notify clients with a minimum of 6 months’ advance discover earlier than the EOL date, offering important time to plan and execute a migration to newer or various mannequin variations. In the course of the Legacy interval, present clients can proceed utilizing the mannequin, although new clients could be unable to entry it, and present clients would possibly lose entry for inactive accounts if they don’t name the mannequin for a interval of 15 days or extra. Organizations ought to word that creating new provisioned throughput by mannequin items turns into unavailable, and mannequin customization capabilities would possibly face restrictions. For fashions with EOL dates after February 1, 2026, Amazon Bedrock introduces an extra section throughout the Legacy state:
  • Public prolonged entry interval – After spending a minimal of three months in Legacy standing, the mannequin enters this prolonged entry section. Energetic customers can proceed utilizing it for a minimum of one other 3 months till EOL. Throughout prolonged entry, quota improve requests by means of AWS Service Quotas will not be anticipated to be permitted, so plan your capability wants earlier than a mannequin enters this section. Throughout this era, pricing could also be adjusted (see Pricing throughout prolonged entry under), and clients will obtain notifications in regards to the transition date and any adjustments.
• END-OF-LIFE (EOL) – When a mannequin reaches its EOL date, it turns into fully inaccessible throughout all AWS Areas until particularly famous within the EOL record. API requests to EOL fashions will fail, rendering them unavailable to most clients until particular preparations exist between the client and supplier for continued entry. The transition to EOL requires proactive buyer motion—migration doesn’t occur routinely. Organizations should replace their utility code to make use of various fashions earlier than the EOL date arrives. When EOL is reached, the mannequin turns into fully inaccessible for many clients.

After a mannequin launches on Amazon Bedrock, it stays obtainable for a minimum of 12 months after launch and stays in Legacy state for a minimum of 6 months earlier than EOL. This timeline helps clients plan migrations with out speeding.

Pricing throughout prolonged entry

In the course of the prolonged entry interval, pricing could also be adjusted by the mannequin supplier. If pricing adjustments are deliberate, you may be notified within the preliminary legacy announcement and earlier than any subsequent adjustments take impact, so there will probably be no shock retroactive worth will increase. Clients with present personal pricing agreements with mannequin suppliers or these utilizing provisioned throughput will proceed to function beneath their present pricing phrases through the prolonged entry interval. This makes certain clients who’ve made particular preparations with mannequin suppliers or invested in provisioned capability is not going to be unexpectedly affected by any pricing adjustments.

Communication Course of for Mannequin State Modifications

Clients will obtain a notification 6 months previous to a mannequin’s EOL date when the mannequin supplier transitions a mannequin to Legacy state. This proactive communication strategy ensures that clients have adequate time to plan and execute their migration methods earlier than a mannequin turns into EOL.

Notifications embody particulars in regards to the mannequin being deprecated, necessary dates, prolonged entry availability, and when the mannequin will probably be EOL. AWS makes use of a number of channels to make sure these necessary communications attain the appropriate folks, together with:

• E mail notifications
• AWS Well being Dashboard
• Alerts within the Amazon Bedrock console
• Programmatic entry by means of the API.

To be sure you obtain these notifications, confirm and configure your account contact e-mail addresses. By default, notifications are despatched to your account’s root person e-mail and alternate contacts (operations, safety, and billing). You’ll be able to assessment and replace these contacts in your AWS Account web page within the Alternate contacts part. So as to add further recipients or supply channels (comparable to Slack or e-mail distribution lists), go to the AWS Person Notifications console and select AWS managed notifications subscriptions to handle your supply channels and account contacts. In case you are not receiving anticipated notifications, test that your e-mail addresses are accurately configured in these settings and that notification emails from well being@aws.com will not be being filtered by your e-mail supplier.

Migration methods and finest practices

When migrating to a more recent mannequin, replace your utility code and test that your service quotas can deal with anticipated quantity. Planning forward helps you transition easily with minimal disruption.

Planning your migration timeline

Begin planning as quickly as a mannequin enters Legacy state:

• Evaluation section – Consider your present utilization of the legacy mannequin, together with which purposes rely on it, typical request patterns, and particular behaviors or outputs that your purposes depend on.
• Analysis section – Examine the advisable alternative mannequin, understanding its capabilities, variations from the legacy mannequin, new options that might improve your purposes, and the brand new mannequin’s Regional availability. Evaluate API adjustments and documentation.
• Testing section – Conduct thorough testing with the brand new mannequin and evaluate efficiency metrics between fashions. This helps establish changes wanted in your utility code or immediate engineering.
• Migration section – Implement adjustments utilizing a phased deployment strategy. Monitor system efficiency throughout transition and preserve rollback functionality.
• Operational section – After migration, repeatedly monitor your purposes and person suggestions to verify they’re performing as anticipated with the brand new mannequin.

Technical migration steps

Check your migration completely:

• Replace API references – Modify your utility code to reference the brand new mannequin ID. For instance, altering from anthropic.claude-3-5-sonnet-20240620-v1:0 to anthropic.claude-sonnet-4-5-20250929-v1:0 or world cross-Area inference world.anthropic.claude-sonnet-4-5-20250929-v1:0. Replace immediate buildings in line with new mannequin’s finest practices. For extra detailed steerage, check with Migrate from Anthropic’s Claude Sonnet 3.x to Claude Sonnet 4.x on Amazon Bedrock.
• Request quota will increase – Earlier than absolutely migrating, be sure you have adequate quotas for the brand new mannequin by requesting will increase by means of the AWS Service Quotas console if vital.
• Regulate prompts – Newer fashions would possibly reply in another way to the identical prompts. Evaluate and refine your prompts accordingly to the brand new mannequin specs. You can too use instruments such because the immediate optimizer in Amazon Bedrock to help with rewriting your immediate for the goal mannequin.
• Replace response dealing with – If the brand new mannequin returns responses in a distinct format or with totally different traits, replace your parsing and processing logic accordingly.
• Optimize token utilization – Benefit from effectivity enhancements in newer fashions by reviewing and optimizing your token utilization patterns. For instance, fashions that help immediate caching can cut back the fee and latency of your invocations.

Testing methods

Thorough testing is crucial for a profitable migration:

• Aspect-by-side comparability – Run the identical requests towards each the legacy and new fashions to match outputs and establish any variations which may have an effect on your utility. For manufacturing environments, think about shadow testing—sending duplicate requests to the brand new mannequin alongside your present mannequin with out affecting end-users. With this strategy, you’ll be able to consider mannequin efficiency, latency and errors charges, and different operational elements earlier than full migration. Carry out A/B testing for person affect evaluation by routing a managed share of stay site visitors to the brand new mannequin whereas monitoring key metrics comparable to person engagement, process completion charges, satisfaction scores, and enterprise KPIs.
• Efficiency testing – Measure response occasions, token utilization, and different efficiency metrics to know how the brand new mannequin performs in comparison with the legacy model. Validate business-specific success metrics.
• Regression and edge case testing – Be certain present performance continues to work as anticipated with the brand new mannequin. Pay particular consideration to uncommon or advanced inputs which may reveal variations in how the fashions deal with difficult eventualities.

Conclusion

The mannequin lifecycle coverage in Amazon Bedrock offers you clear levels for managing FM evolution. Transition intervals provide prolonged entry choices, and provisions for fine-tuned fashions enable you steadiness innovation with stability.

Keep knowledgeable about mannequin states by means of the AWS Well being Dashboard, plan migrations when fashions enter the Legacy state, and take a look at newer variations completely. These pointers may help you preserve continuity in your AI purposes whereas utilizing improved capabilities in newer fashions.

When you’ve got additional questions or considerations, attain out to your AWS workforce. We wish to enable you and facilitate a easy transition as you proceed to benefit from the most recent developments in FM know-how.

For continued studying and implementation help, discover the official AWS Bedrock documentation for complete guides and API references. Moreover, go to the AWS Machine Studying Weblog and AWS Structure Middle for real-world case research, migration finest practices, and reference architectures that may assist optimize your mannequin lifecycle administration technique.

Concerning the authors

Saurabh Trikande is a Senior Product Supervisor for Amazon Bedrock and Amazon SageMaker Inference. He’s obsessed with working with clients and companions, motivated by the objective of democratizing AI. He focuses on core challenges associated to deploying advanced AI purposes, inference with multi-tenant fashions, value optimizations, and making the deployment of generative AI fashions extra accessible. In his spare time, Saurabh enjoys mountaineering, studying about modern applied sciences, following TechCrunch, and spending time along with his household.

Melanie Li, PhD, is a Senior Generative AI Specialist Options Architect at AWS primarily based in Sydney, Australia, the place her focus is on working with clients to construct options utilizing state-of-the-art AI/ML instruments. She has been actively concerned in a number of generative AI initiatives throughout APJ, harnessing the facility of LLMs. Previous to becoming a member of AWS, Dr. Li held information science roles within the monetary and retail industries.

Derrick Choo is a Senior Options Architect at AWS who accelerates enterprise digital transformation by means of cloud adoption, AI/ML, and generative AI options. He focuses on full-stack growth and ML, designing end-to-end options spanning frontend interfaces, IoT purposes, information integrations, and ML fashions, with a specific deal with pc imaginative and prescient and multi-modal programs.

Jared Dean is a Principal AI/ML Options Architect at AWS. Jared works with clients throughout industries to develop machine studying purposes that enhance effectivity. He’s taken with all issues AI, know-how, and BBQ.

Julia Bodia is Principal Product Supervisor for Amazon Bedrock.

Pooja Rao is a Senior Program Supervisor at AWS, main quota and capability administration and supporting enterprise growth for the Bedrock Go-To-Market workforce. Outdoors of labor, she enjoys studying, touring, and spending time along with her household.