MongoDB Atlas¶
What’s New in Atlas
- Available in Beta: MongoDB Stitch.
- MongoDB Stitch is a backend as a service that provides an HTTP API to MongoDB, integration with other services, and a declarative rules infrastructure which spans database and service actions.
- Ability to specify MongoDB user roles at a collection level.
- Ability for owners of a group to kill slow running operations.
- Ability to live migrate MongoDB version 3.0/3.2 replica set to an Atlas 3.4 cluster.
- Ability to restore to clusters in different group.
- Support for deploying clusters on the Google Cloud Platform and Microsoft Azure
Video Series Available
MongoDB Atlas is a cloud service for running, monitoring, and maintaining MongoDB deployments, including the provisioning of dedicated servers for the MongoDB instances. In addition, Atlas provides the ability to introspect collections, query backups, and migrate data from existing MongoDB replica set into an Atlas cluster.
MongoDB Deployments¶
MongoDB deployments, or “clusters” in Atlas, can be either a replica set or a sharded cluster.
MongoDB Versions¶
Atlas supports MongoDB 3.2 and MongoDB 3.4 with the WiredTiger storage engine. By default, Atlas uses MongoDB 3.4. You can specify the MongoDB version when you create a cluster. If a created cluster uses MongoDB 3.2, you can upgrade to MongoDB 3.4 when you scale a cluster.
As new maintenance releases become available, Atlas automatically upgrades to these releases via a rolling process to maintain cluster availability.
If the workload on the Atlas cluster is such that it impedes operations, including the ability to scale, MongoDB Atlas may, in some situations, create indexes in your cluster as a safeguard.
Deployment¶
Atlas deploys mongod process to its own instance.
For sharded clusters, the six routers (the mongos
processes) run on six of the shard servers; i.e. each of the six
mongos processes shares an instance with one mongod process.
Depending on the cloud provider and region selected for the Atlas group, Atlas distributes each cluster across the region for high availability. For more information on how Atlas manages cluster distribution, see Amazon Availability Zones for AWS, GCP Zones for GCP, and Azure Fault Domains for Azure.
Atlas deploys each cluster with mandatory security.
Atlas Group¶
Your Atlas group manages your MongoDB deployments. An Atlas group can have multiple MongoDB clusters.
When Atlas deploys an Atlas group’s first M10+ paid cluster,
Atlas also creates a VPC specific to
the cloud service provider and region selected for the cluster.
Atlas associates all subsequent clusters deployed in the group to this
VPC, locking them to the cloud service
provider and region. Atlas also sets a default VPC CIDR block address
for the group.
For clusters deployed on Amazon Web Services, Atlas supports creating
VPC peering connections between your
Atlas clusters and other AWS VPCs in the
same region. If you need a specific Atlas VPC CIDR block address, configure a VPC peering
connection before creating your first M10+
cluster.
For Atlas clusters deployed on Google Cloud Platform or Microsoft Azure, add the IP addresses of your GCP or Azure services to Atlas group IP whitelist to grant those services access to the cluster.
Security¶
Atlas secures your deployments through the use of TLS/SSL, virtual private cloud (VPC) subnet with IP whitelists, and user authentication and authorization.
Support¶
Atlas provides support for the use of the service itself. Support for development and performance of the database itself requires a MongoDB subscription. For details, contact MongoDB Inc..
Next Steps¶
To get started, see Getting Started.
Additional Resources¶
For more resources, see Videos & Other Resources.