AWS prescriptive-guidance documentation change
Summary
Updated introduction content with new narrative about startup challenges and resilience benefits, expanded explanations of shared responsibility model, and refreshed guidance positioning
Security assessment
The changes focus on improving narrative flow, clarifying resilience concepts, and updating references - but do not address any specific security vulnerabilities or weaknesses. While mentioning the shared responsibility model relates to security practices, this is an existing concept being explained more thoroughly rather than new security documentation.
Diff
diff --git a/prescriptive-guidance/latest/startup-resiliency-baseline/introduction.md b/prescriptive-guidance/latest/startup-resiliency-baseline/introduction.md index 178a2a1b1..a3e4b581b 100644 --- a//prescriptive-guidance/latest/startup-resiliency-baseline/introduction.md +++ b//prescriptive-guidance/latest/startup-resiliency-baseline/introduction.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Startup Resiliency Baseline (AWS SRB)](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Startup Resiliency Baseline](introduction.html) @@ -7 +7 @@ Scope of guidanceShared responsibility model -# AWS Startup Resiliency Baseline (AWS SRB) +# AWS Startup Resiliency Baseline @@ -11 +11 @@ _Amazon Web Services_ ([contributors](./contributors.html)) -_January 2024_ ([document history](./doc-history.html)) +_March 2026_ ([document history](./doc-history.html)) @@ -13 +13 @@ _January 2024_ ([document history](./doc-history.html)) -_Resiliency_ is an application's ability to resist or recover from disruptions. For startups, resiliency is crucial. They are expected to provide always-available systems that operate in the always-on cloud. While agility and speed are key competitive advantages for early-stage companies, workload disruptions can quickly derail progress. Disruptions affect customers, reduce revenue, and harm reputations. +Every startup founder knows the tension: the team is racing to ship new features while customers expect every release to just work. You wake up to a notification about last night's outage, customer complaints are flowing in, and your roadmap is already packed with promised features. This is the daily reality for startups—balancing the pressure to innovate with the need to maintain stable services. @@ -15 +15,7 @@ _Resiliency_ is an application's ability to resist or recover from disruptions. -By proactively incorporating resiliency into initial architecture designs, startups can continue innovating at speed while avoiding the pitfalls of downtime. The AWS Startup Resiliency Baseline (AWS SRB) provides prescriptive guidance that is designed specifically for startups that are ready to build a resilient foundation on AWS, without sacrificing velocity. The AWS SRB combines foundational best practices with guidance that is tailored to common startup workloads. It also outlines the guardrails that startups need in order to rapidly scale on AWS with confidence. +The instinct to prioritize new features is natural. Investors want growth, customers ask for more capabilities, and competitors aren't standing still. Yet experience shows that resilience problems can derail even the most innovative startups. A service disruption doesn't just mean lost revenue; it erodes the trust you've worked so hard to build with your customers. In fact, rock-solid reliability can become your silent differentiator in a crowded market. + +Building resilience into your startup doesn't mean slowing down or massive infrastructure investments. It's about making smart choices early that prevent problems later. Think of it like building a house. It's much easier to put in a solid foundation at the start than to fix structural issues once everything is built. By weaving resilient practices into your initial architecture and operations, you create a competitive advantage. You're not just delivering a product; you're delivering a reliable experience that builds customer loyalty. + +The AWS Startup Resiliency Baseline (AWS SRB) was created specifically for teams facing this challenge. It provides a practical path to build reliability into your systems while maintaining the speed that makes startups special. No heavy processes or enterprise-scale complexity, just practical patterns that grow with your business. + +This guide describes how to implement the AWS SRB in a startup environment. It helps you identify what really matters for resilience, where to focus your limited resources, and how to build practices that scale as your company grows. @@ -19 +25 @@ By proactively incorporating resiliency into initial architecture designs, start -The AWS SRB is aligned with the [resilience lifecycle framework](https://docs.aws.amazon.com/prescriptive-guidance/latest/resilience-lifecycle-framework/introduction.html). It helps startups implement resiliency foundations, with minimal development effort, as they deploy their first applications on AWS. +When exploring the practical steps of building startup resilience, it's important to understand where this guidance fits within your organization's broader growth trajectory. The AWS Startup Resiliency Baseline is aligned with the [resilience lifecycle framework](https://docs.aws.amazon.com/prescriptive-guidance/latest/resilience-lifecycle-framework/introduction.html). It serves as an initial roadmap, designed to help you implement fundamental resilience measures with minimal development overhead as you deploy your first applications on AWS. Think of it as your starter kit for building reliable systems that can recover effectively from disruptions. @@ -21 +27 @@ The AWS SRB is aligned with the [resilience lifecycle framework](https://docs.aw -This document does not comprehensively cover all resiliency resources and tools available in AWS. Startups operating at a later stage of maturity should review additional resources for a comprehensive understanding of resilience best practices on AWS. For example, the [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) is a helpful next resource. It can help you build a secure, high-performing, resilient, and efficient infrastructure for your applications and workloads. Assess your adherence to these best practices by using the [AWS Well-Architected Tool](https://console.aws.amazon.com/wellarchitected/) in your AWS account. +The [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) and this resilience guidance complement each other to help you build secure and reliable infrastructure. This guide dives deeper into resilience practices while the AWS Well-Architected Framework provides a broader set of architectural best practices. You can assess your architecture against these practices using the [AWS Well-Architected Tool](https://docs.aws.amazon.com/wellarchitected/latest/userguide/intro.html) in your AWS account. @@ -25 +31,7 @@ This document does not comprehensively cover all resiliency resources and tools -Resilience is a shared responsibility between AWS and its customers, according to the [shared responsibility model](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/shared-responsibility-model-for-resiliency.html). AWS is responsible for resilience of the underlying cloud infrastructure that runs AWS services. Customers are responsible for the resilience of the AWS services that they deploy in the AWS Cloud. Implementing the resilience guidance prescribed in this document falls under the customer's responsibility when using AWS. By following best practices for resilience, customers can build reliable applications on AWS that recover gracefully from disruptions. +It's critical to clarify an important aspect of building resilient systems in the cloud: the partnership between AWS and your startup. Resilience in the cloud operates on a [shared responsibility model](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/shared-responsibility-model-for-resiliency.html), with AWS and your team each playing distinct roles in ensuring system resilience. + +AWS takes responsibility for the resilience of the underlying cloud infrastructure that powers their services. Think of this as the foundation upon which you build your applications. This includes maintaining the resilience of data centers, networking components, and the core AWS services you use in your architecture. + +Your startup's responsibility focuses on the resilience of the systems you build and deploy on this foundation. The recommendations in this guide fall within your domain of responsibility. By implementing these practices thoughtfully, you can create applications that use reliable AWS infrastructure and incorporate robust recovery capabilities. + +This model means you're never building resilience in isolation. You're building upon a proven, reliable foundation while focusing your efforts on the aspects that directly impact your customers and business operations. This guide explores how to make the most of this shared responsibility model, using reliable AWS infrastructure while implementing practical measures to make sure that your applications recover gracefully from disruptions.