Summary - Domain One
Summary - Domain One - Designing Resilient Architectures
In this module, we introduced the concepts of high availability and fault tolerance and we learn how to recognize and explain how we go about designing highly available, fault-tolerant solutions on AWS.
We introduced and explained the concept of business continuity, the concept of a recovery point objective and a recovery time objective - and how AWS services can be effective enablers when designing for disaster recovery
We then learned to recognize and explain the core AWS services that when used together can reduce single points of failure and improve scalability in a multi-tier solution.
In our hands-on labs we created and worked with Auto Scaling groups to improve add elasticity and durability. We worked with Amazon Simple Queue service - a core service as it can increase resilience by acting as a messaging service between services and applications, thereby enabling us to decouple layers and reduce dependency on state.
Next, we had a hands-on introduction to Amazon CloudWatch monitoring service. Amazon CloudWatch is the “eyes and ears of your environment and an important component when designing a resilient architecture. Cloudwatch alarms and triggers can increase resilience by allowing you to react to changes and events - you can automate auto scaling based on predefined CloudWatch performance metrics.
Finally, we learned to apply the Amazon CloudWatch CDN service to add resilience to a static website served out of Amazon S3. Amazon Cloudfront is tightly integrated with other AWS services such as Amazon S3, AWS WAF and Amazon GuardDuty making Amazon CloudFront an important component to increasing the resilience of your solution.
- [Instructor] That concludes Designing Resilient Architectures, domain one of the Solution Architect Associate learning path. In this module, we introduce the concepts of high availability and fault tolerance. And we learned how to recognize and explain how we go about designing highly available fault tolerant solutions on AWS. We introduce and explain the concept of business continuity, and the concepts of a recovery point objective and a recovery time objective. And how AWS services can been effective enablers when designing for disaster recovery. We then learn how to recognize and explain the core AWS services that, when used together, can reduce single points of failure and improve scability and multi-tiered solution. In our hands-on labs, we created and work with auto-scaling groups to improve elasticity and durability. We work with Amazon Simple Queue Service, a core service, as it can increase resilience by acting as a messaging service between services and applications. Thereby enabling us to decouple layers and reduce dependency on state. Next, we had a hands-on introduction to Amazon Cloud Watch, the monitoring service. Amazon Cloud Watch is the eyes and the ears of your environment if you like. And it's an important component when designing a resilient architecture. Amazon Cloud Watch alarms and triggers can increase resilience by allowing you to react to changes and events. You can automate autoscaling based on predefined Cloud Watch performance metrics, for example.
- [Instructor #2] Next, we worked with Amazon CloudFront, the content delivery network, which can increase our durability by providing a caching layer that we can put in front of our solutions.
- [Instructor] Okay, great work. We know how to choose reliable/resilient storage. We can determine decoupling mechanisms using AWS services, we can determine how to design a multi-tier architecturural solution, and we can determine how to design highly available and/or fault tolerant architectures. If you have any questions or comments, or would like some help understanding the concepts we've covered, please reach out to us at email@example.com.
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.