Configure a VPC for MarkLogic clients
- Last Updated: April 14, 2026
- 1 minute read
- MarkLogic Server
- Version 12.0
- Documentation
If you have an existing VPC or if you are not using the VPC template described in Deploying MarkLogic on EC2 Using CloudFormation, follow the procedure in this section to configure your VPC to enable access by clients, such as mlcp, Java Client API, DMSDK, Node.js Client API, and so on.
MarkLogic clients require that the subnets containing your EC2 instances be configured for inbound access. The procedures for this are as follows.
-
Create an Internet Gateway and attach it to your VPC, as described in Enable VPC internet access using internet gateways.
Note the ID of the Internet Gateway.
If your EC2 instance is in a public subnet, do the following:
-
Enable the public IP address on the EC2 instance, as described in Public IPv4 addresses.
-
Create a route table for the subnets containing your EC2 instances, as described in Configure route tables.
-
In the route table, add the following route:
-
Destination:
0.0.0.0/0 -
Target:
Internet Gateway ID
-
If your EC2 instance is in a private subnet, do the following:
-
Create a public subnet, as described in:
-
Follow Steps 2-3 above.