Skip to content

MI-312: Add default aspect for S3 and DynamoDB#1630

Open
kai-nguyen-aligent wants to merge 4 commits intomainfrom
feat/MI-312-default-aspect-for-stateful-resources
Open

MI-312: Add default aspect for S3 and DynamoDB#1630
kai-nguyen-aligent wants to merge 4 commits intomainfrom
feat/MI-312-default-aspect-for-stateful-resources

Conversation

@kai-nguyen-aligent
Copy link
Contributor

Description of the proposed changes

  • Add default aspect for S3 and DynamoDB

Notes to reviewers

🛈 When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

@kai-nguyen-aligent kai-nguyen-aligent marked this pull request as ready for review March 16, 2026 10:32
@kai-nguyen-aligent kai-nguyen-aligent requested a review from a team as a code owner March 16, 2026 10:32
@kai-nguyen-aligent kai-nguyen-aligent requested review from AdamJHall, NgaNaNa, TheOrangePuff and aaronmedina-dev and removed request for NgaNaNa March 16, 2026 10:32
AdamJHall
AdamJHall previously approved these changes Mar 17, 2026
case "MEDIUM":
return {
pointInTimeRecoverySpecification: {
pointInTimeRecoveryEnabled: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there many INT use cases that require PITR? I would think that most of the things we store in dynamo wouldn't require it or could be rebuilt relatively easily without it?

PITR is relatively cheap ($0.228 per GB-month) so it doesn't matter too much, but it is an added cost and devs should be aware so we aren't storing too much in them with PITR enabled.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, Adam. I don't think INT has many use cases for this. I'll remove this setting.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @AdamJHall I have made some changes to this aspect:

  1. Removed pointInTimeRecoveryEnabled configuration.
  2. Added billingMode with some thoughput configurations:
    a. SHOT now has provisioned thoughput with read/write capacity = 1 for optimal cost
    b. MEDIUM & LONG have on demand thoughput but MEDIUM has a cap of 100 RCUs/WCUs for enough for realistic functional/integration testing in Staging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants