v1.2.0

allow traffic inside security group @kevcube (#145)

boolean flag to enable intra-security group communication.

why

• we create our app infrastructure beginning with the database, then we use the output security group ID that gets created by Postgres as an input in our application, to give it database access
• previously what we've done is create the database, create the app, and add the app security group to the database's inputs, but this makes circular dependencies because our app depends on other outputs of the database

v1.1.0

Support for storage variables @matharoo (#141)

what

• Add support for storage variables storage_type, iops and allocated_storage.
• Fix broken tests

why

• Be able to specify the size and type of storage of the database in the cluster.

references

• closes #140
• aws_rds_cluster

v1.0.0 Aurora Serverless V2 support @topikachu

This release adds Aurora Serverless V2 support thanks to @topikachu.

The v1.0.0 designation is not especially significant. It is part of Cloud Posse's general policy to convert to production Semantic Versioning as we make updates to relatively mature modules.

Add aurora serverlessv2 support @topikachu (#138)

what

• Add aurora serverlessv2 support

why

• AWS releases aurora serverless v2.
• Adopt this new feature in this rds cluster module

references

• closes #137
• Terraform serverlessv2_scaling_configuration

Update test-framework to current @Nuru (#142)

what

• Update test-framework to current

why

• Enable parallel testing
• Bug fixes

git.io->cloudposse.tools update @dylanbannon (#136)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.50.2

🚀 Enhancements

Add optional `subnet_group_name` input to override the name @tjarjoura (#133)

what

• Allow the user to specify the db_subnet_group name, rather than using the default label ID

why

• If importing an existing database cluster and subnet group, we need to be able to set the subnet group name to what it already has, otherwise the subnet group will be recreated. This in turn will cause the database cluster to be recreated, which we don't want.

references

• https://sweetops.slack.com/archives/CB6GHNLG0/p1646336110444589

v0.50.1

🚀 Enhancements

Add enhanced monitoring attributes @nitrocode (#131)

what

• Add enhanced monitoring attributes

why

• The name can be too long at times and exposing this input could prevent the following error

│ Error: expected length of name to be in the range (1 - 64), got snip-snip-snip-snip-aurora-global-example-shared-enhanced-monitoring
│
│   with module.primary_aurora_postgres_cluster.aws_iam_role.enhanced_monitoring[0],
│   on .terraform-mdev/modules/primary_aurora_postgres_cluster/enhanced-monitoring.tf line 17, in resource "aws_iam_role" "enhanced_monitoring":
│   17:   name               = module.enhanced_monitoring_label.id

references

• Test results https://github.com/cloudposse/actions/actions/runs/1895037399
• Closed #132

v0.50.0

Add support for disabling egress traffic @jalgraves (#130)

what

• Add support for disabling egress security-group rule in default security group

why

tl;dr My boss told me to.

We had a third party do a pen test and afterwards they suggested we remove egress traffic from our DB subnets. If I'm missing something and there is another way to accomplish this without changing the module I'd be happy and grateful to hear it.

v0.49.2

🚀 Enhancements

Create dns record if not serverless @nitrocode (#128)

what

• Restore original logic

why

• Previous logic was to create the record when module was not serverless

references

• Previous PR #124

v0.49.1

🚀 Enhancements

Flag `master_username` output as sensitive @batistadasilva (#114)

what

• Flag master_username output as sensitive

why

Running on Terraform Cloud

Terraform v0.14.5
Configuring remote state backend...
Initializing Terraform configuration...

Error: Output refers to sensitive values

  on .terraform/modules/db/outputs.tf line 6:
   6: output "master_username" {

Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.

references

• https://www.terraform.io/upgrade-guides/0-14.html#sensitive-values-in-plan-output

v0.49.0

fix: prevent creating empty replicas record @syphernl (#126)

what

• Prevent creating empty DNS replicas record when cluster_size < 1

why

• If the cluster_size = 0 this would result in an attempt to create an empty DNS record, which is not permitted by the Route53 API

references

• Follow-up to changes done in #124

v0.48.1

🚀 Enhancements

Update AWS provider minimum version @alexjurkiewicz (#125)

what

• c96d859 added performance_insights_retention_period, which is supported in AWS provider v3.63.0 onwards.

why

• Prevent issues with older cached aws providers

references

N/A