fix: rightsize db instance#106
Open
infracost-autofix[bot] wants to merge 1 commit intomasterfrom
Open
Conversation
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💰 Infracost opened this pull request as part of the following campaign:
Policy: AWS RDS - consider rightsizing recommendation from AWS
AWS Compute Optimizer and Cost Optimization Hub analyzes your resources’ configuration and utilization metrics to provide rightsizing recommendations. These are based on resource utilization metrics Amazon CloudWatch for the last 14 days, or 3 months if you opted into "Enhanced recommendations", see https://docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html for details. This policy maps the recommendation to the infrastructure code that requires action.Risk: Medium
Depending on the size selected, changing the instance class may impact query performance.Deployment details: requires downtime, see AWS docs for details
The DB instance is upgraded in-place which can lead to service interruptions. The downtime depends on the configuration of your DB instance.
If you are using a single DB instance you can minimize the downtime by enabling blue/green updates. If you have Multi-AZ enabled, the secondary instance is upgraded first, after which a failover is performed and then the new secondary (former primary) instance is upgraded. The DB instance is unavailable during the failover time (60 - 120 seconds).
If you are using an RDS cluster, for minimal downtime you can update a read replica first and then manually fail over so it is promoted to the primary instance. Terraform does not handle rolling updates for RDS clusters natively, so you will need to ensure you roll out each instance individually.
Next steps:
✅ Deploy this change before the campaign deadline: June 31
💬 Doesn't apply? Close the PR with a comment
🛠️ Needs changes? Check out the branch to rebase or adjust