Configure Your Network Routing - AWS
Before you begin
About this task
- Download the dhs-route-config.template. If necessary, modify the template.
dhs-route-config.templateis an optional template you can use to configure your route tables. If you do not want to use our template to configure your route tables, see https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-routing.html.
- Navigate to the AWS CloudFormation Console page.
Important: Before you continue, ensure you are creating your stack in a region supported by Data Hub Service (DHS). See Supported Regions - AWS.
- Click Create stack.
- Click With new resources (standard).
- In the Create stack page, specify the
- In the Specify Stack Details page, supply the fields with the following information:
Important: The service public and private subnet CIDRs must not overlap with the public and private subnet CIDRs you specified when setting up your client-side VPC.Note: For more general information on creating a stack, see Creating a Stack on the AWS CloudFormation Console.
Field Description Stack name The name for this collection of AWS network resources. Public and Private Subnet Route Table IDs Your client-side VPC's route tables (
rtb-*) used to route network subnet CIDRs to the peering connection ID (
pcx-*), enabling your client-side VPC and MarkLogic VPC to communicate with each other.
To find your Route Tables in AWS CloudFormation Console if you used our template, navigate to the AWS CloudFormation Console.
- Select the stack created when you set up a client-side VPC.
- Select the Outputs tab.
To find all of your route tables in AWS, navigate to AWS.
Tip: You can filter by your VPC ID (
- From the top menu, navigate to .
- In the Resources by Region page, click Route Tables.
vpc-*) to find the route tables for your client-side VPC.
Service Public and Private Subnet CIDRs The public and private subnet CIDRs calculated from the network CIDR in your peered DHS network configuration.
Enter the public subnet CIDRs in the Service Public Subnet CIDR fields and the private subnet CIDRs in the Service Private Subnet CIDR fields. Enter one CIDR in each field. Example:
10.1.2.0/25, 10.1.3.0/24, 10.1.4.0/25, 10.1.0.0/25, 10.1.1.0/27, 10.1.5.0/24
Peering Connection ID The Peering Connection ID (
pcx-*) in your peered DHS network configuration.
Click the following link to view a full list of client-side network resources.
- Click .
- (Optional) In the Configure stack options page, specify tags, IAM roles, and advanced options.
- Click .
- Review the details.
What to do next
Create a Data Hub Service with a peered network: