-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create RDS (non-Aurora) reusable terraform module #122
Comments
Task 1 The database is mostly used for data persistence rather than long-term storage which means our actual allocated storage doesn't need to be that large. The recommendation is to have a If the need arises, we could also set up an automated job (cron, lambda, etc) that drops data after one week. Additional reading |
Excellent! Thank you.
Does this mean that we should change this line to the following?
|
@rocketnova I think so? Nothing in the documents say if the values for |
@aplybeah I think it must be? The terraform argument reference says
And then the storage autoscaling section says:
Which implies to me that the example sets the base |
When you test out the implementation, could you try the following and see if it works as expected/hoped?
|
Sure! I'll give that a try. |
Task 2
|
I assume this these would be arguments on the |
@rocketnova I don't think the s3 bucket applies in our case, I misread something when I added that comment. But yes, these are arguments in |
@aplybeah Oh I see. What does the backup restore process look like if we use |
@rocketnova Every day there is a backup window that is about 30 min. We can either define when we want this backup to be, or use AWS's default time. During this time there may be increased latency, etc (nothing we need to be too concerned about), and the database creates a snapshot of the entire instance |
@aplybeah Are we talking about these RDS automated backups? If so, is this the correct restoration process? |
@rocketnova Yes we are, and that is the correct process. |
Ticket navapbc/wic-participant-recertification-portal#122 Changes Add database-serverless module that contains Aurora code Update database module to create RDS database Context for reviewers We discovered that AWS RDS Aurora v2 is more expensive than AWS RDS. On PRP, Aurora is costing ~$45/mo, even with very little load. On MWDP, RDS is costing ~$15/mo. Even though on large projects, the difference is not significant, it ends up being quite costly for our long-lived demo projects.
Context
We discovered that AWS RDS Aurora v2 is more expensive than AWS RDS. On PRP, Aurora is costing ~$150/mo, even with very little load. On MWDP, RDS is costing ~$15/mo. Even though on large projects, the difference of $135/mo is not significant, it ends up being quite costly for our long-lived demo projects.
In #116, we got really far on creating an RDS drop-in alternative to the RDS Aurora module. But the PR was never merged because 2 comments were not resolved.
Tasks
allocated_storage
should be for the participant portal should beThe text was updated successfully, but these errors were encountered: