Deploying the virtual appliances in AWS through AWS Marketplace
Veritas Resiliency Platform enables you to deploy the virtual appliances in AWS through AWS Marketplace using CloudFormation templates. There are six offerings available for deploying the virtual appliances using CloudFormation templates:
Veritas Resiliency Platform Express Install: Installs Resiliency Manager, IMS, and Replication Gateway appliances in AWS. This template also provides options to install Veritas Data Gateway appliance in AWS.
Veritas Resiliency Platform Gateway Install: Installs an additional Replication Gateway appliance in AWS.
Veritas Resiliency Platform Resiliency Manager Install: Installs an additional Resiliency Manager appliance in AWS.
Veritas Resiliency Platform Infrastructure Management Install : Installs the Infrastructure Management server in AWS.
Veritas Resiliency Platform Resiliency Manager Upgrade : Upgrades the Resiliency Manager appliance in AWS.
Veritas Resiliency Platform Infrastructure Management Upgrade : Upgrades the Infrastructure Management server in AWS.
To deploy the virtual appliances in AWS using CloudFormation templates
- Prerequisites:
1. Create Amazon Virtual Private Cloud (VPC):
See Configuring Amazon VPC for deployment using CloudFormation Templates.
2. Refer IAM permission required:
See Permissions required in AWS Marketplace for IAM roles RM, IMS and Replication Gateway .
- Go to the AWS Marketplace and locate Veritas Resiliency Platform product.
- Select the fulfillment option from the options available: Express Install, Gateway Install, Resiliency Manager, or Infrastructure Management Server.
- AWS Marketplace lets you launch the selected option through CloudFormation Templates interface. You are redirected to the Create Stack page of AWS CloudFormation Template. The template URL is pre-populated for you. Click Next.
- On the next page, provide the values for the input fields:
See Providing inputs for Resiliency Platform CloudFormation Templates.
- Click Next and review the additional options for your stack. Select the check box in the Capabilities section.
- Click Next and review the summary displayed on the Review page.
- Click Create to create the instances. This step creates the EC2 instances, staging volume for Replication Gateway appliance, and required Security Groups. This step also completes the bootstrap for all the appliances.
- For multiple Network Interface card (NIC) instances, every NIC created is associated with a different security group.
- For security reasons, the CloudFormation template disables the SSH communication to the instances. Once the stack deployment completes, you need to enable the SSH communication to the instances for setting the admin password. This password is required for logging in to the Resiliency Manager console. A password is also required for adding the IMS, Replication Gateway appliances to Resiliency Manager.
Modify the security groups of each instance to include the inbound SSH port (TCP port 22) for the required source IP or security group.
Note:
The instances go through some automatic configuration steps immediately after deployment. If you connect to the instance via SSH and if the configuration is still in-progress, wait until all steps are completed and reconnect to the instance.
- Log in to the Resiliency Manager console and setup the initial infrastructure through Getting Started wizard.
Note:
For Express install, if creation of stack fails and rollback is enabled on failure, AWS takes care of all the clean-up required in this situation. However, to enable this clean-up, you need to manually delete the Elastic Network Interface (ENI) associated with the security group that is attached with ZipFileUploaderLambda function.
Note:
Instance Metadata Service v2 (IMDSv2) is introduced by AWS as security enhancement over IMDSv1. While using AWS CloudFormation template, there is no way to disable the IMDSv1 option. So this limits the AWS MarketPlace deployment to have IMDSv2 enabled. It can be changed later using AWS CLI.
See Getting started with a new Resiliency Platform configuration.