Aurora RDS Download


Solve AWS RDS and DNS Names in VPN Networks

If you are interested in Aurora RDS Download, you are familiar with RDS Endpoints. This is a random string that points to the main host where your database server is hosted. The reason AWS provides this endpoint is that the failover IP Servers from the database server will change. Instead of using a virtual / floating IP address, they use this type of DNS name. 

Thus, during failover, they update the new master IP address on the DNS server. And this end point is solved by internal and external networks. Previously, we were preparing many Replicas from RDS to the On-Prem platform or cross-clouds like Azure and GCP. However, the replication connection is made through the public internet. Because endpoints cannot finish Private IP. But we have a few solutions to make this possible.

• Use Unlimited to appear as your DNS successor.
• Use the AWS Directory service (Simple Ads).
• Use AWS (Microsoft AD) Directory Services.
• Central DNS management.

However, the effort to configure this is not small and is time consuming. I recently had the opportunity to copy Aurora to a GCP VM. I use R53 instead of configuring the solution mentioned above. AWS recently announced that we could use Route53 for Hybrid DNS solutions through the Managed VPN and Direct Connect. There is only 5 minutes of work to adjust this. Before starting this tutorial, be sure to configure the VPN between AWS and GCP. This returns the Generic IP from the Host 52.7.5.183. If you do not enable public access, it does not return anything in Aurora RDS Download.

Download Aurora RDS

RDS
Free Driver
Monitoring 
Free Driver

Now let's Set the Route53 Resolver

1. You must select the region where your RDS is started. In my case we are east.

2. Go to R53 → Solver → Start Point Point. I just need the GCP VM, I have to finish the RDS endpoint, I don't want anything else with it. So for me it's just a link that comes with RDS. That's why I chose the Incoming Endpoint.

3. Click Create Entry Endpoint.

4. Under VPC in Zone, select the VPC from which your RDS instance started.

5. And then this R53 endpoint will not automatically allow all traffic. We may limit who can use this 
Analyzer to resolve DNS names. So I've created a security group and I've allowed port 53 of my GCP Virtual Machine.

6. AWS uses this endpoint in the availability zone 2 to ensure high availability. In IP Address # 1, grant AZ and subnet for the first DNS endpoint. Select AZ for # 2 and a different subnet.
Make sure that the 2 subnets you selected are connected to the Route table to which the VGW is connected. If not, it won't work.

7. Click the Submit button. Let's wait to spread. Then use the IP address of the DNS resolvers in your VM. I want to play more. From this setting, I manually added the parser to the VM. You can use the startup script to add this line when starting instances. Or find a way to use it for existing examples without adding them manually. Check the ElasticSearch endpoint, the internal load balancer endpoint, or everything that can be completed, such as S3 with Aurora RDS Download.

Discussion: