111917907-4698e300-8a7a-11eb-8152-a46b5d0a45cd.jpeg

The AWS learning challenge continues. This week was about Route53 which is literally the first time I touch this service and then some deeper dive into VPCs. Route53 gives a lot of flexibility and customisation but it is quite expensive for buying new domains and also you have to pay to transfer your domain which was a bummer. Nevertheless I gave it a try and it now makes a lot of sense.

Afterwards, in the VPC section there were some a bit advanced topic which I have to admit are difficult to make sense in a tweet. One of the biggest advantages I have seen so far is that it is a lot easier to follow devops related conversations and understand why certain decisions were made. Enough with me blabbing let’s go to the content.

Route53

Let’s talk about AWS Route53

It is a managed DNS (Domain Name System) service which contains a collection of rules and records for reaching a server through its domain name

The most common records include

CNAME vs Alias

Let’s do a comparison of when to use CNAME vs Alias in AWS Route53

AWS resources expose a hostname that looks like

http://abc-123.eu-west-2.elb.amazonaws.com. You want that to point to http://yoursite.example.com

The CNAME points a hostname to another hostname. Only for non root domains

Powered by Fruition