Installing the data broker in AWS
Contributors Download PDF of this page
When you create a new data broker, choose the AWS Data Broker option to deploy the data broker software on a new EC2 instance in a VPC. Cloud Sync guides you through the installation process, but the requirements and steps are repeated on this page to help you prepare for installation.
You also have the option to install the data broker on an existing Linux host in the cloud or on your premises. Learn more.
Supported AWS regions
All regions are supported except for the China and GovCloud (US) regions.
The data broker needs an outbound internet connection so it can poll the Cloud Sync service for tasks over port 443.
When Cloud Sync deploys the data broker in AWS, it creates a security group that enables the required outbound communication. Note that you can configure the data broker to use a proxy server during the installation process.
If you need to limit outbound connectivity, see the list of endpoints that the data broker contacts.
NetApp recommends configuring the source, target, and data broker to use a Network Time Protocol (NTP) service. The time difference between the three components should not exceed 5 minutes.
Permissions required to deploy the data broker in AWS
The AWS user account that you use to deploy the data broker must have the permissions included in this NetApp-provided policy.
When Cloud Sync deploys the data broker, it creates an IAM role for the data broker instance. You can deploy the data broker using your own IAM role, if you prefer. You might use this option if your organization has strict security policies.
The IAM role must meet the following requirements:
The EC2 service must be allowed to assume the IAM role as a trusted entity.
The permissions defined in this JSON file must be attached to the IAM role so the data broker can function properly.
Follow the steps below to specify the IAM role when deploying the data broker.
Installing the data broker
You can install a data broker in AWS when you create a sync relationship.
Click Create New Sync.
On the Define Sync Relationship page, choose a source and target and click Continue.
Complete the steps until you reach the Data Broker page.
On the Data Broker page, click Create Data Broker and then select Amazon Web Services.
If you already have a data broker, you’ll need to click the icon first.
Enter a name for the data broker and click Continue.
Enter an AWS access key so Cloud Sync can create the data broker in AWS on your behalf.
The keys aren’t saved or used for any other purposes.
If you’d rather not provide access keys, click the link at the bottom of the page to use a CloudFormation template instead. When you use this option, you don’t need to provide credentials because you are logging in directly to AWS.
If you entered an AWS access key, select a location for the instance, select a key pair, choose whether to enable a public IP address, and then select an existing IAM role, or leave the field blank so Cloud Sync creates the role for you.
If you choose your own IAM role, you’ll need to provide the required permissions.
Specify a proxy configuration, if a proxy is required for internet access in the VPC.
After the data broker is available, click Continue in Cloud Sync.
The following image shows a successfully deployed instance in AWS:
Complete the pages in the wizard to create the new sync relationship.
You have deployed a data broker in AWS and created a new sync relationship. You can use this data broker with additional sync relationships.
Details about the data broker instance
Cloud Sync creates a data broker in AWS using the following configuration.
- Instance type
m5n.xlarge when available in the region, otherwise m5.xlarge
- Operating system
Amazon Linux 2
- Disk size and type
10 GB GP2 SSD