RDS on VMware helps your DBA to spend only a fraction of his time on routine management tasks, getting more time for new features and proactive tuning.
Simple interface for creating, modifying and managing different SQL database engines using Console, CLI or API suitable for different user profiles.
Manage sensitive database workloads with consistency, whether on-premises or in the cloud, to ensure you comply with all regulations.
Amazon RDS on VMware delivers AWS-managed relational database in on-premises VMware environments. Managing relational database is complex and time-consuming, and RDS on VMware makes it easy to setup, scale, and operate relational databases in your VMware vSphere clusters. RDS on VMware uses the same simple interface, AWS Management Console, which you can use to manage databases both on premises and in AWS.
RDS on VMware supports MySQL 5.7, PostgreSQL 10.9, and Microsoft SQL Server 2016 SP2 Enterprise Edition. For Microsoft SQL Server, customers will need to provide their own media and license (on-premises customer provided license).
Yes, you need to bring your own media and your own Microsoft SQL Server license (on-premises customer provided license) to create RDS on VMware managed Microsoft SQL Server databases.
To onboard RDS on VMware, you create a Custom Availability Zone from the AWS Management Console, in the AWS Region where you want to use the service. You then download the RDS on VMware installer from the AWS Management Console to the on-premises vSphere cluster where you want to use the service. When you run the installer, it deploys the local components for RDS on VMware on your vSphere cluster and connects your cluster to the Amazon RDS service running in the AWS Region. Once this process is complete, your newly created Custom Availability Zone will become “Active”. You can then create a new database using the AWS Management Console, CLI, or APIs by choosing the appropriate database engine and instance size. Please note that for Microsoft SQL Server, customers have to provide their own media and on-premises license to create the database.
RDS on VMware comprised of a set of VMs running on your vSphere infrastructure, connected through a dedicated VPN tunnel to the AWS Region. This service provides a single pane of glass experience via the AWS Management Console, CLI, and APIs to manage RDS databases running on-premises and in AWS. This service helps you to automatically perform the common database management tasks, including database provisioning, operating system and database patching, backup, point-in-time restore, compute scaling, instance health monitoring, and failover, freeing you to focus on your applications.
Yes, RDS on VMware allows you to configure automated daily backups and to take user-initiated backups on-demand (DB snapshots). You can restore the database instance from a DB snapshot for all supported engines or to a specific point-in-time for MySQL and PostgreSQL.
RDS on VMware allows you to specify automated backup retention period of up to 35 days for each database in your fleet. It is important to note that the RDS on VMware restore mechanism does not perform in-place replacement of existing databases. RDS on VMware creates a new database instance and restores your data to new volumes, allowing you to decide the best path forward in your specific situation.
Yes, every RDS instance benefits from local, on-premises health monitoring. When RDS on VMware detects that the database instance is unhealthy, the service replaces the unhealthy database instance. Customers can continue to access their databases using the same FQDN.
Yes. RDS on VMware takes care of both OS and database engine patching with minimal downtime. Patching happens during a configurable maintenance window for database instances.
Your database instance availability is not impacted due to disruption in the network connection to the AWS Region from your vSphere cluster. In case of VPN disconnect, you will not be able to initiate any new database management operations using the AWS Management Console, CLI, or APIs. If AWS services are not reachable, database monitoring metrics will not be sent to Amazon CloudWatch.
Yes, RDS on VMware supports customers who are using a http proxy server in front of their Amazon RDS on VMware databases to protect their network from unauthorized access.
During the installation process, the installer will prompt you to enter the right IP, port and authentication information. It will then validate this information until this information is correctly provided from customer and verified by the installer. After the cluster is up, proxy server will be periodically authenticated for changed credentials.
As part of the installation process, you can specify your network proxy server through the RDS on VMware installer. Should you require to change a Network Proxy Server setting, you will need to contact AWS support with all the proxy information in the support ticket before making any modifications. AWS will need to make corresponding changes on the AWS side to support the new Network Proxy Server Information.
Yes, RDS on VMware will upgrade the database engine for you.
Yes, you can specify the maintenance window that’s most suitable or you can request to perform the upgrade immediately.
A member of our team will be in touch shortly.