adam/proposal-system
1
0
Fork 0
mirror of https://github.com/Sea-Haven-Industries/proposal-system.git synced 2026-10-07 10:28:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix(infra): give the Aurora cluster a distinct construct ID

Browse source 
The RDS->Aurora swap (PR3 #125) kept construct ID 'Database', so CloudFormation
saw the same logical ID change from AWS::RDS::DBInstance to AWS::RDS::DBCluster and
rejected the changeset ('Update of resource type is not permitted'). Renaming the
construct to 'AuroraCluster' gives the cluster a new logical ID, so CFN does a clean
replace (remove old DBInstance, add new DBCluster) instead of an in-place type change.
This commit is contained in:
Adam Moussa 2026-06-15 10:59:24 -04:00
parent aff38a11ae
commit 516dd39f55
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
infra/lib/foundation-stack.ts
View file

@ -88,7 +88,11 @@ export class FoundationStack extends cdk.Stack {
// PR3: replaced the RDS instance + OpenSearch Serverless with Aurora + pgvector
// (kills the AOSS OCU floor; scales toward 0 ACU when idle). Data API is required
// by Bedrock Knowledge Bases to query the vector table.
const dbCluster = new rds.DatabaseCluster(this, 'Database', {
// Construct ID is 'AuroraCluster' (not 'Database') so CloudFormation gets a NEW
// logical ID for the cluster — the old RDS DBInstance shared logical ID 'Database*'
// and CFN forbids changing a resource's type in place ("Update of resource type is
// not permitted"). A distinct ID makes it a clean replace instead.
const dbCluster = new rds.DatabaseCluster(this, 'AuroraCluster', {
clusterIdentifier: `proposal-system-db${config.stackSuffix}`,
engine: rds.DatabaseClusterEngine.auroraPostgres({
version: rds.AuroraPostgresEngineVersion.VER_15_4,