Cyber resilience on AWS: A reference approach for recovery from ransomware and destructive events
The article discusses cyber resilience on AWS, focusing on recovery strategies from ransomware and destructive events. It emphasizes the importance of isolating recovery environments from production to ensure safety and integrity. The authors outline a reference approach that includes using separate AWS accounts and logically air-gapped vaults for secure backup storage.
- ▪Cyber resilience is the ability to recover workloads to a known-good state after an adversary has affected the environment.
- ▪The recovery environment must not share a trust boundary with the production environment to ensure safety during recovery.
- ▪AWS Backup provides logically air-gapped vaults that offer deletion protection for backup storage.
AWS Architecture Blog files mainly under programming. We currently carry 6 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | AWS Architecture Blog |
| Canonical URL | https://aws.amazon.com/blogs/architecture/cyber-resilience-on-aws-a-reference-approach-for-recovery-from-ransomware-and-destructive-events/ |
| Publication time | Wed, 20 May 2026 17:32:57 +0000 |
| Retrieval time | 2026-05-20T17:35:02.741Z |
| Last seen | 2026-05-20T17:35:02.741Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | zUJLT8QDT8zr |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Cyber resilience on AWS: A reference approach for recovery from ransomware and destructive events by Ashish Panwar, Kanniah Vagathupatti Jaikumar, and Rakesh Singh on 20 MAY 2026 in Amazon GuardDuty, AWS Backup, Best Practices, Resilience, Thought Leadership Permalink Comments Share Cyber resilience is the ability to recover workloads to a known-good state after an adversary has affected the environment. Prevention works to keep threat actors out and detection works to find them quickly. Cyber resilience focuses on recovery: restoring a trustworthy environment when backups, credentials, or parts of the infrastructure can no longer be assumed to be safe.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at AWS Architecture Blog.
Discussion
0 commentsMore from AWS Architecture Blog
