Designing for high availability, fault tolerance and cost efficiency
AWS Services That Enable High Availability
Knowledge Check Point
The AWS exam guide outlines that 60% of the Solutions Architect–Associate exam questions could be on the topic of designing highly-available, fault-tolerant, cost-efficient, scalable systems. This course teaches you to recognize and explain the core architecture principles of high availability, fault tolerance, and cost optimization. We then step through the core AWS components that can enable highly available solutions when used together so you can recognize and explain how to design and monitor highly available, cost efficient, fault tolerant, scalable systems.
- Identify and recognize cloud architecture considerations such as functional components and effective designs
- Define best practices for planning, designing, and monitoring in the cloud
- Develop to client specifications, including pricing and cost
- Evaluate architectural trade-off decisions when building for the cloud
- Apply best practices for elasticity and scalability concepts to your builds
- Integrate with existing development environments
This course is for anyone preparing for the Solutions Architect–Associate for AWS certification exam. We assume you have some existing knowledge and familiarity with AWS, and are specifically looking to get ready to take the certification exam.
Basic knowledge of core AWS functionality. If you haven't already completed it, we recommend our Fundamentals of AWS Learning Path. We also recommend completing the other courses, quizzes, and labs in the Solutions Architect–Associate for AWS certification learning path.
This Course Includes:
- 11 video lectures
- Detailed overview of the AWS services that enable high availability, cost efficiency, fault tolerance, and scalability
- A focus on designing systems in preparation for the certification exam
What You'll Learn
|Lecture Group||What you'll learn|
Designing for High availability, fault tolerance and cost efficiency
Designing for business continuity
How to combine AWS services together to create highly available, cost efficient, fault tolerant systems.
How to recognize and explain Recovery Time Objective and Recovery Point Objectives, and how to recognize and implement AWS solution designs to meet common RTO/RPO objectives
|Ten AWS Services That Enable High Availability||Regions and Availability Zones, VPCs, ELB, SQS, EC2, Route53, EIP, CloudWatch, and Auto Scaling|
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
- Hi Cloud Academy ninjas. Let's talk about autoscaling. Okay, now I get a lot of questions out in the field about, "Why did my autoscaling group suddenly stop?" So let's think this through, okay. Generally people reach a number, around 20, and they find that autoscaling will just pause. And I have enterprise customers who have gone from having two or three instances, which they've been running and enjoying, and then they go live and they're expecting to have 30 or 40 instances running to deal with the burst activity they have, and generally they get to 20 and then it pauses. So let's think through why that might be. Is it that autoscaling has a limit of 20 and then if you get above that it just pauses? How about it's to do with desired capacity number? If I've set a desired capacity number of 25 or 20, does that mean that autoscaling will stop when it gets to that number? Or is it perhaps due to a regional constraint, alright? Now this is one of the common questions I get asked a lot in the field, is that. Yeah, it's to do with a regional constraint, because by default, accounts have a limit of 20 EC2 instances they can start per day. So if your autoscale group sets itself beyond that 20 EC2 instance per day limit, then it's going to get to that ceiling and stop. Now it's easy to fix this problem. All you have to do is contact AWS support and let them know that your customer is going to need more than 20 instances. And then no problem, you can go up to 100, 150, whatever. Let them know that your customer's going to exceed that 20-a-day limit so that you know your customer's going to have a good experience from their Okay, see you next time.
- What is an SQS First In First Out Queue and when should I use it?
- Bastion Hosts and NAT Gateway
- Amazon SQS versus Amazon SNS - What is the Difference?
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.