Getting Started with Data Hub Service in AWS
Overview
To create and set up a peered MarkLogic Data Hub Service (DHS), you need two virtual networks (called VPCs [virtual private cloud] in Amazon Web Services [AWS]):
- The client-side network that keeps your DHS endpoints more secure.
- The peered DHS network that houses the DHS clusters.
To create and set up a public DHS, you need one virtual network:
Before you begin
You need:
- An AWS account with permissions to create and configure AWS VPCs.
- To subscribe to MarkLogic Data Hub Service (DHS) in AWS.
The following table organizes the tasks to create a Data Hub Service (DHS) into two configurations:
- Peered (Recommended)
- Public
Choose one of the supported configurations to get started. The tasks are in the order they must be executed.
| Task | Peered | Public |
|---|---|---|
| Set Up a Secure Client-Side VPC | ||
| Create the Peer Role | ||
| Set Up a Peered DHS Network | ||
| Set Up a Public DHS Network | ||
| Configure Your Network Routing | ||
| Create a Peered DHS Instance | ||
| Create a Public DHS Instance | ||
| Authentication Service: Internal (Default) | ||
| Authentication Service: External (Recommended) | Optional | Optional |
| Configure SSH Tunneling: (Recommended) | Optional | |
| Provision Data Hub Service | ||
| Create Peered Data Hub Service | Create Public Data Hub Service |
What to do next
- Set up local development and QA environments that mirror the configuration of your DHS production environment.
- Using MarkLogic Data Hub, set up a local project, create and test your flows, and deploy them and other artifacts (e.g., modules, index configurations, and TDE templates) to your DHS instance. The deployment also installs or updates MarkLogic Data Hub in your cloud environment.