Update the instance type of AWS DocumentDB
We've been using documentDB for few months, the current instance type seems not enough since we started seeing exception in our application (yes alarm is not set yet)
MongoDB.Driver.MongoWriteException: A write operation resulted in an error. Operation timed out due to low available memory.
Can I change instance type of aws DocumentDB without losing Database or Data?
- Newest
- Most votes
- Most comments
With Amazon DocumentDB, the storage layer is decoupled from compute. You can scale at any time (either by adding a bigger instance, fail over to have the new instance the new Primary and then delete the old instance, or just by changing the type of the current instance) without losing any data. Furthermore, data is backed up (1 day retention by default) and streamed continuously to Amazon S3, for additional peace of mind.
You can scale document DB on the following Storage Scaling Instance Scaling Read Scaling Please read more here https://docs.aws.amazon.com/documentdb/latest/developerguide/db-cluster-manage-performance.html#db-cluster-manage-scaling-instance so the answer is yes, you can scale the instance type of your DocumentDB cluster without losing any data,
Relevant content
- Accepted Answerasked 6 years ago
- Accepted Answerasked 4 months ago
- How do I resolve issues with an Amazon DocumentDB instance that is in an incompatible-network state?
AWS OFFICIALUpdated 4 years ago - AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
Thank you! I was reading that documentation about the how, I did not find explicit information that my data will not be impacted, I will try that