Ensuring that your DocumentDB volumes are of type gp3 (General Purpose SSD) instead of gp2 is an important step in optimizing your database's performance and reducing costs. The gp3 volume type offers higher performance and more flexibility than the gp2 type, at a similar or lower cost.By switching to the gp3 volume type, you can improve the IOPS (input/output operations per second) and throughput performance of your database, and reduce the overall storage costs.
Here are some general remediation steps that you can follow to ensure that your DocumentDB volumes are of type gp3 (General Purpose SSD) instead of gp2:
- Review current instance settings: First, review the current settings of your DocumentDB instance and check whether it is using the gp2 volume type or not. You can do this by going to the AWS Management Console and navigating to the DocumentDB dashboard.
- Modify instance settings: If your instance is currently using the gp2 volume type, you can modify the instance settings to switch to the gp3 volume type. To do this, go to the "Modify" section of your DocumentDB instance and select the gp3 volume type from the "Storage Type" drop-down menu.
- Verify changes: After making changes to the instance settings, verify that the changes have been applied successfully. You can do this by checking the instance details in the DocumentDB dashboard.
- Monitor performance: Once you have switched to the gp3 volume type, monitor the performance of your DocumentDB instance to ensure that it meets your workload requirements. You can use Amazon CloudWatch to monitor the instance's CPU utilization, disk I/O, and other metrics.
- Optimize storage usage: To optimize the usage of your storage, you can also consider enabling auto-scaling for your DocumentDB instance. This will automatically adjust the storage capacity based on the workload demands, helping to reduce the storage costs.
By following these steps, you can ensure that your DocumentDB volumes are of type gp3 and are optimized for performance and cost-efficiency.
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.
