> This page location: /docs.md > /docs/management.md > /docs/atlas/reference.md > /docs/atlas/faq.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# FAQ: Networking

**Note:**

Some answers on this page apply to Atlas Core clusters only. To learn which features Atlas Infinite supports, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability)

## Do Atlas cluster's public IPs ever change?

The factors that determine if and when an Atlas cluster's public IP address changes depends on the cluster tier.

**Note:**

This section applies to `M10` or larger dedicated clusters only unless specified.

An Atlas cluster's public IP addresses must change when you:

- [Add shards to a sharded cluster.](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-shardNum)

- [Change the region into which a cluster is deployed.](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-region)

- [Scale](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-open-dialog) a Free cluster (formerly known as `M0`) or Flex cluster to an `M10` or larger cluster.

- [Terminate](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-terminate-cluster) then re-deploy a cluster with the same name *but in a different tier* within 36 hours.

- [Enable Encryption at Rest](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-enable-encryption) on a cluster with a lifetime less than 12 hours.

**Note:**

For NVMe-backed clusters on [Amazon Web Services (AWS)](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-amazon-aws) or [Microsoft Azure](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure), vertically scaling usually keeps the existing public IP addresses. However, there is a small chance they change; Atlas does not guarantee IP address retention.

An Atlas cluster's public IPs don't change when you:

- [Convert a replica set to a sharded cluster](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-sharding), provided you make no other topology changes at the same time. Topology changes are changes to the architecture of your cluster, for example adding or removing shards or nodes or changing your cluster's regional distribution.

- Vertically scale a cluster on [Amazon Web Services (AWS)](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-amazon-aws) or [Microsoft Azure](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure) that is not backed by an [NVMe SSD](https://www.mongodb.com/docs/atlas/nvme-storage.md#std-label-nvme-storage), or vertically scale a cluster from any tier on [Google Cloud Platform (GCP).](https://www.mongodb.com/docs/atlas/reference/google-gcp.md#std-label-google-gcp)

- Unpause the cluster.

- [Terminate](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-terminate-cluster) and then re-deploy a cluster with a lifetime of 12 hours or more within 12-36 hours.

- Experience a maintenance or a healing event on your cluster.

To find the public IP address for any node in your cluster, use the `nslookup` tool from the command line. The IP address is shown in the `Address` portion of the output.

```sh
$ nslookup ds-shard-00-00-17jcm.mongodb-dev.net

Address: 34.226.104.79
```

## Can I specify my own VPC for my MongoDB Atlas project?

No. An Atlas project, and its clusters, are associated with a region-specific VPC (Virtual Private Cloud).

Atlas creates a VPC (Virtual Private Cloud) when you deploy the first `M10+` dedicated cluster to a given provider and region. For multi-region clusters, Atlas creates one VPC (Virtual Private Cloud) per region if there is not already a VPC (Virtual Private Cloud) for that region.

*(AWS deployments only)* Atlas also creates a VPC (Virtual Private Cloud) when you create a [VPC peering connection](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering) to an AWS (Amazon Web Services) VPC (Virtual Private Cloud). Atlas creates the VPC (Virtual Private Cloud) in the same region as the peered VPC (Virtual Private Cloud).

To use a different VPC (Virtual Private Cloud) (that is, on the customer's own cloud infrastructure accounts), you would need to use MongoDB Cloud Manager or Ops Manager.

## How do I find my Atlas-side hostnames to open up my outbound firewall?

If your firewall blocks outbound network connections, you must configure outbound access from your application environment to MongoDB Atlas.

### Automatically Resolve IP Addresses

You can use the [SRV Connection String Format](https://www.mongodb.com/docs/manual/reference/connection-string-formats.md#std-label-connections-dns-seedlist), which automatically resolves to the appropriate IP addresses for MongoDB Atlas services and clusters.

### Retrieve Specific IP Addresses for Outbound Firewall Rules

If your application environment requires configuring outbound firewall rules using specific IP addresses, you can retrieve a list of IP addresses associated with all clusters and services in your project using the [Return All IP Addresses for One Project](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupipaddresses) API endpoint.

**Note:**

These IP addresses are dynamic and subject to frequent changes. Use this option only if your application can programmatically integrate these IP addresses into your orchestration automation, enabling frequent updates to your firewall rules.

## How many cross-region network permissions does Atlas support?

Gen1 clusters can span regions and cloud service providers. Gen2 clusters can span multiple regions and cloud service providers so long as all nodes are on AWS (Amazon Web Services) or Google Cloud and in regions that support Gen2 clusters. All nodes in a cluster must be Gen2. You can't mix Gen1 and Gen2 nodes in the same cluster. To learn more, see:

- [AWS Gen2 Supported Regions](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-aws-reference-gen2-regions)

- [GCP Gen2 Supported Regions](https://www.mongodb.com/docs/atlas/reference/google-gcp.md#std-label-gcp-reference-gen2-regions)

Atlas limits the total number of nodes in other regions in one project to a total of 100, **not** including: - Google Cloud regions communicating with each other - Free clusters - Flex clusters

Sharded clusters include additional nodes. The electable nodes on the dedicated Config Server Replica Set (CSRS) count towards the total number of allowable nodes. Each sharded cluster has an additional electable node per region as part of the dedicated CSRS. To learn more, see [Replica Set Config Servers.](https://www.mongodb.com/docs/manual/core/sharded-cluster-config-servers.md#std-label-replset-config-servers)

The total number of nodes between any two regions must meet this constraint.

**Example:**

If an Atlas project has nodes in clusters spread across three regions:

- 75 nodes in **Region A**

- 10 nodes in **Region B**

- 5 nodes in **Region C**

You can only add 10 more nodes to **Region C** because:

1. If you exclude Region C, Region A + Region B = 85, \<= 100.&#x20;

2. If you exclude Region B, Region A + Region C = 80, \<= 100.&#x20;

3. If you exclude Region A, Region B + Region C = 15, \<= 100.&#x20;

4. Each combination of regions with the added 10 nodes still meets the per-project constraint:

   - Region A + B = 85, \<= 100&#x20;

   - Region A + C = 90, \<= 100&#x20;

   - Region B + C = 25, \<= 100&#x20;

You can't create a multi-region cluster in a project if it has one or more clusters spanning 100 or more nodes in other regions.

Contact Atlas [support](https://www.mongodb.com/docs/manual/support/) for questions or assistance with raising this limit.

If you would exceed the cross-region permissions limit when creating a cluster through the Atlas Administration API, the API (Application Programming Interface) returns the following error:

```json
{
  "error" : 403,
  "detail" : "Cannot have more than 100 cross-region network permissions.",
  "reason" : "Forbidden"
}
```

## Can Atlas be used with AWS Transit Gateway?

Yes. AWS (Amazon Web Services) PrivateLink powers Atlas Private Endpoints. This allows for transitive connectivity. You can use the [AWS Transit Gateway](http://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html) with your VPC (Virtual Private Cloud) if you connected your VPC (Virtual Private Cloud) to Atlas via AWS (Amazon Web Services) PrivateLink.

## Can Atlas be used with AWS Direct Connect?

Yes. AWS (Amazon Web Services) PrivateLink powers Atlas Private Endpoints. This allows for transitive connectivity. You can use [AWS Direct Connect](http://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/aws-direct-connect-network-to-amazon.html) with your VPC (Virtual Private Cloud) if you connected your VPC (Virtual Private Cloud) to Atlas via AWS (Amazon Web Services) PrivateLink.
