AWS re:Invent 2025 - Version lifecycle management at scale with AWS Health (SPS326)

Comprehensive Summary: AWS re:Invent 2025 - Version Lifecycle Management at Scale with AWS Health

Understanding Lifecycle Events in the Cloud

• Three main types of lifecycle events discussed:
  1. Routine Changes: Predictable timelines, e.g. EKS version deprecation with 14 months of standard support
  2. Non-Routine Changes: Less predictable timelines, e.g. hardware retirements
  3. Urgent Changes: Short notice changes, e.g. security patches that need rapid rollout
• Lifecycle events are necessary to:
  • Improve service performance
  • Enable new features
  • Enhance security
  • Keep infrastructure up-to-date

Challenges of Managing Lifecycle Events at Scale

• As organizations grow, managing lifecycle events becomes increasingly complex:
  • Startups/SMBs: Manageable with manual processes
  • Growth Stage: Email notifications become unreliable, need better visibility
  • Enterprise: Siloed teams, competing priorities, technical debt from acquisitions
• Key challenges include:
  • Visibility into upcoming changes across thousands of resources
  • Coordinating action across distributed teams
  • Prioritizing lifecycle management vs. delivering new features

AWS Health for Lifecycle Event Management

• AWS Health is a platform that communicates events impacting AWS resources to customers
• Key features for lifecycle event management:
  • Planned Lifecycle Events: Specific event type designed for programmatic management
  • Resource Specificity: Events include full ARN for affected resources
  • Dynamic Burndown: Status tracking of pending vs. resolved actions
  • Advance Notifications: Up to 1 year notice for upcoming changes
• Health Maturity Model:
  1. Reactive: Manual processes, email notifications
  2. Programmatic: Ingesting Health events into operational tools
  3. Automated Assignment: Linking resources to owners, auto-creating tasks
  4. Workflow Integration: Automating remediation steps, AI-driven prioritization

BMW's Lifecycle Management Solution with AWS Health and ServiceNow

• BMW manages 10,000 AWS accounts supporting 23M connected vehicles
• Implemented a comprehensive solution leveraging AWS Health and ServiceNow:
  • Daily ingestion of Health events into S3 and data hub
  • Automated mapping of resources to owning teams/cost centers
  • Jira issue creation and dashboarding per team
  • Automated escalations for unresolved items
• Results:
  • 96% of RDS and 98% of EKS resources upgraded on time
  • Significant cost savings from reduced extended support
  • 90% reduction in overhead for lifecycle management team
  • Improved developer satisfaction through autonomy and accountability

ServiceNow Integration for Lifecycle Event Management

• New AWS Health and ServiceNow integration announced
• Automatically ingests Health events, maps to business context:
  • Identifies affected applications, services, and business processes
  • Auto-creates change requests and tasks for remediation
  • Assigns ownership based on resource metadata
• Provides single pane of glass visibility:
  • Breakdown of impacted resources, services, and business impact
  • Automated change management workflows
  • Traceability between technical infrastructure and business applications

Key Takeaways

• Lifecycle event management is critical as cloud adoption scales
• AWS Health provides programmatic tools to manage events at scale
• Integrating Health data with ITSM platforms like ServiceNow enables:
  • Automated assignment of responsibilities
  • Visibility into business impact of changes
  • Streamlined remediation workflows
• Solutions like BMW's demonstrate 90%+ reductions in overhead
• New AWS Health and ServiceNow integration simplifies this integration