COST01-BP04 Keep up-to-date with new service releases
Cloud providers release new services, features, and price reductions constantly. Each release can make part of your architecture cheaper to run, and each price cut can change a decision you made months ago. Staying current, through your own monitoring and through experts who track the cloud provider, turns these changes into recurring savings.
Desired outcome:
-
You stay aware of new services, features, and price reductions that can lower the cost of running your workloads.
-
You have a defined owner and cadence for reviewing releases and deciding which are worth adopting.
-
You revisit deferred decisions when a relevant price reduction or new service changes their economics.
-
Your teams draw on account teams, partners, and events to learn about cost-relevant changes.
Common anti-patterns:
-
Keeping legacy designs out of habit, without checking whether a newer service would cost less.
-
Leaving the architecture unchanged for long periods without evaluating new options.
-
Ignoring release announcements and blog updates that describe cost-saving features.
-
Overlooking price reductions that would change past build-or-buy and deferral decisions.
-
Never engaging account teams, partners, or events that surface relevant changes.
Benefits of establishing this best practice:
-
Cost efficiency improves continuously as new services and features replace costlier approaches.
-
Access to newer capabilities keeps architectures aligned with current best practices.
-
Price reductions translate into savings, because deferred decisions are revisited.
-
Teams build a working understanding of the provider's direction and roadmap.
Level of risk exposed if this best practice is not established: Medium
Implementation guidance
The economics of a workload are not fixed at design time. A provider that ships features and cuts prices frequently keeps changing the cheapest way to run any workload. The risk is architectural inertia: a design that was cost-optimal at launch becomes more expensive as new functionality appear and go unadopted.
No team can evaluate every announcement, and not every new service is worth adopting. Adoption carries a cost in migration effort, testing, and retraining, which you weigh against the savings it promises. Separate monitoring from evaluation. Scan releases lightly but continuously. Then, on a cadence, deliberately evaluate the few changes that could materially reduce cost for your workloads.
Price reductions can change decisions retroactively. A build-or-buy analysis or a deferred migration might not have made sense at last year's prices. It can make sense now, with no change to the service itself. Treat a relevant price reduction as a prompt to reopen decisions you previously parked.
Announcement channels and blogs tell you what shipped. AWS account teams, solutions architects, and partners bring context on what is relevant to your workloads and how other organizations use it. That's often faster than reading every release yourself. Events and community meetups add peer experience. Assign this monitoring to a defined owner, often within a cloud center of excellence or cost-management function. Without a named owner, the work gets neglected.
Implementation steps
-
Assign ownership and a review cadence: Make one team or role responsible for monitoring new releases and price changes, and set a recurring cadence to evaluate them. Without a named owner, release monitoring lapses.
-
Subscribe to announcement channels: Follow What's New with AWS
and the AWS News Blog by RSS or email, and set your preferences on the AWS communication preferences page. Add the AWS Cost Management blog for cost-specific guidance. -
Track price reductions and revisit deferred decisions: Follow the price-reduction category of the AWS News Blog
, and reopen any decisions you parked for cost reasons when a relevant reduction lands. -
Engage your account team and partners: Schedule a regular cadence with your account manager, solutions architect, and support team to discuss industry trends and cost-relevant services. Include AWS Partners where they bring specialized expertise.
-
Attend events and meetups: Attend AWS summits, local meetups, and virtual events to hear how AWS experts and other customers apply new services to reduce cost.
-
Evaluate and pilot promising services: For the few releases that could materially cut cost, run a focused evaluation or pilot before committing, weighing migration and operating effort against expected savings.
Resources
Related best practices:
Related documents:
Related examples:
Related workshops: