October 13th, 2022

Machine translation is used partially for this article. See the Japanese version for the original article.

Introduction

We tried connecting to an HA cluster based on DNS name control using Amazon Route 53 Resolver (hereinafter called "Route 53 Resolver") on Amazon Web Services (hereinafter called "AWS").

Route 53 Resolver is a feature released in November 2018 that enables the name resolution between on-premises environment (such as in-house servers) and Amazon Virtual Private Cloud (hereinafter called "VPC").

When connecting from an on-premises environment to an HA cluster based on DNS name control on AWS, the name resolution from the on-premises environment to AWS is required.
This time, we used a VPC in the Singapore region as a pseudo environment of an on-premises environment, connected to a VPC in the N. Virginia region via VPN, and tried the name resolution using a Route 53 Resolver.

This time, we will explain an overview of how to connect to the HA cluster and its configuration.
For building procedure of the HA cluster, see this article.

Contents

1. Configuration of an HA Cluster Based on DNS Name Control

This HA cluster configuration uses the AWS DNS resources introduced in the previous blog.

In EXPRESSCLUSTER blog, we have introduced an HA cluster based on DNS name control as a directly accessing the HA cluster on AWS from an on-premises environment (such as in-house servers) using AWS Direct Connect.
In an HA cluster based on DNS name control, the connection destination to the active server is switched by rewriting the record registered in the private hosted zone in Amazon Route 53 (hereinafter called "Route 53").

However, we cannot perform the name resolution to the record registered in the private hosted zone in Route 53 directly from the on-premises environment, so we need to prepare a DNS forwarder in a VPC separately.

2. What is Route 53 Resolver?

As mentioned above, the Route 53 Resolver is a feature that enables the name resolution between the on-premises environment and the VPC.
Route 53 Resolver allows to resolve domain name in the VPC from the on-premises environment, and domain name in the on-premises environment from the VPC.

2.1 Name Resolution Using a DNS

Before the release of Route 53 Resolver, when we perform the name resolution to the record registered in the private hosted zone in Route 53 from the on-premises environment, it was necessary to build a DNS server or prepare SimpleAD in the VPC.

2.2 Name Resolution Using a Route 53 Resolver

Using a Route 53 Resolver, we can perform the name resolution from the on-premises environment without preparing a DNS server in the VPC.

3. HA Cluster Configuration

This time, we build an "HA cluster based on DNS name control" in the N. Virginia region.
Also, we build client machine in the Singapore region as a pseudo environment of an on-premises environment, and connect the Singapore region and the N. Virginia region VPCs via VPN.
The configuration is as follows:

Conclusion

This time, we explained an overview of how to connect to the HA cluster and its configuration.
For building procedure of the HA cluster, see this article.

If you consider introducing the configuration described in this article, you can perform a validation with the trial module of EXPRESSCLUSTER. Please do not hesitate to contact us if you have any questions.