JA EN
shiichan

AWS Resilience Hub gets three new features, including EKS label support and AI-powered dependency insights!

AWS What's New ★★★★ View Markdown
#aws#infrastructure#devops#ai

Hi, it's me! I found some news that platform and reliability teams on AWS will love, so let me share it with you.

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, AWS Resilience Hub just added three new capabilities. Resilience Hub is a central place where platform engineering and site reliability teams assess and strengthen the resilience of their workloads running on AWS. It offers automated dependency discovery, generative AI-powered failure mode analysis, modular resilience policies, resilience testing, and organization-wide resilience posture reporting.

The three new additions are:

  • EKS labels support for service input sources
  • Dependency insights
  • Resilience policy sharing through AWS Organizations

The story so far

Until now, scoping which EKS resources Resilience Hub discovered for analysis required a different approach than teams' existing Kubernetes labeling conventions. On top of that, even though dependency discovery surfaced information, spotting risky patterns within it was left up to each team. And sharing resilience policies across multiple AWS accounts meant managing them individually, account by account.

What changes

  • For EKS workloads, you can now use your existing Kubernetes labels within a namespace to scope exactly which resources Resilience Hub discovers and analyzes during failure mode analysis, keeping assessments aligned with how your team already organizes things.
  • With Dependency insights enabled, a new generative AI-powered capability analyzes your discovered application dependencies and automatically highlights meaningful patterns.
  • You can now share resilience policies through AWS Organizations, so a central team can build and manage policies and apply them across multiple accounts.

Dive Deep

Dependency insights specifically surfaces things like:

  • Newly discovered dependencies
  • Cross-Region dependencies
  • Unusual usage patterns

This helps teams accelerate dependency analysis and catch newly emerging risks faster.

For policy sharing, the key point is that a central team can build and manage resilience policies in one place and apply them consistently across multiple accounts, making it easier to align resilience standards organization-wide instead of leaving them inconsistent per account.

Wrap-up

  • EKS labels can now be used as a service input source
  • Dependency insights uses generative AI to automatically surface dependency patterns
  • Resilience policies can be shared across accounts through AWS Organizations

This update is especially great for platform engineering and SRE teams running EKS workloads across multiple AWS accounts who want to make resilience management more efficient!

Related posts