Send requests to the Cloud API from your AWS Virtual Private Cloud (VPC) via AWS PrivateLink.
Why use PrivateLink?
Sending your requests via AWS PrivateLink can:
- Improve security by keeping your data within the Amazon network (no internet traversal)
- Meet regulatory compliance requirements such as HIPAA and EU-US Privacy Shield
- Reduce your AWS egress costs
All DWS4 endpoints are supported enabling secure document generation.
Availability
Supported Regions and Availability Zones
DWS4 provides AWS PrivateLink endpoints for:
| Docmosis Region | AWS Region | Availability Zones |
| US1 (United States) | us-east-1 (North Virginia) |
us-east-1d us-east-1e |
| EU1 (Europe) | eu-central-1 (Frankfurt) |
eu-central-1b eu-central-1c |
| AU1 (Australia) | ap-southeast-2 (Sydney) |
ap-southeast-2a ap-southeast-2b |
How to setup PrivateLink
1. Contact Docmosis support (This email address is being protected from spambots. You need JavaScript enabled to view it.) with the AWS Region you intend to use and your AWS Account ID. This will be used to verify the origin of the connection request.
2. Docmosis support will reply with the AWS endpoint service name.
3. Create an interface endpoint in AWS using the service name and let us know when its ready. For example:
4. We will verify and accept the pending connection request.
5. Enable the "Private DNS names" setting on your Endpoint, which will do the DNS mapping to the internal address for our service (eg: eu1.dws4.docmosis.com). To do so, click Actions -> Modify private DNS name:
Tick "Enable for this endpoint" and save:
Once this is in place, AWS will automatically direct traffic to the relevant Docmosis service using the internal network addresses. No changes to application code or configuration is required.
Note: If you would like to use PrivateLink from a region other than the current supported regions listed above you will need to setup a peering connection, see AWS instructions.
