Get an overview of AWS services and define which AWS services are most useful when building a DR environment.
- [Instructor] AWS launched the EC2 service back in 2008. EC2 is the standard VM, which is known as Infrastructure as a Service or IaaS. Limiting IaaS to a public cloud environment does not fully extract the value of AWS. The true value of the public cloud comes from the services offered that that abstract away the burden of managing the infrastructure. Gartner's Annual Magic Quadrant continues to maintain each year that Amazon is ahead of Microsoft and Google when it comes to the maturity of these platform services.
Hundreds of enhancements and new services are released each year by AWS. These services allow customers to more easily build and manage their environments. Here is a view of the AWS console, showing all the services currently offered. These are the managed services that are most important to building a DR environment. Let's dive it. The Amazon Machine Image, or AMI, is used to launch any EC2 instance for AWS's IaaS offering. AWS allows an organization to take full copies of any AMI and easily move them to a different region so that they can be launched in a DR scenario.
Snapshots can be taken of each EC2 instance or AMI and stored in a different region. Snapshots and AMIs are related but not the same. An AMI can be created from a snapshot, but a snapshot is not an AMI. AWS charges in gigabytes per month, but snapshots are compressed and only differential data of each snapshot results in charges. Simple Storage Service is AWS's object data storage service solution. It is infinitely scalable, meaning organizations can continue to add more data without worrying about needing to purchase additional capacity in advance.
S3 was one of the original services released by AWS, back in the spring of 2006. S3 is used to store snapshots, and S3 replication allows all objects within an S3 region to be automatically replicated to any other region. Relational Database Service, or RDS, is AWS's database management solution. AWS will manage updates, patching, backups, read replicas, and high availability for failovers. When a DB is launched, an endpoint will be provided to use with an application, and the rest is handled by AWS.
RDS allows an organization to easily back up and restore a DB to a different AWS region. A read replica can also be run in a different DR region to bring RPO to near zero. Another critical service to DR is Route 53, AWS's DNS service. It allows organizations to create public and private DNS zones, records, and routing policies. It also supports domain registration, advanced routing policies, and health checks. Route 53 supports DR through manual or automated changes to DNS, to point to a new environment, in the event of a disaster.
For automated changes, Route 53 has a number of features, such as failover routing, that can support automated DR failover. Finally, Cloud Formation is a complex service that allows an organization to manage entire AWS environments with code. All EC2 instances in platform services can be represented in Cloud Formation templates written in JSON or YAML. Imagine building an entire network of servers and all infrastructure inside of it. Now imagine a template that stores the exact details defining that infrastructure, the networking, the firewall rules, the servers, the S3 storage buckets, the Route 53 DNS records, and anything else that AWS supports.
An organization can launch and manage all of this inside of a template. For DR, this allows an organization to quickly build an environment using the Cloud Formation template in any AWS region. This makes DR much simpler because the infrastructure does not need to be manually created. The template handles everything.
- DR in the public cloud
- Recovery time objective (RTO)
- Recovery point objective (RPO)
- AWS platform services that support DR
- Comparing the four DR architectures
- Differences between high availability and DR
- Cold DR procedure
- Pilot light DR procedure
- Warm standby procedure
- Multisite DR failover