The AWS exam guide outlines that 15% of the SysOps Administrator–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.

Course Objectives

• 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

Intended Audience

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.

Prerequisites

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

If you have thoughts or suggestions for this course, please contact Cloud Academy at support@cloudacademy.com.

So we've made it to service number three on our AWS high availability top 10. Elastic IP Addresses. Now, elastic IP addresses are public IP addresses that can be programatically mapped between instances within a region. They are associated with the AWS account, and not with a specific instance or lifetime of an instance. Elastic IP addresses can be used to work around host or availability zone failures by quickly remapping the address to another running instance, or a replacement instance, that was just started. To use an elastic IP address, you first allocate one to your account, and then associate it with your instance, or a network interface. You can allocate up to five elastic IP addresses fer VPC per region. If you need to increase this limit, you submit a request to AWS support. When you associate an elastic IP address with an instance, or its primary network interface, the instance's public IP address is released. You cannot reuse a public IP address. You can dissociate an elastic IP address from a resource and reassociate it with a different resource. A dissociated elastic IP address remains allocated to your account until you explicitly release it. There is a small hourly charge if an elastic IP address is not associated with a running instance or if it is associated with a stopped instance or an unattached network interface. This practice is to discourage people from reserving a large number of IP addresses. An elastic IP address is for use in a specific region only.