In this Meetup, Speaker walked us through the below AWS Route 53 Concepts: - What is DNS - How does DNS work? - DNS Record types - Routing Policies - MuleSoft vanity domain mapping - Load distribution of MuleSoft APIs - Failover Scenario - Disaster Recovery

1. 17 September 2022, 11:00 IST
Coimbatore MuleSoft Meetup
AWS Route 53 with Mulesoft

2. Safe Harbour Statement
● Both the speaker and the host are organizing this meet-up in individual capacity only. We are
not representing our companies here.
● This presentation is strictly for learning purposes only. Organizer/Presenter do not hold any
responsibility that same solution will work for your business requirements.
● This presentation is not meant for any promotional activities.
2

3. A recording of this meetup will be uploaded to events page within 24 hours.
Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab.
Make it more Interactive!!!
Give us feedback! Rate this meetup session by filling feedback form at the end of the day.
We Love Feedbacks!!! Its Bread & Butter for Meetup.
Housekeeping
3

4. 4
Coimbatore MuleSoft Meetup Group
Organizers

5. 5
About the Speaker:
● 14 years of experience in design, development and deployment of
Mulesoft and Java-based applications.
● Mulesoft Certified Integration and Platform Architect
● AWS Certified Solutions Architect - Associate
Introductions

6. 6
● What is DNS
● How does DNS work?
● DNS Record types
● AWS Route 53 - Introduction and Routing Policies
● Mulesoft vanity domain mapping
● Load distribution of Mulesoft APIs
● Failover Scenario - DR
● Demo
● Q&A and then Quiz for all participants
● Discussion for next Meetup, Stay connected, and Happy Learning.
Agenda

7. AWS Route 53 with Mulesoft

8. Domain Name System (DNS)

9. What is DNS?
9
1. The Domain Name System (DNS) is
the phonebook of the Internet
1. DNS translates domain names to IP
addresses. E.g amazon.com to the
IP address - 205.251.242.103

10. 10
How does DNS
work?

11. DNS Record Types
1. A Record - This is the most fundamental type of DNS record It holds the IP address of a given
domain. A records only hold IPv4 addresses
1. AAAA Record - The record that contains the IPv6 address for a domain
1. CNAME Record - Canonical name (CNAME) records maps one domain or subdomain to
another domain. All CNAME records must point to a domain, never to an IP address.
1. NS Record - Nameserver (NS) records tells the internet where to go to find out the domain’s
IP address. It indicates which DNS server is authoritative for that domain.
1. SOA Record - Start of Authority (SOA) record stores admin information about a domain e.g
the email address of the administrator
11

12. AWS Route 53

13. AWS Route 53 - Introduction
1. Highly available, reliable and scalable domain name system provided by AWS
1. The 3 main functionalities offered by Route 53 -
a. Domain name registration
Provides interface to buy and register a domain name for a server/website
b. DNS resolution
Provides hosted zone capabilities to host records for a given domain
c. Health Checks
Health checks can be configured to ensure that the resources connected through Route
53 are up and running.
13

14. AWS Route 53 - Routing Policies
1. Simple Routing - Route traffic to a single resource
1. Multivalue Answer Routing - Returns upto to 8 healthy records based on health checks
1. Weighted Routing - Route traffic based on the weight assigned to each record
1. Failover Routing - Support for an active-passive failover mechanism
1. Geolocation Routing - Traffic is served based on the geolocation of the client/user
1. Geoproximity routing - Traffic is served based on the geographic proximity of a user with a
resource
1. Latency Routing - Traffic is served from the resource that provides the lowest latency to the
calling client/user
14

15. Simple Routing
1. Simple Routing is typically used to configure routing for a single resource
1. You cannot create multiple records that have the same name and type
1. You can specify multiple values for a given record.
1. If multiple values are specified, then Route 53 returns all the values in a random order. The
client/user then selects any of the IP address and sends the further query
1. Health checks cannot be used for Simple Routing policy
15

16. Multivalue Answer Routing
1. Returns upto 8 healthy records
1. Health checks can be associated with the records
1. Support only A records, not CNAME records
16

