How It Works
AWS DocumentDB is designed for applications that work with document-format data, such as JSON or BSON objects. Unlike a relational database, where data lives in rows and columns, a document database stores each record as a self-contained document with its own structure. AWS manages the underlying infrastructure, including storage, replication, and patching, so engineering teams do not need to operate the database layer themselves. DocumentDB clusters run continuously, which means costs accrue whether or not queries are actively running. That always-on billing model is the primary reason DocumentDB becomes a significant line item for teams with growing or persistent workloads.
Why It Matters for Cloud Cost
DocumentDB charges are based on instance hours, storage consumed, and I/O requests. Because clusters run around the clock, teams that pay purely on-demand rates pay a premium for capacity they could have reserved in advance. AWS does not offer a standard Savings Plan for DocumentDB, but it does support Reserved Instances, which allow teams to commit to a specific instance type in exchange for a lower hourly rate versus on-demand pricing. Teams that skip commitment planning for DocumentDB end up paying full on-demand rates for predictable, stable workloads, which is one of the more avoidable sources of cloud waste.
Usage AI: The Usage Flex DB Savings Plan covers DocumentDB alongside RDS and ElastiCache, saving teams 20 to 35% versus on-demand rates with no upfront payment and a guaranteed buyback on any underutilized capacity.