AWS Route 53 Inbound Resolver to resolve DNS for Multi Account Organization

By

Amazon Route53 Resolver

The route 53 resolvers are contactable IP addresses (endpoints) where the DNS queries from different sources can be directed. There are two types of resolvers that administrators can deploy.

Inbound Resolver

As the name says inbound (DNS Resolutions coming in) which will enable your resources in the on-prem network to resolve AWS resource domain names or records in a Route 53 private hosted zone by allowing your on-prem network DNS resolvers to forward queries to Route 53 Resolver.

Outbound Resolver

As the name says Outbound (DNS Resolutions going out) which will enable your AWS resources to resolve the domain names of your on-prem network resources using resolver rules, which would forward selected queries to the on-prem network DNS resolvers

On-prem to AWS DNS Resolution for Multi Account Organization Setup

In this blog, I will be explaining on how the DNS resolutions can be configured in a multi account organization setup. When we have a requirement to enable DNS query from On-premises to AWS Multi account organization with a cost effective solution then below design is the right one to choose.

Pre-Requisites

  • Ensure that there's network connectivity between your on-prem network and AWS via a VPN connection or Direct Connect.
  • Enable DNS host names and resolutions in the DNS support attributes in the VPC in which you would create the endpoint.
  • For the inbound endpoint, you would need a security group with inbound rules that allow incoming traffic from the on-prem network IP addresses via the following port:
    TCP/UDP 53

Architecture Workflow

When we have multi account Organization setup then each cloud consumers in your Organization will use a dedicated AWS account to deploy the workloads. As a platform engineering team, we have to ensure the account provided to cloud consumers adhere to security and compliance framework and also we have to design a cost effective solutions. 

In this blog, I will explain on how the DNS resolution can be made from on-premises to AWS Cloud using single Inbound Resolver. We know Route53 Resolver is an expensive service and just to host the service with few queries, you will cost around 186.50 USD assuming 2 ENIs and 10 million DNS query per month.
Its not feasible to create inbound resolver in each cloud consumers account keeping cost in mind. The proposed design will have one resolver endpoints created in shared services account with 2 ENIs, if you have high number of incoming queries then you can add additional ENIs to handle the threshold. You can add up to 6 ENIs for an inbound resolver.

Follow the below steps for implementing this design

Step 1: Create an Inbound Resolver in Shared Services Account

Login to Shared Services Account and navigate to Route53 service and create Inbound endpoints. As per the requirement, add IP Address between 2 to 6. Once we create the inbound endpoints, we get the IP Address from the given subnets, In my case, I got  allocated with10.0.0.11 and 10.0.0.24 IP addresses.

Step 2: Create a hosted zone for your domain

In Shared Services Account, navigate to Route 53 console and from the Hosted zone service create private hosted zone. In this example, I taken cloudsolutionsonline.com as my domain name in the hosted zone. As per your requirement, enter the domain that you want to route traffic for. Choose the Private hosted zone and select your VPC and create hosted zone.

Step 3: Create a hosted zone for your domain in spoke accounts

In spoke accounts, create a hosted zone with your desired name + your domain name which we created in the Step 2. So in my case, I created a hosted zone with name myhost1.cloudsolutionsonline.com, myhostn.cloudsolutionsonline.com respectively into multiple spoke accounts

Step 4: Create a records inside the hosted zone in spoke accounts

In Spoke accounts, from the created hosted zone, one can start creating the records for your applications or servers. To simplify in this example, I created few 'A' records to route to my respective server IPs. Below is my consolidated records in the spoke account hosted zones


Step 5: Authorize and Associate Shared Services VPC to the spoke hosted zones

While create the hosted zone, we associate its specific VPCs to the hosted zone, like spoke 1 VPC will be associated to spoke 1 hosted zone. Now, we have to associate Shared services account VPC to all spoke hosted zone via AWS CLI or SDK, currently cross account VPC and hosted zone association is not possible from the AWS console.

Run the below AWS CLI command to create the authorization and association

From Spoke Accounts:
aws route53 create-vpc-association-authorization --hosted-zone-id <hosted-zone-id> --vpc VPCRegion=<region>,VPCId=<vpc-id> --region <region>
From Shared Services Account:
aws route53 associate-vpc-with-hosted-zone --hosted-zone-id <hosted-zone-id> --vpc VPCRegion=<region>,VPCId=<vpc-id> --region <region>
For more details, checkout the AWS documentation for authorization and association 

Step 6: Create a conditional Forwarder in the on-prem DNS server

In On-prem DNS server, create a condition forwarder in the DNS server to route your hosted zone domain to Inbound endpoints. In my case, I will route cloudsolutionsonline.com to 10.0.0.11 or 10.0.0.24

From on-premises network, when we run nslookup or dig to the cloud records which we created, it gets resolved to the respective cloud servers.

Conclusion

In this blog post, I have shown you on how to configure DNS resolution from on-premises DNS to the records which we create in the spoke accounts in a cost effective way. Hope this blog helped you in your similar use case.

Thank you for reading!

Comments

Post a Comment

Popular posts from this blog

Connect to Linux EC2 Instance if Key pair is lost after Initial Launch

By
Use Case We know that EC2 Linux instances are accessible through the private keys by default. However, SSH is allowed but you cannot use SSH password authentication to access Linux instance as it is disabled by default. So, what would happen if you lose the private key of your Linux instance? In this blog, I will walk you through the easiest ways to login when you lost the Key pair What is a key-pair file? Key-pair is a combination of a public and private key. Amazon EC2 uses public-key cryptography to encrypt and decrypt login information. Private key is only the way to get access to the instance, what if you lost the key? Is your servers lost in black hole? Thankfully nothing is lost you still can access your server, let me show you how can you solve this problem. Things that you should know before to proceed to this topic This procedure will requires s
Read more

