On this page
Atlas only allows client connections to the database deployment from entries in the project's IP access list. Each entry is either a single IP address or a CIDR-notated range of addresses. For AWS clusters with one or more VPC Peering connections to the same AWS region, you can specify a Security Group associated with a peered VPC.
For Atlas clusters deployed on Google Cloud Platform (GCP) or Microsoft Azure, add the IP addresses of your Google Cloud or Azure services to Atlas project IP access list to grant those services access to the cluster.
The IP access list applies to all database deployments in the project and can have up to 200 IP access list entries, with the following exception: projects with an existing sharded cluster created before August 25, 2017 can have up to 100 IP access list entries.
Atlas supports creating temporary IP access list entries that expire within a user-configurable 7-day period.
Atlas audits the creation, deletion, and updates of both temporary and permanent IP access list entries in the project's Activity Feed.
To view the project's Activity Feed, click Activity Feed in the Project section of the left navigation pane.
Activity Feed Considerations
Atlas does not report updates to a IP access list entry's comment in the Activity Feed.
When you modify the address of a IP access list entry, the Activity Feed reports two new activities: one for the deletion of the old entry and one for the creation of the new entry.
To manage IP Access List entries, you must have
Project Owner access
to the project.
Organization Owner access must add themselves to the
project as a
When you remove an entry from the IP access list, existing connections from the removed addresses may remain open for a variable amount of time. How much time passes before Atlas closes the connection depends on several factors, including:
how the connection was established
how the application or driver using the address behaves
which protocol (like TCP or UDP) the connection uses