[rds] Add more 11.9 for AuroraPostgresEngineVersionmodule

[1davidmichael]

Currently, a new version of Aurora Postgres Engine is available, 11.9. However, this is not supported by the CDK AuroraPostgresEngineVersion enum yet.

aws rds describe-db-engine-versions --engine aurora-postgresql --engine-version 11.9  --region us-east-1

{
    "DBEngineVersions": [
        {
            "Engine": "aurora-postgresql",
            "EngineVersion": "11.9",
            "DBParameterGroupFamily": "aurora-postgresql11",
            "DBEngineDescription": "Aurora (PostgreSQL)",
            "DBEngineVersionDescription": "Aurora PostgreSQL (Compatible with PostgreSQL 11.9)",
            "ValidUpgradeTarget": [],
            "ExportableLogTypes": [
                "postgresql"
            ],
            "SupportsLogExportsToCloudwatchLogs": true,
            "SupportsReadReplica": false,
            "SupportedEngineModes": [
                "provisioned"
            ],
            "SupportedFeatureNames": [
                "s3Import",
                "Comprehend",
                "s3Export",
                "SageMaker",
                "Lambda"
            ],
            "Status": "available",
            "SupportsParallelQuery": false,
            "SupportsGlobalDatabases": true
        }
    ]
}

Use Case

This AuroraPostgresEngineVersion of 11.9 is required to utilize the newest db.r6g instances in preview with the CDK.

https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-amazon-aurora-r6g-instance-types-powered-by-aws-graviton-2-processors-in-preview/

Proposed Solution

I will provide a PR for this:

  /** Version "11.9". */
  public static readonly VER_11_9 = AuroraPostgresEngineVersion.of('11.9', '11', { s3Import: true, s3Export: true });

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.