Setup Grafana on AWS EKS and integrate with AWS Cloudwatch

By
What is Grafana? Grafana is open-source visualization and analytics software. It allows you to query, visualize, alert on, and explore your metrics no matter where they are stored. In plain English, it provides you with tools to turn your time-series database (TSDB) data into beautiful graphs and visualizations. Setup Grafana on Amazon Elastic Kubernetes Service This blog explains on how to run Grafana on Amazon Elastic Kubernetes cluster and adding cloudwatch as datasource to Grafana. Using Grafana you can simplify Kubernetes monitoring dashboards from Clo
Read more

Start or Stop services in multiple Windows EC2 Instances using AWS Systems Manager

By
Use Case You are the admin over a large amount of EC2 instances and managing different AWS accounts under Organization and you have to start/stop/disable a service for all Windows EC2 Instances in the Organization. Rather than wasting labor hours to perform this activity in each instance manually, you want to automate the process using AWS Systems Manager. Recently Windows had a flaw in Print Spooler Remote Code Execution Vulnerability and Microsoft recommended to stop until the patch is applied, in order to apply this immediately, we can make use of this design Systems Manager Systems Manager (SSM) gives you visibility and control over your AWS infrastructure. Automation, a capability of AWS Systems Manager, simplifies common maintenance and deployment tasks of Amazon Elastic Compute Cloud (Amazon EC2) instances and other AWS resources. Automation helps you to do the following: Build automations to configure and manage instances and
Read more

Concourse CI Installation and Configuration in Windows

By
Introduction to Concourse Concourse is an open source CI/CD system with integration supported to Resource types in the outside world. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control. Install and Configure Concourse in Windows Follow the below Steps to Install Installing Docker Desktop is pretty simple, download the exe file and install the docker desktop Modify Docker daemon configuration file as below
Read more

Install SSM Agent in Amazon EC2 Instance

By
What is SSM Agent AWS Systems Manager Agent is a Amazon software which can be installed on Amazon EC2 Instances. If SSM Agent is Installed in the servers then it will be easy to manage the EC2 Instances through AWS Systems manager.  By default SSM agent is pre installed for below Amazon Machine Images Amazon Linux Amazon Linux 2 Amazon Linux 2 ECS-Optimized Base AMIs macOS 10.14.x (Mojave), 10.15.x (Catalina), and 11.x (Big Sur) SUSE Linux Enterprise Server (SLES) 12 and 15 Ubuntu Server 16.04, 18.04, and 20.04 Windows Server 2008-2012 R2 AMIs published in November 2016 or later Windows Server 2016 and 2019 In this blog, I will walk you through on the ways to Install SSM Agent in the Instances which will not get SSM Agent by default. Steps to Install S
Read more

Deploy AWS infrastructure using Terraform and GitHub Actions

By
Terraform being an Infrastructure as a Code helps us to manage a lot of infrastructure for several platforms in a consistent manner.  In this blog, I will walkthrough on deploying a terraform code using  Github actions Terraform code to create S3 bucket In this blog, I will walkthrough each blocks in terraform to create an S3 bucket in AWS in automated workflow using GitHub Actions. Lets look into the Terraform files. To understand easily, I have created separate tf files for each purpose, but you can still use all in one tf file as per your convenient. You can use any name with tf extension, for better understanding I used following names. versions.tf
Read more

Automate Permission Boundary Attachment to IAM roles and Users

By
When we are managing multiple AWS Accounts in an Organization and each accounts will have their own requirement but as a centralized admin, we should be having a certain governance and compliance framework. IAM is a widely used AWS service and IAM roles/users are common used entity in AWS. As a centralized Admin, when we provide access to create IAM roles, cloud consumers in the landing zone accounts would create Users and Roles and attach Administrative policy and bypass the governance framework. In this blog, I will be briefing on restricting this scenario using IAM permission boundary and also deploying this setup through automation. AWS supports permissions boundaries for IAM entities (users or roles). A permissions boundary is an advanced feature for using a managed policy to set the maximum permissions that an identity-based policy can grant to an IAM entity. An entity's permissions boundary allows
Read more

Import Existing Resources using Terraform

By
In this blog, I will walk you through the ways to import pre-existing cloud resources in terraform. Why Import is required? There will be a scenario, where you will have a stringent timeline to setup a cloud Infrastructure and it can lead to situations where infrastructure needs to be created manually due to time pressures, emergency releases or just the fact that the infrastructure exists, and terraform was never used in the first instance. In a worst case scenario, you can lose the terraform.tfstate file. Terraform import will be essential in most of all these scenarios. Let's Import With an understanding of why Import is required, let us begin by importing a simple AWS resource S3. Firstly, we need to setup the Terraform and AWS credentials locally, we will not go into the details of installing and setting AWS credentials in
Read more

Hosting AWS VPC Interface Endpoints in Shared Model

By
What is VPC Endpoint A VPC endpoint enables private connections between your VPC and supported AWS services. Endpoints are classified as Interface and Gateways endpoints. In this blog, I will be showing how to host interface endpoints in shared model Do you have Multi AWS Accounts in Organization? When you have multi accounts structure in your Organization then creating endpoints in each accounts will increase the costs and IPs, in this blog I will explain how you can deploy endpoints in Shared Services Account and associate the member accounts VPCs with Private Hosted zone. Below is the Architectural diagram which I will be showing in detail on how to setup and also how the flow works Architecture Design AWS Services/Components required VPC Subnets Endpoints Hosted zone and Record set Transit Gateway I
Read more