Getting started with Amazon RDS on VMware - Amazon Relational Database Service on VMware

Getting started with Amazon RDS on VMware

To get started with Amazon RDS on VMware, you onboard a new vSphere cluster as a custom Availability Zone (custom AZ) for Amazon RDS.

You only onboard a particular vSphere cluster once. After you complete the onboarding tasks successfully, you don't need to repeat the tasks for the same vSphere cluster. If you have already configured the vSphere cluster for Amazon RDS on VMware, and you want to add another custom AZ to it, see Creating additional custom AZs in an AWS Region.

During onboarding, you configure the following networks.

Network name Purpose DHCP server required?
Cluster Control Network New network for communication between Amazon RDS management virtual machines (VMs) and database VMs No. Amazon RDS runs its own Dynamic Host Configuration Protocol (DHCP) server on this network.
Internet Network New or existing network for outbound internet connectivity for Amazon RDS VMs and for establishing an HTTPS connection to the Amazon RDS service Yes. This network must advertise a default route.
Application Network New or existing network for communication between your applications and Amazon RDS database VMs Yes. This network can advertise a default route, but the corresponding default route is not installed.
Management Network Existing network for communication between Amazon RDS management VMs and ESXi hosts No. You must provide a static IP address during onboarding.

The following illustration shows how your Amazon RDS on VMware configuration looks after onboarding is complete.

RDS on VMware configuration
Important

Currently, Amazon RDS on VMware is available only in the US East (N. Virginia) AWS Region.

To create a custom AZ, you take the following two steps:

For more details about working with Amazon RDS on VMware, see Working with Amazon RDS on VMware.