Connectivity
Network connectivity requirements differ depending on the protocol (REST or FIX) and the environment (non-production or production).
Quick Reference
| Protocol | Non-Production | Production |
|---|---|---|
| REST | Open internet | IP whitelisting |
| FIX | Open internet | VPN / AWS PrivateLink / VPC peering |
REST API
In non-production environments (UAT / staging), the REST API is accessible over the open internet. No special network configuration is required — authenticate with your API key and connect directly.
In production, all REST API access requires IP whitelisting. You must provide your static egress IP addresses to Atomic Vaults so they can be added to the allowlist before you can reach the production endpoints.
Submit your production IP addresses during onboarding. Requests from non-whitelisted IPs will be rejected.
FIX
In non-production environments, FIX connectivity is available over the open internet. However, we strongly recommend setting up a production-like private connectivity configuration in non-prod before going live. This ensures your network path, firewall rules, and failover behavior are validated ahead of the production cutover.
In production, FIX connections must use one of the following private networking methods:
- VPN — Site-to-site VPN tunnel between your infrastructure and Atomic Vaults.
- AWS PrivateLink — Private endpoint within your AWS VPC, keeping traffic on the AWS backbone.
- VPC Peering — Direct peering between your AWS VPC and the Atomic Vaults VPC.
Coordinate with your Atomic Vaults integration contact to select the private connectivity method that best fits your infrastructure and to begin provisioning.