Q: What is Amazon DocumentDB (with MongoDB compatibility)?
A: Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Developers can use the same MongoDB application code, drivers, and tools as they do today to run, manage, and scale workloads on Amazon DocumentDB and enjoy improved performance, scalability, and availability without having to worry about managing the underlying infrastructure. Customers can use AWS Database Migration Service (DMS) for free (for six months) to easily migrate their on-premises or Amazon Elastic Compute Cloud (EC2) MongoDB databases to Amazon DocumentDB with virtually no downtime. There are no up-front investments required to use Amazon DocumentDB, and customers only pay for the capacity they use.
Q: What does "MongoDB-compatible" mean?
A: It means that vast majority of the applications, drivers, and tools you already use today with your MongoDB database can be used with Amazon DocumentDB with little or no change. Amazon DocumentDB emulates the responses that a client expects from a MongoDB server by implementing the Apache 2.0 open source MongoDB 3.6 API on a purpose-built, distributed, fault-tolerant, self-healing storage system that gives customers the performance, scalability, and availability they need when operating mission-critical MongoDB workloads at scale.
Q: How does Amazon DocumentDB work?
A: Amazon DocumentDB emulates the responses that a client expects from a MongoDB server by implementing the Apache 2.0 open source MongoDB 3.6 API on a purpose-built, distributed, fault-tolerant, self-healing storage system that gives customers the performance, scalability, and availability they need when operating mission-critical MongoDB workloads at scale.
Q: How can I migrate data from an existing MongoDB database to Amazon DocumentDB?
A: Customers can use AWS Database Migration Service (DMS) for free (for six months) to easily migrate their on-premises or Amazon Elastic Compute Cloud (EC2) MongoDB databases to Amazon DocumentDB with virtually no downtime. With DMS, you can migration from a MongoDB replica set or from a sharded cluster to Amazon DocumentDB. Additionally, you can use most existing tools to migrate data from a MongoDB database to AWS DocumentDB, including mongodump/mongorestore, mongoexport/mongoimport, and third-party tools that support Change Data Capture via the oplog.
Q: Do I need to change client drivers to use Amazon DocumentDB?
A: No, Amazon DocumentDB works with a vast majority of MongoDB drivers compatible with MongoDB 3.4+.
Q: Why are Amazon RDS permissions and resources required to use Amazon DocumentDB?
A: For certain management features such as instance lifecycle management, encryption-at-rest with Amazon Key Management Service (KMS) keys and security groups management, DocumentDB leverages operational technology that is shared with Amazon RDS.
Q: What instances types does DocumentDB offer?
Please see our pricing page for current information on available instant types per region.
Q: How do I try Amazon DocumentDB?
To try Amazon DocumentDB, please see the Getting Started section.
Q: Does Amazon DocumentDB have an SLA?
Yes. For more information, please see Amazon DocumentDB (with MongoDB compatibility) Service Level Agreement.
Q: What type of performance can I expect from Amazon DocumentDB?
When writing to storage, Amazon DocumentDB only persists a write-ahead logs, and does not need to write full buffer page syncs. As a result of this optimization, which does not compromise durability, Amazon DocumentDB writes are typically faster than traditional databases. Amazon DocumentDB clusters can scale out to millions of reads per second with up to 15-read replicas.
Q: How do I access my Amazon DocumentDB cluster?
A: Amazon DocumentDB clusters deployed within a VPC can be accessed directly by EC2 instances or other AWS services that are deployed in the same VPC. Additionally, Amazon DocumentDB can be accessed by EC2 instances or other AWS service in different VPCs in the same region or other regions via VPC peering. Access to Amazon DocumentDB instances must be done through the mongo shell or with MongoDB drivers. Amazon DocumentDB requires that you authenticate when connecting to DocumentDB.
Q: How much does Amazon DocumentDB cost?
A: Please see our pricing page for current pricing information.
Q: In which AWS regions is Amazon DocumentDB available?
A: Please see our pricing page for current information on regions and prices.
Q: Does Amazon DocumentDB have a free tier?
A: No, Amazon DocumentDB does not have a free tier.
Q: Amazon DocumentDB replicates each chunk of my storage volume six ways across three Availability Zones. Does that mean that my effective storage price will be three or six times what is shown on the pricing page?
A: No. Amazon DocumentDB’s storage replication feature is included in the price. You are charged based on the size of the data in your cluster and you are not charged separately for the replicated storage.
Q: What are IOs in Amazon DocumentDB and how are they calculated?
A: IOs are input/output operations performed by Amazon DocumentDB against an SSD-based virtualized storage layer. Every database page read operation counts as one IO. Amazon DocumentDB issues reads against the storage layer in order to fetch pages not present in the buffer cache. Each page is 8KB in Amazon DocumentDB.
Amazon DocumentDB was designed to eliminate unnecessary IO operations in order to reduce costs and to ensure resources are available for serving read/write traffic. Write IOs are only consumed when pushing write-ahead log records to the storage layer for the purpose of making writes durable. Write IOs are counted in 4KB units. For example, a log record that is 1KB will count as one IO operation. However, concurrent write operations whose write-ahead log is less than 4KB can be batched together by the Amazon DocumentDB database engine in order to optimize I/O consumption. Unlike traditional database engines Amazon DocumentDB never pushes modified database pages to the storage layer, resulting in further IO consumption savings.
You can see how many IOs your Amazon DocumentDB cluster is consuming by going to the AWS Console. To find your IO consumption, go to the Amazon DocumentDB section of the console, look at your list of clusters, select your Amazon DocumentDB cluster, then look for the “VolumeReadIOPs” and “VolumeWriteIOPs” metrics in the monitoring section.
Hardware, Scaling, and Storage
Q: What are the minimum and maximum storage limits of an Amazon DocumentDB cluster?
A: The minimum storage is 10GB. Based on your cluster usage, your Amazon DocumentDB storage will automatically grow, up to 64 TB in 10GB increments with no impact on performance. There is no need to provision storage in advance.
Q: How does Amazon DocumentDB scale?
A: Amazon DocumentDB scales in two dimensions: storage and compute. DocumentDB's storage automatically scales from 10GB to 64 TB in increments of 10GB. Amazon DocumentDB's compute capacity can be scaled up by creating larger instances and horizontally (for greater read throughput) by adding additional replica instances (up to 15) to the cluster.
Q: How do I scale the compute resources associated with my Amazon DocumentDB cluster?
A: You can scale the compute resources allocated to your instance in the AWS Management Console by selecting the desired instance and clicking the “modify” button. Memory and CPU resources are modified by changing your instance class.
When you modify your instance class, your requested changes will be applied during your specified maintenance window. Alternatively, you can use the "Apply Immediately" flag to apply your scaling requests immediately. Both of these options will have an availability impact for a few minutes as the scaling operation is performed. Bear in mind that any other pending system changes will also be applied.
Q: Does Amazon DocumentDB support MongoDB sharding?
A: No. Amazon DocumentDB's distributed storage architecture is a different approach to scaling than MongoDB sharding.
Backup and Restore
Q: How do I enable backups for my cluster?
A: Automated backups are always enabled on Amazon DocumentDB clusters. You can increase your backup window for point-in-time restores up to 35-days. Backups do not impact database performance.
Q: Can I take cluster snapshots and keep them around as long as I want?
A: Yes, manual snapshots can be retained beyond the backup window and there is no performance impact when taking snapshots. Note that restoring data from cluster snapshots requires creating a new cluster.
Q: If my instance fails, what is my recovery path?
A: Amazon DocumentDB automatically maintains six copies of your data across three Availability Zones and will automatically attempt to recover your instance in a healthy AZ with no data loss. In the unlikely event your data is unavailable within Amazon DocumentDB storage, you can restore from a cluster snapshot or perform a point-in-time restore operation to a new cluster. Note that the latest restorable time for a point-in-time restore operation can be up to five minutes in the past.
Q: What happens to my automated backups and cluster snapshots if I delete my cluster?
A: You can choose to create a final snapshot when deleting your instance. If you do, you can use this snapshot to restore the deleted instance at a later date. Amazon DocumentDB retains this final user-created snapshot along with all other manually created snapshots after the instance is deleted. Only snapshots are retained after the instance is deleted (i.e., automated backups created for point-in-time restore are not kept).
Q: What happens to my automated backups and cluster snapshots if I delete my account?
A: Deleting your AWS account will delete all automated backups and snapshot backups contained in the account.
Q: Can I share my snapshots with another AWS account?
A: Yes. Amazon DocumentDB gives you the ability to create snapshots of your cluster, which you can use later to restore a cluster. You can share a snapshot with a different AWS account, and the owner of the recipient account can use your snapshot to restore a cluster that contains your data. You can even choose to make your snapshots public – that is, anybody can restore a cluster containing your (public) data. You can use this feature to share data between your various environments (production, dev/test, staging, etc.) that have different AWS accounts, as well as keep backups of all your data secure in a separate account in case your main AWS account is ever compromised.
Q: Will I be billed for shared snapshots?
A: There is no charge for sharing snapshots between accounts. However, you may be charged for the snapshots themselves, as well as any clusters that you restore from shared snapshots.
Q: Can I automatically share snapshots?
A: We do not support sharing automatic cluster snapshots. To share an automatic snapshot, you must manually create a copy of the snapshot, and then share the copy.
Q: Can I share my Amazon DocumentDB snapshots across different regions?
A: No. Your shared Amazon DocumentDB snapshots will only be accessible by accounts in the same region as the account that shares them.
Q: Can I share an encrypted Amazon DocumentDB snapshot?
A: Yes, you can share encrypted Amazon DocumentDB snapshots. The recipient of the shared snapshot must have access to the KMS key that was used to encrypt the snapshot.
Q: Can I use Amazon DocumentDB snapshots outside of the service?
A: No, Amazon DocumentDB snapshots can only be used inside of the service.
Q: What happens to my backups if I delete my cluster?
A: You can choose to create a final snapshot when deleting your cluster. If you do, you can use this snapshot to restore the deleted cluster at a later date. Amazon DocumentDB retains this final user-created snapshot along with all other manually created snapshots after the cluster is deleted.
High Availability and Replication
Q: How does Amazon DocumentDB improve my cluster’s fault tolerance to disk failures?
A: Amazon DocumentDB automatically divides your storage volume into 10GB segments spread across many disks. Each 10GB chunk of your storage volume is replicated six ways, across three Availability Zones. Amazon DocumentDB is designed to transparently handle the loss of up to two copies of data without affecting write availability and up to three copies without affecting read availability. Amazon DocumentDB’s storage volume is also self-healing. Data blocks and disks are continuously scanned for errors and repaired automatically.
Q: How does Amazon DocumentDB improve recovery time after a database crash?
A: Unlike other databases, after a database crash Amazon DocumentDB does not need to replay the redo log from the last database checkpoint (typically 5 minutes) and confirm that all changes have been applied, before making the database available for operations. This reduces database restart times to less than 60 seconds in most cases. Amazon DocumentDB moves the cache out of the database process and makes it available immediately at restart time. This prevents you from having to throttle access until the cache is repopulated to avoid brownouts.
Q: What kind of replicas does DocumentDB support?
A: Amazon DocumentDB supports read replicas, which share the same underlying storage volume as the primary instance. Updates made by the primary instance are visible to all Amazon DocumentDB replicas.
Feature: Amazon DocumentDB read replicas
Number of replicas: Up to 15
Replication Type: Asynchronous (typically milliseconds)
Performance impact on primary: Low
Act as failover target: Yes (no data loss)
Automated failover: Yes
Q: Can I have cross-region replicas with Amazon DocumentDB?
A: No, Amazon DocumentDB does not support cross-region replicas
Q: Can I prioritize certain replicas as failover targets over others?
A: Yes. You can assign a promotion priority tier to each instance on your cluster. If the primary instance fails, Amazon DocumentDB will promote the replica with the highest priority to primary. If there are inconsistencies between two or more replicas in the same priority tier, then Amazon DocumentDB will promote the replica that is the same size as the primary instance.
Q: Can I modify priority tiers for instances after they have been created?
A: You can modify the priority tier for an instance at any time. Simply modifying priority tiers will not trigger a failover.
Q: Can I prevent certain replicas from being promoted to the primary instance?
A: You can assign lower priority tiers to replicas that you do not want promoted to the primary instance. However, if the higher priority replicas on the cluster are unhealthy or unavailable for some reason, then Amazon DocumentDB will promote the lower priority replica.
Q: How does Amazon DocumentDB assure high availability of my cluster?
A: Amazon DocumentDB can be deployed in a high-availability configuration by using replica instances in multiple AWS Availability Zones as failover targets. In the event of a primary instance failure, a replica instance is automatically promoted to be the new primary with minimal service interruption.
Q: How can I improve upon the availability of a single Amazon DocumentDB instance?
A: You can add additional Amazon DocumentDB replicas. Amazon DocumentDB replicas share the same underlying storage as the primary instance. Any Amazon DocumentDB replica can be promoted to become primary without any data loss and therefore can be used for enhancing fault tolerance in the event of a primary instance failure. To increase cluster availability, simply create 1 to 15 replicas, in multiple AZs, and Amazon DocumentDB will automatically include them in failover primary selection in the event of an instance outage.
Q: What happens during failover and how long does it take?
A: Failover is automatically handled by Amazon DocumentDB so that your applications can resume database operations as quickly as possible without manual administrative intervention.
- If you have an Amazon DocumentDB replica, in the same or a different Availability Zone, when failing over, Amazon DocumentDB flips the canonical name record (CNAME) for your cluster endpoint to a healthy replica, which is in turn is promoted to become the new primary. Start-to-finish, failover typically completes within 30 seconds. Additionally, the read replicas endpoint doesn't require any CNAME updates during failover.
- If you do not have an Amazon DocumentDB Replica (i.e. single instance), Amazon DocumentDB will first attempt to create a new instance in the same Availability Zone as the original instance. If unable to do so, Amazon DocumentDB will attempt to create a new instance in a different Availability Zone. From start to finish, failover typically completes in under 15 minutes.
Your application should retry requests in the event of connection loss.
Q: If I have a primary instance and an Amazon DocumentDB replica instance actively taking read traffic and a failover occurs, what happens?
A: Amazon DocumentDB will automatically detect a problem with your primary instance and begin routing your read/write traffic to an Amazon DocumentDB replica instance. On average, this failover will complete within 30 seconds. In addition, the read traffic that your Amazon DocumentDB replicas instances were serving will be briefly interrupted.
Q: How far behind the primary will my replicas be?
A: Since Amazon DocumentDB replicas share the same data volume as the primary instance, there is virtually no replication lag. We typically observe lag times in the 10s of milliseconds.
Security and Compliance
Q: Can I use Amazon DocumentDB in Amazon Virtual Private Cloud (Amazon VPC)?
A: Yes, all Amazon DocumentDB instances must be created in a VPC. With Amazon VPC, you can define a virtual network topology that closely resembles a traditional network that you might operate in your own datacenter. This gives you complete control over who can access your Amazon DocumentDB instances.
Q: How do the existing MongoDB authentication modes work with Amazon DocumentDB?
A: Amazon DocumentDB utilizes VPC’s strict network and authorization boundary. Authentication and authorization for Amazon DocumentDB management APIs is provided by IAM users, roles, and policies. Authentication to an Amazon DocumentDB database is done via standard MongoDB tools and drivers with Salted Challenge Response Authentication Mechanism (SCRAM), the default authentication mechanism for MongoDB.
Q: Does Amazon DocumentDB support encrypting my data-at-rest?
A: Amazon DocumentDB also allows you to encrypt your clusters using keys you manage through AWS Key Management Service (KMS). On a database instance running with Amazon DocumentDB encryption, data stored at rest in the underlying storage is encrypted, as are its automated backups, snapshots, and replicas in the same cluster. Encryption and decryption are handled seamlessly. For more information about the use of KMS with Amazon DocumentDB, see the Amazon DocumentDB User Guide.
Q: Can I encrypt an existing unencrypted cluster?
A: Currently, encrypting an existing unencrypted DocumentDB cluster is not supported. To use Amazon DocumentDB encryption for an existing unencrypted cluster, create a new cluster with encryption enabled and migrate your data into it.
Q: What compliance certifications does Amazon DocumentDB meet?
A: Amazon DocumentDB was designed to meet the highest security standards and to make it easy for you to verify our security and meet your own regulatory and compliance obligations. Amazon DocumentDB has been assessed to comply with PCI DSS, ISO 9001, 27001, 27017, and 27018, SOC 2, in addition to being HIPAA eligible. AWS compliance reports are available for download in AWS Artifact.
Visit the Amazon DocumentDB (with MongoDB compatibility) pricing page.
Instantly get access to the AWS Free Tier.
Get started building with Amazon DocumentDB (with MongoDB compatibility) in the AWS Console.