It is best if you have experience launching and configuring EC2 instances within your AWS environment. Read below for specific tasks to complete before deployment.
Before deploying the Delphix Engine for AWS:
- Review Checklist of Information Required for Installation and Configuration.
- Make sure that the Amazon account you are using to deploy your Delphix Engine has an appropriate level of enablement to subscribe to the Delphix Engine for AWS subscription.
Determine which virtual private cloud (VPC) you will use when launching the virtualization instance. To maximize performance, deploy the Delphix Engine instance in the same VPC/subnet in which you will create your virtual databases (VDBs).
Provisioning a VDB requires a compute instance running the same database engine as the source. Please note, however, that the target instance only needs storage to accommodate the OS, database platform binaries, etc., because Delphix delivers all of the data files.
Make sure that the necessary ports are open.
Using the Delphix Engine for AWS will require connections to source and target database servers. Such connections require various ports to be open, enabling communications. For a detailed list of the network and port requirements, click the link appropriate to your database platform:
- Update Security Group settings to accommodate the necessary connections.
- Select the same Security Group that your current (or future) non-production EC2 compute nodes utilize.
- You must modify the Security Group to allow access to all of the networking ports used by the Delphix Engine and the various source and target platforms. See links above for information about specific port configurations.
- Allocate storage.
To properly size the initial storage capacity and determine the number and size of EBS Provisioned IOPs Volumes required, download and utilize the Delphix-Dynamic-Data-Platform-Storage-Calculator.
It is helpful to first create a list of the data sources from which you intend to make dSources. A data source is typically a production database that you link to the Virtualization Engine, enabling you to create virtual, full, read-write copies of the source within minutes. The list should include the database's name, platform (for example, Oracle or SQL Server), current size (in GB), the estimated number of virtual copies, and retention period (in days) of snapshots (backup copies).
- All data storage volumes must be EBS volumes. Allocate a minimum of four (4) EBS volumes to accommodate storage capacity needs.
- Provisioned IOPS EBS volumes are highly recommended.
- During the Manual Deployment option, use the guidelines outlined in Virtual Machine Requirements for AWS EC2 Platform.
Geographic Distribution in Regions and Availability Zones
The latency will be directly related to not just the Availability Zone configuration, but more specifically the geographies of those zones. The latencies can vary from tens to hundreds of milliseconds if the zones are geographically diverse (US West to US East would certainly be expected to perform better than US West to Europe). AWS advertises that all AZs in a given region are interconnected with high-bandwidth and low-latency networking per this AWS article.
Applications that are performance-sensitive will benefit from colocating the target servers and Engine in the same region if possible. Another possibility is building a failover strategy for those highly sensitive servers, enabling them to failover to another AZ in the instance where an Engine needs to be failed over. The architecture selected and geographies will also naturally be dependent on your redundancy requirements (your organization may require geographically diverse failover options beyond the ~60 miles advertised within a region).