massdriver-cloud / aws-rds-mysql Goto Github PK

Configure the UI schema for field order

Follow best practice alerts, document in operator guide, configure as locals that we can override via UI if necessary.

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MonitoringOverview.html

Add presets for:

• Development
• Production

If enhanced monitoring is enabled, include in alarms

Medium Pri

• Ensure RDS database has IAM authentication enabled (not part of any benchmarks)

Low Pri

• Ensure AWS resources that support tags have Tags

???

• Ensure RDS instances have Multi-AZ enabled

Automated Fixed

PR

• Ensure RDS database has IAM authentication enabled
• Ensure rotation for customer created CMKs is enabled

I originally bulk added these while setting up alarms and picked arbitrary values to test out the config. Need to reassess and pick solid relative values for the instance / config of this bundle.

When enabled, include Performance insights in md alarms

Include a localstack docker-compose with a default VPC for development/testing.

Add support for parameter groups. Link to here and accept a map<string,string>

• Artifact output?
• Alarms

For the artifact, I think we have two options...

1. Add a named authentication similar to policies and networks under security. This would give us a path to make many types of auth to a db (including app level).

• Pros: a lot of flexibility, Con: no direct representation in the diagram of the replicas.
• Breaking change to artifact definitions if we re-type the field, we'd need to make a new field for the named auths

2. Add a second artifact for the replicas.

• Pros: direct representation in the diagram for replicas, Cons: N replicas, we'd need to get DNS integrated to have a single hostname

3. One infrastructure artifact that describes the primary and its replicas, one auth artifact that describes all of the possible auths, including if enabled a load balanced replica hostname