Documentdb Storage
Storage configuration guidance for Azure DocumentDB — when and how to use Premium SSD v2 high-performance storage, IOPS/bandwidth caps that are gated by compute tier (not disk size), Premium SSD v2 limitations (no CMK, migration paths, disk-hydration sequencing), and storage capacity change limits. Use when picking a storage type at cluster creation, sizing for I/O-intensive workloads, migrating…
Install
$ agentstack add skill-azure-documentdb-agent-kit-storage ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Storage — Azure DocumentDB
Azure DocumentDB clusters use remote premium SSD storage. Two disk types are offered:
| Storage type | IOPS / bandwidth scaling | Max IOPS | CMK | Use it for | |---|---|---|---|---| | Premium SSD (v1) | Scales with disk capacity — bigger disk → higher IOPS | 20,000 | ✔️ | Legacy clusters, scenarios that require CMK | | Premium SSD v2 | Decoupled from disk size — IOPS/bandwidth gated by compute tier | 80,000 | ❌ | New production clusters; any I/O-intensive workload |
Premium SSD v2 is the default recommendation for new clusters. It delivers up to a 12× performance boost at no added cost by removing the disk-size lever from the IOPS equation — you size storage for capacity and size compute for throughput, independently.
How Premium SSD v2 changes sizing
On Premium SSD v1, hitting 20,000 IOPS required provisioning a 20 TB disk even when only ~1 TB of data was stored. On Premium SSD v2, the highest achievable IOPS and bandwidth for the chosen compute tier are auto-configured regardless of disk size:
- Choose storage size based on how much data the cluster will hold.
- Choose compute tier based on how much IOPS / MBps the workload needs (see [storage-tier-iops-caps](storage-tier-iops-caps.md)).
- No knobs to tune — the upper-bound IOPS/bandwidth for the tier are applied automatically at no extra cost.
Rules
- [storage-choose-premium-ssdv2](storage-choose-premium-ssdv2.md) — When to pick Premium SSD v2 vs Premium SSD; the CMK trade-off.
- [storage-tier-iops-caps](storage-tier-iops-caps.md) — Compute-tier → max IOPS / MBps table; size compute for throughput, not disk for IOPS.
- [storage-premium-ssdv2-limitations](storage-premium-ssdv2-limitations.md) — Known limits: no CMK, capacity-change cap, replication restrictions, no online v1→v2 migration.
- [storage-disk-hydration-sequencing](storage-disk-hydration-sequencing.md) — Space out compute scale / storage scale / HA-enable operations while the disk is hydrating.
References
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Azure
- Source: Azure/documentdb-agent-kit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.