NAT Gateways can auto scale upto 10 Gbps.
Flow logs per single network interface, single subnet, or single VPC in a region = 2
VPCs per region = 5
Elastic IP addresses per region = 5
We will configure and demo the use of CloudFront with an S3 bucket as the origin. This note assumes that you have setup your AWS account and are familiar with using S3.
Steps:
Create an S3 bucket in a region far from your region, keeping all defaults.
We already created a EC2 server setup and tried few routing policies. We deleted those A records. We will create one with failover policy now. We will also need to create health check within route 53 for this. This policy lets you chose where traffic will be sent based on geographical location of users.
Steps:
We already created a EC2 server setup and tried few routing policies. We deleted those A records. We will create one with failover policy now. We will also need to create health check within route 53 for this. Use this policy when you want an active/passive setup.
Copy your ELB dns address and go back to Route 53
We already created a EC2 server setup and configured and uses simple routing policy. We deleted those A records. We will create one with latency policy now. This policy allows you to route based on lowest latency for end user (e.g. which region will give fastest response time).
We already created a EC2 server setup and configured and uses simple routing policy. We deleted the A record that specified simple routing. We will create one with weighted policy now. In this policy, requests for your domain that come to Route 53 will be forwarded to different regions or even different ELBs based on weight specified.
We will create an EC2 server setup and configure and use simple routing policy in first part of this lab. For continuity and incurring less cost, it is better you do all the five parts of this lab together.
Login to AWS console and go to Route 53.
Amazon Route 53 is a DNS web service that effectively connects user requests to infrastructure running in AWS such as EC2 instances, ELB load balancers, or S3 buckets. It can also be used to route users to infrastructure outside of AWS.
Route 53 is designed to be extremely reliable, highly available, scalable and cost effective. Amazon Route 53 is fully compliant with IPv6 as well.
Please first use the contact form or facebook page messaging to connect.
Offline ContactComplete the form below, and we'll send you an e-mail every now and again with all the latest news.
CloudMaterials is my blog to share notes and learning materials on Cloud and Data Analytics. My current focus is on Microsoft Azure and Amazon Web Services (AWS).
I like to write and I try to document what I learn to share with others. I believe that knowledge is useless unless you share it; the more you share, the more you learn.
Recent comments