Skip to content

Release/custom backup retention period#23

Open
dupontz wants to merge 4 commits into
theonestack:masterfrom
dupontz:release/custom-backup-retention-period
Open

Release/custom backup retention period#23
dupontz wants to merge 4 commits into
theonestack:masterfrom
dupontz:release/custom-backup-retention-period

Conversation

@dupontz

@dupontz dupontz commented May 7, 2026

Copy link
Copy Markdown

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Aurora PostgreSQL CloudFormation DSL template to support configuring cluster backup retention and adjusts DB instance resource logical IDs.

Changes:

  • Add support for a configurable backup_retention_period and set BackupRetentionPeriod on the AWS::RDS::DBCluster.
  • Rename the writer and reader AWS::RDS::DBInstance logical IDs (currently to DBClusterInstance and DBClusterInstances).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread aurora-postgres.cfndsl.rb
Condition("EnableReader", FnEquals(Ref("EnableReader"), 'true'))

RDS_DBInstance(:DBClusterInstanceWriter) {
RDS_DBInstance(:DBClusterInstance) {
Comment thread aurora-postgres.cfndsl.rb
reader_maintenance_window = external_parameters.fetch(:reader_maintenance_window, nil)

RDS_DBInstance(:DBClusterInstanceReader) {
RDS_DBInstance(:DBClusterInstances) {
Comment thread aurora-postgres.cfndsl.rb
Comment on lines +179 to +185
backup_retention_period = external_parameters.fetch(:backup_retention_period, 1)

# for serverless v2 the EngineMode property in the DBCluster is to be left unset

RDS_DBCluster(:DBCluster) {
Engine 'aurora-postgresql'
BackupRetentionPeriod backup_retention_period
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