Docs Menu
Docs Home
/ /
MongoDB Atlas for Government

Security

On this page

  • Preconfigured Security Features
  • Required Security Features
  • Optional Security Features

MongoDB Atlas for Government and databases hosted in AtlasGov use TLS 1.2 to encrypt connections. This cannot be disabled.

AtlasGov automatically enables FIPS 140-2 for all databases.

You must configure the following security features:

  • IP access list, and

  • Database user authentication.

A subset of commercial Atlas optional security features are available in AtlasGov with some limitations.

  • You must use KMS keys in AWS GovCloud and GCP Assured Workloads regions to encrypt data in AWS GovCloud and GCP Assured Workloads region-only projects. You must use KMS keys in AWS Standard regions to encrypt data in AWS Standard region-only projects.

See the Atlas documentation to configure Customer Key Management with AWS KMS and Manage Customer Keys with Google Cloud KMS.

  • You can only peer AWS GovCloud regions with MongoDB clusters in AWS GovCloud regions. You can only peer AWS Standard regions with MongoDB clusters in AWS Standard regions.

  • You can only peer GCP Assured Workloads regions with MongoDB clusters in GCP Assured Workloads regions.

See the Atlas documentation to Set up a Network Peering Connection

  • You can only link AWS GovCloud regions with MongoDB clusters in AWS GovCloud regions. You can only link AWS Standard regions with MongoDB clusters in AWS Standard regions.

  • You can only link GCP Assured Workloads regions with MongoDB clusters in GCP Assured Workloads regions.

See the Atlas documentation to Set up a Private Endpoint.

You can use the following endpoints: