All Notes
AWS
AWS
  • AIM
  • General Stuff about AWS
  • AWS Global Infrastructure
  • Interacting with AWS
  • AWS Identity and Access Management
    • AWS Organizations
    • Users
    • Policies and Permissions
    • Groups and Roles
    • Federation
    • Access Control (via available tools)
    • AWS Cognito
    • AWS IAM Identity Center
  • Networking and Content Delivery in AWS
    • AWS VPC
    • AWS Route 53
    • Elastic Load Balancing
    • AWS CloudFront
    • Amazon API Gateway
  • AWS Storage Services
    • Amazon EBS
    • Amazon EFS
    • Amazon FSx
    • S3
    • AWS Databases Services
      • Amazon RDS
      • Amazon DymanoDB
      • Amazon Elasticache
      • Amazon RedShift
      • Amazon DocumentDB
  • AWS Compute Services
    • EC2
    • Elastic BeanStalk
    • AWS Lambda
    • Container Services
      • ECR and ECS
      • EKS
      • AppRunner
  • Other AWS Services
    • CloudFormation
    • AWS Key Management Services (KMS)
    • AWS Secrets Manager
    • AWS Certificate Manager (ACM)
    • AWS Messaging Services
      • AWS SNS (Simple Notification Service)
      • AWS Simple Queue Service (SQS)
    • AWS Systems Manager
      • Application Management
      • Node Management
    • Logging and Monitoring
      • AWS CloudTrail
      • AWS CloudWatch
    • AWS Macie
    • AWS Inspector
    • AWS GuardDuty
Powered by GitBook
On this page
  1. Networking and Content Delivery in AWS

AWS Route 53

PreviousAWS VPCNextElastic Load Balancing

Last updated 1 year ago

Simply speaking, Domain Name System is a translation of a Domain Name to IP Address. Route 53 is Amazon's DNS Service. Some of its features are as follows:

  • Its a global service rather than regional service. It uses edge locations.

  • It can be used for global resource routing i.e., it can be sued to redirect the nearest server to a user based on region or country or the server with fastest response time.

  • Its highly available with almost zero downtime i.e., it provides failover capability to route the user to different server if the server nearest to them is down w/o the user knowing it.

Let's see how to get started with Route 53 to look into the following sub-services that are available with Route 53:

Route 53 after registering the domain can have various options as per the above features:

Hosted Zone

Let's suppose, we have registered a domain on Route 53 or any other domain registration website such as Bigrock or Godaddy or Namecheap. Now, one can purchase and register the domain at one place and can still definitely use AWS Hosted Zone to maintain the DNS records. This is done with the help of pointing the nameservers of the AWS at domain registration website, which can be done as shown below:

Now, there are two ways to create DNS record. One is one record at a time and one is zone wise i.e. by importing the zone file (filenameofrecords.zone). Let's look at the latter first.

To create a single record, the steps are as follows:

Now there is a concept of Alias records. These are not CNAME records but rather an AWS concept. They provide alternate Route 53 way to AWS services such as S3 or Elastic Load Balancers, CloudFront etc. One can simply set the alias record as shown below: