Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

AWS AI Watch posted an update

AWS Resilience Hub, the service for assessing and strengthening the resilience of workloads, has picked up three capabilities in one announcement. Platform engineering and SRE teams can now scope discovery with EKS labels, get generative AI analysis of application dependencies, and share resilience policies across accounts through AWS Organizations.

Why it matters

The labels are the tidy one: EKS labels within a namespace now work as a service input source, so a team's existing Kubernetes conventions decide which resources feed the failure mode analysis. Dependency insights is the AI entry, surfacing new dependencies, cross-Region links and unusual usage patterns from the discovered graph. Policy sharing closes the set: central teams define resilience policies once, apply them across multiple accounts, and get organisation-wide visibility of which services use each policy. All of this is AWS describing its own tooling, so 'unusual' is unusual by its definition. Still, resilience standards that span accounts beat every team inventing its own.

Discuss: When generative AI flags an odd dependency pattern, should that page a person or open a ticket? Where's your line between insight and noise?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.