17. Weighted Routing
1. Multiple resources can be associated with a single domain or a subdomain
1. Traffic flow can be configured by assigning a weight for each resource. The weight an be a
number between 0 and 255
1. Ideal for canary deployment model. For e.g.- If you want to release version 2 of an API only to
5%of the users and the rest of the users should continue using version 2.
17

18. Failover Routing
1. Uses the concept of Primary and Secondary
resource
1. When the primary resource is healthy, all the
traffic is routed to it. When the primary
resource is unhealthy, all the traffic gets
automatically directed to the secondary
resource
1. Health check is mandatory to be associated
with the primary record
1. Ideal for Active-Passive disaster recovery
scenario
18

19. Geolocation Routing
1. Helps to choose resources to serve traffic based on the geographic location of the user/client.
For e.g. We can have all the traffic originating from India served by resource A and all the
traffic originating from the UK served by resource B
1. Geographic locations can be set at the continent,country or states(in case of US) level
1. Useful for localised content delivery and delivery of content based on distribution rights
19

20. Geoproximity Routing
1. Routes traffic based on the geoproximity of users and resources
1. A bias value can be defined to route more or less traffic
1. Typically used when when you want to route traffic based on the location of your resources
and, optionally, shift traffic from resources in one location to resources in another.
Bias - 0 for Resource 1 Bias 60 for Resource 1
20

21. Latency Routing
1. Helps to route traffic to the resources in AWS
region which have the lowest latency from the
client/user
1. Latency records need to be created in multiple
AWS regions
1. Route 53 automatically determines the route
with the lowest latency
1. Typically used when you have resources in
multiple AWS Regions and you want to route
traffic to the region that provides the best
latency.
21

22. Mulesoft with AWS Route 53

23. Mulesoft DLB vanity domain mapping
1. A DLB in Anypoint Platform has a DNS name in the form - <DLBName>.lb.anypointdns.net
1. Mulesoft customers typically wants their clients to access Mulesoft APIs using their own DNS
names and not by the default DNS name of the DLB. This can be achieved by CNAME
mapping of vanity domain name of the client with that of the Anypoint DNS of the DLB
e.g The CNAME record below will map the vanity domain sg.vaibhavpatkar.co.in with the
Mulesoft Anypoint DLB sg-dlb.lb.anypointdns.net
23

24. Load distribution of Mulesoft APIs
Mulesoft APIs can be deployed on multiple regions to leverage the benefits from the AWS routing
policies
1. Weighted Routing - Route traffic based on the weight assigned to each Mulesoft API
1. Geolocation Routing - Traffic is served based on the geolocation of the client/user invoking
the Mulesoft API
1. Geoproximity routing - Traffic is served based on the geographic proximity of a user with a
Mulesoft API
1. Latency Routing - Traffic is served from the Mulesoft API that provides the lowest latency to
the calling client/user
24

25. Failover Scenario - Disaster Recovery
1. The Failover Routing policy can be used to ensure that Mulesoft APIs follow the
active-passive model
1. In this model, one of the API will act as the primary API and serve all the traffic.
1. The other API(in another region), will act as the secondary API
1. Health checks can be configured in AWS Route 53 to constantly check the health of the
primary API.
1. Whenever, the primary API goes down due to any disaster, AWS Route 53 will automatically
route all the traffic to the secondary API, thereby providing an automatic DR
1. Once the issue with the primary API is fixed and the API is up, health checks will report the
primary API as healthy. This would cause the traffic to be redirected back to the primary API
25

26. Demo

27. Mulesoft Setup
27

28. AWS Route 53 Setup
1. Domain name registration
1. Managing non AWS Route 53 registered domain in AWS Route 53
1. Creation of public hosted Zone in AWS Route 53
1. Sample record creation and test
28

29. 29
● Map a new vanity domain name with Anypoint DLB
● Test the connectivity to the API using vanity domain name
Demo 1 - Mulesoft DLB vanity domain
mapping

30. 30
● Weighted Routing
● Geolocation Routing
● Failover routing
Demo 2 - Load distribution and Failover for
Mulesoft APIs

32. Take a stand !
18
● Nominate yourself for the next meetup speaker and suggest a topic as
well.

33. 20
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: https://meetups.mulesoft.com/coimbatore
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the
program
What’s next?

34. Quiz Time
Get ready to WIN a Special Gift from MuleSoft Community

35. Thank you