Deploying the Amazon Web Services CloudFormation stack

The second step in configuring DNS data flow from Route 53 to IBM® NS1 Connect® through IBM Cloud Sync is to deploy the AWS CloudFormation stack.

Before you begin

Cloud Sync is available to organizations that are participating in the Public Preview program.

You must have the following:

  • An API key for your NS1 Connect account
  • An Amazon Web Services (AWS) account with permissions to use CloudFormation

About this task

The aws-route53-ns1-connect template in CloudFormation defines the infrastructure of the AWS services that Cloud Sync uses to synchronize data to NS1 Connect. The template is open source so that you can see the services that Cloud Sync uses.

You must update the settings in the template and deploy the CloudFormation stack to start synchronizing data from Route 53 to NS1 Connect.

The values in the template are prepopulated with most of the information that you need to deploy the CloudFormation stack. You only need to enter the API key for the NS1 Connect account. You also have the option to indicate if the predefined CloudSync tag is needed to synchronize DNS data from Route 53 to NS1 Connect.

Draft comment:
can you redeploy? what if you want to add the tags back, do you redeploy?

Complete this task through your AWS account.

Procedure

In AWS:
  1. Make sure that your region is set to US East (N. Viriginia).
    This is where the serverless application repository is located.
  2. Open the Serverless Application Repository service.
  3. In the Serverless Application Repository pane, click Available applications.
    The Available applications pane opens.
  4. Click the Private applications tab.
  5. Select the Show apps that create custom IAM roles or resource policies.
    A list of applications is displayed.
    Screen capture of the Serverless Applications Repository page
  6. From the list, click aws-route53-ns1-connect.
    The Review, configure and deploy page opens showing the template, permissions, and settings for the application.
  7. Optional: In EnableZoneOmmission, enter a value to indicate how Cloud Sync identifies which zones are synchronized from Route 53.
    • To indicate that zones need the predefined tag name CloudSync in Route 53 before they are synchronized to NS1 Connect, enter true.
    • To indicate that zones don't need a tag name in Route 53 before they are synchronized to NS1 Connect, enter false.
    If you entered true, you must tag the zones in Route 53 with the CloudSync tag.
  8. In NS1APIKey, enter the API key of your NS1 Connect account.
    This is the API key that you created in NS1 Connect.
  9. Select the I acknowledge that this app creates resource policies and deploys nested applications checkbox.
  10. Click Deploy.

Results

Background processes run to deploy the stack. The processes could take a few minutes. If you want to see the progress, you can check the CloudFormation stack for aws-route53-ns1-connect.

What to do next

Tag the zones in Route 53 that you want to synchronize to NS1 Connect if you chose to use tags to indicate which zones to synchronize to NS1 Connect.