> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Create an Atlas Infinite or Atlas Core Cluster Atlas Infinite is available as a Public Preview feature. Atlas Infinite and its documentation might change at any time during the Preview period. To learn more, see [Preview Features](https://www.mongodb.com/docs/preview-features/). This tutorial takes you through the steps to create a new Atlas cluster. To learn how to modify an existing Atlas Core cluster, see [Modify an Atlas Core Cluster](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster). To learn how to modify an existing Atlas Infinite cluster, see [Modify an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-modify-cluster.md#std-label-atlas-infinite-modify-cluster) A [cluster](https://www.mongodb.com/docs/atlas/create-database-deployment.md#std-label-ref-deployment-types) on Atlas Infinite is a [replica set](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-replica-set). A cluster on Atlas Core can be a replica set or a [sharded cluster](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-sharded-cluster). This tutorial walks you through creating a replica set. To learn about recommendations for clusters, see [Recommendations for Atlas Orgs, Projects, and Clusters](https://www.mongodb.com/docs/atlas/architecture/current/hierarchy.md#std-label-arch-center-orgs-projects-clusters-recs) in the Atlas Architecture Center. To learn about high availability recommendations, see [Recommendations for Atlas High Availability](https://www.mongodb.com/docs/atlas/architecture/current/high-availability.md#std-label-arch-center-ha-recs) in the Atlas Architecture Center. ## Required Access To create a cluster, you must have [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner), [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner), or [`Project Cluster Creator`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Cluster-Creator) access to the project. ## Considerations To learn about the differences between Atlas database editions, see [Database Editions](https://www.mongodb.com/docs/atlas/database-editions.md#std-label-atlas-editions). The following considerations apply when you create a cluster: ### Considerations That Apply to Both Editions The following considerations apply to both Atlas Infinite and Atlas Core: - To minimize network latency and data transfer costs, and to increase overall stability and security, use the same cloud provider and region to host your application and cluster when possible. - Each Atlas [project](https://www.mongodb.com/docs/atlas/organizations-projects.md#std-label-projects) supports up to 25 clusters. If you have questions or need assistance regarding the cluster limit, [contact support.](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support) - If your Atlas project contains a [custom role](https://www.mongodb.com/docs/atlas/security-add-mongodb-roles.md#std-label-mongodb-roles) that uses actions introduced in a specific MongoDB version, you must delete that role before creating clusters with an earlier MongoDB version. - New clusters use TLS (Transport Layer Security) version 1.3 by default, and support 1.2 if you set it explicitly. IMPORTANT: Atlas no longer supports TLS (Transport Layer Security) 1.0 or 1.1. All clusters reject attempts to connect with TLS (Transport Layer Security) 1.0 or 1.1. Set the minimum TLS (Transport Layer Security) version of your clusters to 1.2 or higher. - When you create a cluster, Atlas creates a [network container](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcontainer) in the project for the cloud provider to which you deploy the cluster if one does not already exist. - If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), all new and existing clusters have Cloud Backup automatically enabled and use the project-level Backup Compliance Policy. Atlas augments any preexisting cluster-level policies to meet the minimum requirements of the Backup Compliance Policy. All new clusters use the Backup Compliance Policy unless the mininum requirements of the [cluster-level backup policy](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) expand beyond the mininum requirements of the Backup Compliance Policy. - We recommend `M30` and higher clusters for production environments. - The cluster type you select determines how your cluster receives new MongoDB versions: - For Atlas Core clusters, you can use Latest Version With Auto Upgrades, or you can choose a specific major MongoDB version to control when you upgrade. - For Atlas Infinite clusters, Atlas always uses Latest Version With Auto Upgrades. - For Free clusters and Flex clusters, Atlas upgrades them automatically and keeps them on a specific major MongoDB version. - To learn more, see [MongoDB Versions in Atlas.](https://www.mongodb.com/docs/atlas/atlas-versions.md#std-label-atlas-versions) ### Considerations for Atlas Infinite clusters Only - To create an Atlas Infinite cluster in the Atlas UI, click Go to Advanced Configuration and select Atlas Infinite. You can also use the Atlas CLI, the Atlas Administration API, or Terraform. - You can't change the database edition after you create the cluster, so to use a different edition, create a new cluster. - Atlas Infinite clusters have several public preview limitations; see [Public Preview Availability](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability) for the full list. - You can set a max storage limit that caps the logical data size of your Atlas Infinite cluster. To learn more, see [Max Storage Limit.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-max-storage-limit) - To learn how Atlas Infinite manages cluster storage, see [Manage Storage on an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage) ### Considerations for Atlas Core clusters Only - Multi-region and multi-cloud clusters are subject to cross-region node limits. To learn more, see [Configure High Availability and Workload Isolation.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) - When you create a cluster, cluster tier auto-scaling is enabled by default in the Atlas UI and disabled by default in the Atlas Administration API. To learn more, see [Auto-Scaling for Atlas Clusters.](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling) - The AI Cluster Assistant can help you configure a cluster while you create it. To learn more, see [AI Cluster Assistant.](https://www.mongodb.com/docs/atlas/ai-cluster-assistant.md#std-label-atlas-ai-cluster-assistant) ## Procedure ### Create an Atlas Core cluster To create one cluster in the specified project using the Atlas CLI, run the following command: ```sh atlas clusters create [name] [options] ``` To watch for a specific cluster to become available using the Atlas CLI, run the following command: ```sh atlas clusters watch [options] ``` To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for [atlas clusters create](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-create/) and [atlas clusters watch.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-watch/) **See also: Related Links** - [Install the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/) - [Connect to the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/connect-atlas-cli/) Don't use `atlas clusters create` to create an Atlas Infinite cluster. That command has no edition option, so it creates an Atlas Core cluster. ### Create an Atlas Infinite cluster During public preview, Atlas Infinite clusters support [select AWS regions](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-atlas-infinite-aws-regions). To create an Atlas Infinite cluster, create a `payload.json` file that sets `databaseEdition` to `INFINITE`. Replace the other values with your cluster configuration: ```json { "name": "{CLUSTER-NAME}", "databaseEdition": "INFINITE", "clusterType": "REPLICASET", "replicationSpecs": [ { "regionConfigs": [ { "providerName": "AWS", "regionName": "{REGION-NAME}", "priority": 7, "electableSpecs": { "instanceSize": "M10", "nodeCount": 2 } } ] } ] } ``` Then run the following command: ```sh atlas api clusters createCluster \ --version 2024-08-05 \ --groupId {GROUP-ID} \ --file payload.json ``` To confirm which database edition your cluster runs on, run `atlas api clusters getCluster`. Atlas returns `databaseEdition` and the read-only `effectiveDatabaseEdition`. ### View Available Regions To list available regions that Atlas supports for new deployments using the Atlas CLI, run the following command: ```sh atlas clusters availableRegions list [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas clusters availableRegions list.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-availableRegions-list/) This command returns all regions that Atlas supports. During public preview, Atlas Infinite clusters support select AWS (Amazon Web Services) regions. To learn more, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability) When you create your first Atlas cluster using the Atlas UI, you can either: - Use a template with preset advanced configuration options. - Specify advanced configuration options. Whether you use a template or specify advanced configuration, you can [modify an Atlas Core cluster](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster) or [modify an Atlas Infinite cluster](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-modify-cluster.md#std-label-atlas-infinite-modify-cluster) after you create the cluster. To use a different edition, create a new cluster and select the edition at creation time. **Note:** The procedure for creating a new Atlas cluster in the Atlas UI differs depending on whether you already have one or more clusters in your project. The following steps apply to both, but you may see slightly different options in the UI. **Important:** This procedure uses a template, which creates an Atlas Core cluster. To create an Atlas Infinite cluster, navigate to the bottom of the page and click Go to Advanced Configuration. You can't change the database edition after you create the cluster. 1. In Atlas, go to the Clusters page for your project. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the sidebar, click Clusters under the Database heading. The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays. 2. Open the Deploy your cluster page. If you already have one or more clusters, click Create to display the Deploy your cluster page. If this is your first cluster, click Build a Cluster to display the Deploy your cluster page. 3. Select a cluster type. You can deploy the following clusters from this page: M10 The M10 tier is suitable for development environments and low-traffic applications, while higher tiers can handle large datasets and high-traffic applications. Dedicated clusters can be deployed into a single geographical region or multiple geographical regions. **Note:** To create Dedicated cluster tiers higher than M10, select Go to Advanced Configuration at the bottom of the page. Flex Clusters Flex clusters are low-cost cluster types suitable for teams who are learning MongoDB or developing small proof-of-concept applications. You can begin your project with an Atlas Flex cluster and upgrade to a production-ready Dedicated cluster tier at a future time. **Important:** As of February 2025, you can create Flex clusters, and can no longer create `M2` and `M5` clusters or Serverless instances in the Atlas UI, Atlas CLI, Atlas Administration API, Atlas Kubernetes Operator, HashiCorp Terraform, or Atlas CloudFormation Resources. As of January 22, 2026, Atlas no longer supports `M2` and `M5` clusters and Serverless instances. All existing `M2` and `M5` clusters were migrated to Flex clusters. Atlas migrated Serverless instances to Free clusters, Flex clusters, or Dedicated clusters according to your usage. To see which tiers Atlas migrated your instances to, consult the [All Clusters](https://cloud.mongodb.com/v2#/clusters) page in the Atlas UI. **Important:** All Serverless instances have been automatically migrated, based on current usage, to Free clusters, Flex clusters, or Dedicated clusters. The [All Clusters](https://cloud.mongodb.com/v2#/clusters) page in the Atlas UI shows which tiers your instances will be migrated to. Free clusters A Free cluster provides a free sandbox replica set. You can deploy one Free cluster per Atlas project. Free clusters are more limited than Atlas Flex and Dedicated clusters. For information on these limitations, refer to [Configuration Limits.](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-shared-limits-config) 4. Select your preferred Cloud Provider & Region. The choice of cloud provider and region affects the configuration options for the available cluster tiers, network latency for clients accessing your cluster, the geographic location of the nodes in your cluster, and the [cost of running the cluster.](https://www.mongodb.com/docs/atlas/billing.md#std-label-billing-overview) To learn more, see [Cloud Providers and Regions.](https://www.mongodb.com/docs/atlas/cloud-providers-regions.md#std-label-create-cluster-cloud-provider-region) **Note:** To deploy your cluster across multiple regions, or to deploy separate Search Nodes for workload isolation, select Go to Advanced Configuration at the bottom of the page. 5. Specify a name for the cluster in the Name box. This label identifies the cluster in Atlas. **Note:** Atlas creates your hostname based on your cluster name. You can't change the cluster name after Atlas deploys the cluster. Cluster names can't exceed 64 characters in length. IMPORTANT: Atlas truncates the cluster name to *23 characters* in its internal interactions. In practice, this means: - Cluster names shorter than 23 characters can't end with hyphen or dash (`-`). - Cluster names 23 characters or longer can't use a hyphen or dash (`-`) as its 23rd character. - The first 23 characters in a cluster name must be unique within a project. Don't include [sensitive information](https://www.mongodb.com/docs/atlas/production-notes.md#std-label-sensitive-info) in your cluster name. 6. Specify a tag key and value to apply to the cluster. To learn more, see [Apply a cluster Tag to a New Cluster from a Template.](https://www.mongodb.com/docs/atlas/database-deployment-tags.md#std-label-apply-tags-new-cluster-template) **Important:** Don't include sensitive information such as Personally Identifiable Information (PII) or Protected Health Information (PHI) in your resource tags. Other MongoDB services, such as Billing, can access resource tags. MongoDB also sends cluster resource tags to DataDog and Prometheus integrations. Resource tags are *not* intended for private and sensitive data. To learn more, see [Sensitive Information.](https://www.mongodb.com/docs/atlas/production-notes.md#std-label-sensitive-info) 7. Deploy your cluster. Click Create. **Important:** Each Atlas [project](https://www.mongodb.com/docs/atlas/organizations-projects.md#std-label-projects) supports up to 25 clusters. If you have questions or need assistance regarding the cluster limit, [contact support.](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support) 8. Update your Billing Address details as needed. | Field | Necessity | Action | | --- | --- | --- | | Billing Email Address | Optional | Type the email address to which Atlas should send [billing alerts.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-billing-alerts) By default, Atlas sends billing alerts to the Organization Owners and Billing Admins. If you leave the Billing Email Address blank, Atlas sends billing alerts to the Organization Owners and Billing Admins.; If you specify a billing email address and uncheck Only send invoice emails to the Billing Email Address, Atlas sends billing alerts to the billing email address, Organization Owners, and Billing Admins.; If you specify a billing email address and check the box for Only send invoice emails to the Billing Email Address, Atlas send billing alerts to the billing email address only. | | Company Name | Optional | Type the name of the company for your billing address. | | Country | Required | Select the country for your billing address. You can also start typing the name of the country and then select it from the filtered list of countries. | | Street Address | Required | Type the street address for your billing address. | | Apt/Suite/Floor | Optional | Type an the apartment, suite, or floor for your billing address. | | City | Required | Type the name of the city for your billing address. | | State/Province/Region | Required | Type or select the political subdivision in which your billing address exists. The label and field change depending on what you selected as your **Country**: If you select **United States** as your **Country**, this label changes to **State**. The field changes to a dropdown menu of U.S. states. You can also start typing the name of the state and then select it from the filtered list of states.; If you select **Canada** as your **Country**, this label changes to **Province**. The field changes to a dropdown menu of Canadian provinces. You can also start typing the name of the province and then select it from the filtered list of provinces.; If you select any other country as your **Country**, this label changes to **State/Province/Region**. The field changes to a text box. Type the name of your province, state, or region in this box. | | ZIP or Postal Code | Required | Type the ZIP (U.S.) or Postal Code (other countries) for your billing address. | | VAT Number | Conditional | Atlas displays the VAT ID field if you select a country other than the United States. To learn more about VAT, see [VAT ID.](https://www.mongodb.com/docs/atlas/billing/international-usage.md#std-label-vat-id-number) If your company's billing address is in a country other than the United States (USA), Atlas typically charges VAT (Value Added Tax) if you do not enter a valid `VAT ID Number` on your [billing profile.](https://www.mongodb.com/docs/atlas/billing.md#std-label-atlas-billing-profile) IMPORTANT: If your billing address is in Ireland or certain Canadian provinces, Atlas always charges VAT (Value Added Tax), even with a valid `VAT ID Number`. To learn more about VAT (Value Added Tax) by region, see [International Usage and Taxation.](https://www.mongodb.com/docs/atlas/billing/international-usage.md#std-label-atlas-international-tax) | 9. Update your Payment Method details as needed. Click the radio button for Credit Card or Paypal. - If you selected Credit Card, type values for the following fields: | Field | Necessity | Action | | --- | --- | --- | | Name on Card | Required | Type the name that appears on your credit card. | | Card Number | Required | Type the 16-digit number that appears on your credit card. American Express uses a 15-digit number. | | Expiration Date | Required | Type the expiration date for your credit card in the two-digit month and two-digit year format. | | CVC (Card Verification Code) | Required | Type the three-digit number on the back of your credit card. American Express uses a 4-digit number found on the front of the credit card. | - If you selected PayPal: Click Pay with PayPal. Complete the actions on the PayPal website. **Note:** All projects within your organization share the same billing settings, including payment method. 10. Review project's cost. Under the Cart section, review the following: | Field | Description | | --- | --- | | Cluster Tier | Displays cost for your selected cluster tier and configuration details. To learn more, see [Cloud Service Provider and Region](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-region-costs) and [Cluster Tier.](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-instance-size-costs) | | Included Features | Displays features included with your selected cluster configuration. | | Additional Settings | Displays additional settings that you enabled, such as cloud backups, sharding, [BI Connector](https://www.mongodb.com/docs/bi-connector/current/), and more. To learn more, see [Cloud Backups.](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-billing-backup-cloud-provider-snapshots) | Atlas Infinite doesn't support sharding in public preview, so sharding costs don't apply to an Atlas Infinite cluster. To learn how Atlas Infinite bills compute and storage, see [MongoDB Atlas Infinite Cluster Costs.](https://www.mongodb.com/docs/atlas/billing/atlas-infinite-costs.md#std-label-atlas-infinite-billing) 11. Deploy your cluster. Click Confirm and Deploy Cluster. **Important:** Each Atlas [project](https://www.mongodb.com/docs/atlas/organizations-projects.md#std-label-projects) supports up to 25 clusters. If you have questions or need assistance regarding the cluster limit, [contact support.](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support) 1) In Atlas, go to the Clusters page for your project. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the sidebar, click Clusters under the Database heading. The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays. 2) Open the Deploy your cluster page. If you already have one or more clusters, click Create to display the Deploy your cluster page. If this is your first cluster, click Build a Cluster to display the Deploy your cluster page. 3) Open Advanced Configuration. Navigate to the bottom of the page and click Go to Advanced Configuration. 4) Select the cluster edition. To create an Atlas Infinite cluster, turn on the Try the new edition: Atlas Infinite toggle. To create an Atlas Core cluster, leave the toggle off. Atlas Core couples compute and storage on the same node. Atlas Infinite runs them as separate layers that scale independently. To compare the two editions, see [MongoDB Atlas Database Editions.](https://www.mongodb.com/docs/atlas/database-editions.md#std-label-atlas-editions) 5) Select a cluster type. During public preview, Atlas Infinite supports replica sets only. A single Atlas Infinite cluster replica set stores up to 128 TB (logical), so you can grow to large data sizes without sharding. Sharded clusters are available on Atlas Core. You can deploy the following clusters from this page: Flex Clusters Flex clusters are low-cost cluster types suitable for teams who are learning MongoDB or developing small proof-of-concept applications. You can begin your project with an Atlas Flex cluster and scale the cluster tier to a production-ready Dedicated cluster at a future time. Flex clusters are more limited than Dedicated clusters. For information on these limitations, refer to [Configuration Limits.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-limits-config) Dedicated clusters Dedicated clusters include M10 and higher tiers. The M10 and M20 tiers are suitable for development environments and low-traffic applications, while higher tiers can handle large datasets and high-traffic applications. Dedicated clusters can be deployed into a single geographical region or multiple geographical regions. In public preview, all nodes in an Atlas Infinite cluster [deploy in the same region.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability) **Note:** If you choose to create a Dedicated cluster in Atlas Core, you also have the option to create a Global Cluster. For more information, refer to [Manage Global Clusters.](https://www.mongodb.com/docs/atlas/global-clusters.md#std-label-global-clusters) Atlas Infinite [doesn't support global clusters in public preview.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability) Free clusters A Free cluster provides a free sandbox replica set. You can deploy one Free cluster per Atlas project. Free clusters are more limited than Atlas Flex and Dedicated clusters. For information on these limitations, refer to [Configuration Limits.](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-shared-limits-config) 6) Select your preferred Cloud Provider & Region. The choice of cloud provider and region affects the configuration options for the available cluster tiers, network latency for clients accessing your cluster, the geographic location of the nodes in your cluster, and the [cost of running the cluster.](https://www.mongodb.com/docs/atlas/billing.md#std-label-billing-overview) To learn more about selecting a provider and region, refer to [Cloud Providers and Regions.](https://www.mongodb.com/docs/atlas/cloud-providers-regions.md#std-label-create-cluster-cloud-provider-region) From the Cloud Provider & Region section, you can also choose Multi-Cloud, Multi-Region & Workload Isolation. Multi-region clusters can better withstand data center outages and may contain dedicated geographic regions for localized reads, thereby improving performance. To learn how to deploy a multi-region cluster, see [Configure High Availability and Workload Isolation.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) During public preview, Atlas Infinite clusters don't support multi-cloud clusters. On an Atlas Infinite cluster, you can configure read-only nodes and analytics nodes for workload isolation. To learn more, see [Workload Isolation on Atlas Infinite clusters.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-atlas-infinite-workload-isolation) If you choose Multi-Cloud, Multi-Region & Workload Isolation, you can also choose to configure: - Electable nodes - Read-only nodes - Analytics nodes - Search nodes For information on these settings, see [Configure High Availability and Workload Isolation.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) During public preview, Atlas Infinite clusters support [select AWS regions.](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-atlas-infinite-aws-regions) 7) Select the Cluster Tier. On Atlas Core clusters, the cluster tier sets the RAM, vCPUs, IOPS (Input/Output Operations per Second) and storage for each [data-bearing node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-data-bearing-node) in the cluster. Depending on your cluster tier and cloud provider, you can customize storage capacity and IOPS (Input/Output Operations per Second) beyond the defaults for your cluster tier. To learn more, see [Customize Atlas Core Cluster Storage.](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-create-cluster-storage) On Atlas Infinite clusters, the cluster tier sets the RAM and vCPUs for each [compute node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-compute-node) in the cluster. The tier also fixes the storage IOPS (Input/Output Operations per Second) and storage throughput values. Storage scales independently of the cluster tier, and these values don't change as storage scales. To review the values for each tier, see [Atlas Infinite Storage IOPs and Throughput Values per Cluster Tier](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-atlas-infinite-storage-iops-throughput-values). To learn more about storage, see [Manage Storage on an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage) During public preview, Atlas Infinite clusters support the `M10` through `M60` General cluster tiers and the `M40` through `M60` Low-CPU cluster tiers. To learn more, see [supported cluster tiers.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-modify-cluster.md#std-label-atlas-infinite-modify-tier) To choose an appropriate tier and storage settings for your workload, see [Cluster Tiers](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-create-cluster-instance) and [Customize Atlas Core Cluster Storage.](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-create-cluster-storage) At this step, you can also: - [Select your cluster's generation](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-gen2-clusters) for `M30+` Dedicated clusters on AWS (Amazon Web Services) or Google Cloud. This applies to Atlas Core clusters only. Atlas Infinite clusters of `M30` and larger always run Gen2, and the `M10` and `M20` cluster tiers have no generation. - [Select a different tier for your Search Nodes](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-select-tiers-for-search-nodes). During public preview, Atlas Infinite clusters don't support Search Node tier selection. - You can [select a cluster tier](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-create-cluster-instance) appropriately sized for your analytics workload. To learn more, see [Analytics Nodes for Workload Isolation.](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-deploy-analytics-nodes) Both Atlas Core clusters and Atlas Infinite clusters support analytics nodes. An Atlas Infinite cluster supports up to 5 read-only and analytics nodes combined, in addition to its 2 electable nodes, for a maximum of 7 nodes. 8) Select any Additional Settings. From the Additional Settings section, you can: - [Version Availability](https://www.mongodb.com/docs/atlas/atlas-versions.md#std-label-atlas-version-availability) On Atlas Infinite clusters, Atlas sets the MongoDB version and you can't change it. - [Configure Backup Options for the Cluster](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-backups) On Atlas Infinite clusters, this setting is Additional Backup Retention. - [Termination Protection](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-termination-protection) - [Deploy a Sharded Cluster](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-sharding) - [Configure the Number of Shards](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-shardNum) Atlas Infinite clusters don't support sharding, so these two settings are unavailable. - [Manage Your Own Encryption Keys](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-enable-encryption) - [Configure Additional Options](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-more-configuration-options) 9) Specify the Cluster Details. From the Cluster Details section, you can: - Specify the Cluster Name. This label identifies the cluster in Atlas, and Atlas creates your hostname based on it. You can't change the cluster name after Atlas deploys the cluster. Cluster names can't exceed 64 characters in length. IMPORTANT: Atlas truncates the cluster name to *23 characters* in its internal interactions. In practice, this means: - Cluster names shorter than 23 characters can't end with hyphen or dash (`-`). - Cluster names 23 characters or longer can't use a hyphen or dash (`-`) as its 23rd character. - The first 23 characters in a cluster name must be unique within a project. Don't include [sensitive information](https://www.mongodb.com/docs/atlas/production-notes.md#std-label-sensitive-info) in your cluster name. - [Apply tags to the cluster.](https://www.mongodb.com/docs/atlas/database-deployment-tags.md#std-label-apply-tags-new-cluster) **Important:** Don't include sensitive information such as Personally Identifiable Information (PII) or Protected Health Information (PHI) in your resource tags. Other MongoDB services, such as Billing, can access resource tags. MongoDB also sends cluster resource tags to DataDog and Prometheus integrations. Resource tags are *not* intended for private and sensitive data. To learn more, see [Sensitive Information.](https://www.mongodb.com/docs/atlas/production-notes.md#std-label-sensitive-info) 10) Proceed to checkout. Click Create Cluster below the form. The billing address, payment method, and cost review steps that follow apply only if your organization doesn't have billing information on file. 11) Update your Billing Address details as needed. | Field | Necessity | Action | | --- | --- | --- | | Billing Email Address | Optional | Type the email address to which Atlas should send [billing alerts.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-billing-alerts) By default, Atlas sends billing alerts to the Organization Owners and Billing Admins. If you leave the Billing Email Address blank, Atlas sends billing alerts to the Organization Owners and Billing Admins.; If you specify a billing email address and uncheck Only send invoice emails to the Billing Email Address, Atlas sends billing alerts to the billing email address, Organization Owners, and Billing Admins.; If you specify a billing email address and check the box for Only send invoice emails to the Billing Email Address, Atlas send billing alerts to the billing email address only. | | Company Name | Optional | Type the name of the company for your billing address. | | Country | Required | Select the country for your billing address. You can also start typing the name of the country and then select it from the filtered list of countries. | | Street Address | Required | Type the street address for your billing address. | | Apt/Suite/Floor | Optional | Type an the apartment, suite, or floor for your billing address. | | City | Required | Type the name of the city for your billing address. | | State/Province/Region | Required | Type or select the political subdivision in which your billing address exists. The label and field change depending on what you selected as your **Country**: If you select **United States** as your **Country**, this label changes to **State**. The field changes to a dropdown menu of U.S. states. You can also start typing the name of the state and then select it from the filtered list of states.; If you select **Canada** as your **Country**, this label changes to **Province**. The field changes to a dropdown menu of Canadian provinces. You can also start typing the name of the province and then select it from the filtered list of provinces.; If you select any other country as your **Country**, this label changes to **State/Province/Region**. The field changes to a text box. Type the name of your province, state, or region in this box. | | ZIP or Postal Code | Required | Type the ZIP (U.S.) or Postal Code (other countries) for your billing address. | | VAT Number | Conditional | Atlas displays the VAT ID field if you select a country other than the United States. To learn more about VAT, see [VAT ID.](https://www.mongodb.com/docs/atlas/billing/international-usage.md#std-label-vat-id-number) If your company's billing address is in a country other than the United States (USA), Atlas typically charges VAT (Value Added Tax) if you do not enter a valid `VAT ID Number` on your [billing profile.](https://www.mongodb.com/docs/atlas/billing.md#std-label-atlas-billing-profile) IMPORTANT: If your billing address is in Ireland or certain Canadian provinces, Atlas always charges VAT (Value Added Tax), even with a valid `VAT ID Number`. To learn more about VAT (Value Added Tax) by region, see [International Usage and Taxation.](https://www.mongodb.com/docs/atlas/billing/international-usage.md#std-label-atlas-international-tax) | 12) Update your Payment Method details as needed. Click the radio button for Credit Card or Paypal. - If you selected Credit Card, type values for the following fields: | Field | Necessity | Action | | --- | --- | --- | | Name on Card | Required | Type the name that appears on your credit card. | | Card Number | Required | Type the 16-digit number that appears on your credit card. American Express uses a 15-digit number. | | Expiration Date | Required | Type the expiration date for your credit card in the two-digit month and two-digit year format. | | CVC (Card Verification Code) | Required | Type the three-digit number on the back of your credit card. American Express uses a 4-digit number found on the front of the credit card. | - If you selected PayPal: Click Pay with PayPal. Complete the actions on the PayPal website. **Note:** All projects within your organization share the same billing settings, including payment method. 13) Review the project's cost. Under the Cart section, review the following: | Field | Description | | --- | --- | | Cluster Tier | Displays cost for your selected cluster tier and configuration details. To learn more, see [Cloud Service Provider and Region](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-region-costs) and [Cluster Tier.](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-instance-size-costs) | | Included Features | Displays features included with your selected cluster configuration. | | Additional Settings | Displays additional settings that you enabled, such as cloud backups, sharding, [BI Connector](https://www.mongodb.com/docs/bi-connector/current/), and more. To learn more, see [Cloud Backups.](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-billing-backup-cloud-provider-snapshots) | Atlas Infinite doesn't support sharding in public preview, so sharding costs don't apply to an Atlas Infinite cluster. To learn how Atlas Infinite bills compute and storage, see [MongoDB Atlas Infinite Cluster Costs.](https://www.mongodb.com/docs/atlas/billing/atlas-infinite-costs.md#std-label-atlas-infinite-billing) 14) Deploy your cluster. Click Confirm and Deploy Cluster. **Important:** Each Atlas [project](https://www.mongodb.com/docs/atlas/organizations-projects.md#std-label-projects) supports up to 25 clusters. If you have questions or need assistance regarding the cluster limit, [contact support.](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support)