Skip to content

RDS create-blue-green-deployment - The input parameter TargetResourceConfigurations is not supported. #10867

Closed as not planned

Description

@jorjuth

Describe the bug

When creating a RDS blue green deployment, the input parameter TargetResourceConfigurations is not supported.
The goal here is to rekey the Aurora green cluster (only option supported / documented so far).
The parameter is described in the awscli documentation and the API data type here.
It looks like an issue on the API side: it succesfully worked at the beginning of October, but the API data type seems to have been renamed from TargetResourceConfigurations to TargetResourceConfiguration. Failing since the mid-October.

It has been tested in multiple accounts / multiple regions, with the same result.

Expected Behavior

The blue green deployment should be successfully processed and the green cluster should be created on the configuration specified (new KMS key here).

Current Behavior

aws: [ERROR]: An error occurred (InvalidParameterCombination) when calling the CreateBlueGreenDeployment operation: The input parameter TargetResourceConfigurations is not supported.

Output log

output.log

Reproduction Steps

Tested with both variants:

aws rds create-blue-green-deployment \
       --blue-green-deployment-name $BG_NAME \
       --source $BG_ARN \
       --target-engine-version $BG_TARGET_VERSION \
       --target-db-cluster-parameter-group-name $BG_PGNAME \
       --target-resource-configuration "SourceArn=$BG_ARN,TargetKmsKeyId=$KMS"        
aws rds create-blue-green-deployment \
       --blue-green-deployment-name $BG_NAME \
       --source $BG_ARN \
       --target-engine-version $BG_TARGET_VERSION \
       --target-db-cluster-parameter-group-name $BG_PGNAME \
       --target-resource-configurations "SourceArn=$BG_ARN,TargetKmsKeyId=$KMS"        

CLI version used

aws-cli/2.39.6 Python/3.15.2 Darwin/25.6.0 source/arm64

Environment details (OS name and version, etc.)

macOS 26.7.2 (tested on WSL as well)

Activity

  1. added
    bugThis issue is a bug.
    needs-triageThis issue or PR still needs to be triaged.
    on Nov 9, 2026
  2. juliankock commented on Nov 11, 2026

    @juliankock

    We are also experiencing the same.

    I tried the following directly to the API on eu-west1.

    • TargetResourceConfigurations.TargetResourceConfiguration.1.SourceArn / .TargetKmsKeyId
      -> InvalidParameterCombination: The input parameter TargetResourceConfigurations is not supported.
    • Raw request, TargetResourceConfigurations.member.1.* -> same error.
    • Raw request, TargetResourceConfiguration.member.1.* and
      TargetResourceConfiguration.TargetResourceConfiguration.1.* -> deployment created,
      but green StorageEncrypted=false (parameter silently ignored, like any unknown name).
  3. faizalsomani commented on Nov 11, 2026

    @faizalsomani

    We’re seeing the same issue with Aurora PostgreSQL through Boto3 as well. The SDK accepts the documented cluster-level request, but the service returns:

    InvalidParameterCombination: The input parameter TargetResourceConfigurations is not supported.
    

    No blue/green deployment is created. Has a supported workaround been identified?

  4. jorjuth commented on Nov 12, 2026

    @jorjuth
    Author

    We’re seeing the same issue with Aurora PostgreSQL through Boto3 as well. The SDK accepts the documented cluster-level request, but the service returns:

    InvalidParameterCombination: The input parameter TargetResourceConfigurations is not supported.
    

    Confirmed behavior with boto3 too.


    Response from the support :

    The root cause of the error is that the TargetResourceConfigurations parameter in the CreateBlueGreenDeployment API is not currently supported for Aurora PostgreSQL clusters. All other aspects of your cluster configuration are valid for Blue/Green deployment. The issue is specifically and exclusively the TargetResourceConfigurations parameter used for KMS re-keying.

    CloudTrail event record from 6.10:

        "eventTime": "2026-10-06T12:50:49Z",
        "eventSource": "rds.amazonaws.com",
        "eventName": "CreateBlueGreenDeployment","userAgent": "aws-cli/2.37.9 md/awscrt#0.37.0 ua/2.1 os/linux#5.15.167.4-microsoft-standard-WSL2 md/arch#x86_64 lang/python#3.14.6 md/pyimpl#CPython m/s,r,Z,E,b cfg/retry-mode#standard md/installer#exe sid/0085e0a6faa0 md/distrib#ubuntu.22 md/prompt#off md/command#rds.create-blue-green-deployment",
        "requestParameters": {
            "blueGreenDeploymentName": "postgres-cluster-bgd",
            "source": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
            "targetEngineVersion": "18",
            "targetDBClusterParameterGroupName": "postgres-cluster-ca6c3ffb0649b54933217ad3a0",
            "targetResourceConfigurations": [
                {
                    "sourceArn": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
                    "targetKmsKeyId": "arn:aws:kms:eu-west-1:123456789012:key/xxxxxxxx"
                }
            ]
        },
        "responseElements": {
            "blueGreenDeployment": {
                "blueGreenDeploymentIdentifier": "bgd-zy3ktt6av4gferwi",
                "blueGreenDeploymentName": "cluster-bgd",
                "source": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
                "switchoverDetails": [
                    {
                        "sourceMember": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
                        "status": "PROVISIONING"
                    },
                    {
                        "sourceMember": "arn:aws:rds:eu-west-1:123456789012:db:application-autoscaling-xxxxxxxxx",
                        "status": "PROVISIONING"
                    },
                    {
                        "sourceMember": "arn:aws:rds:eu-west-1:123456789012:db:postgres-cluster-1",
                        "status": "PROVISIONING"
                    },
                    {
                        "sourceMember": "arn:aws:rds:eu-west-1:123456789012:db:postgres-cluster-2",
                        "status": "PROVISIONING"
                    }
                ],
                "tasks": [
                    {
                        "name": "CREATING_READ_REPLICA_OF_SOURCE",
                        "status": "PENDING"
                    },
                    {
                        "name": "DB_ENGINE_VERSION_UPGRADE",
                        "status": "PENDING"
                    },
                    {
                        "name": "CREATE_DB_INSTANCES_FOR_CLUSTER",
                        "status": "PENDING"
                    }
                ],
                "status": "PROVISIONING",
                "createTime": "2026-10-06T12:50:49Z",
                "tagList": []
            }
        },
    

    Latest try:

      "eventTime": "2026-11-02T20:23:41Z",
     "eventSource": "rds.amazonaws.com",
     "eventName": "CreateBlueGreenDeployment",
     "userAgent": "aws-cli/2.39.3 md/awscrt#0.38.0 ua/2.1 os/linux#5.15.167.4-microsoft-standard-WSL2 md/arch#x86_64 lang/python#3.14.8 md/pyimpl#CPython m/s,r,Z,E,b cfg/retry-mode#standard md/installer#script-exe sid/0478d72ef05f md/distrib#ubuntu.22 md/prompt#off md/command#rds.create-blue-green-deployment",
        "errorCode": "InvalidParameterCombinationException",
        "errorMessage": "An unknown error occurred",
        "requestParameters": {
            "blueGreenDeploymentName": "cluster-bgd",
            "source": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
            "targetEngineVersion": "18",
            "targetDBClusterParameterGroupName": "postgres-clusterca6c3ffb0649b54933217ad3a0",
            "targetResourceConfigurations": [
                {
                    "sourceArn": "arn:aws:rds:eu-west-1:123456789012:cluster:postgres-cluster",
                    "targetKmsKeyId": "arn:aws:kms:eu-west-1:123456789012:key/xxxxxxxx"
                }
            ]
        },
    

    It fails with awscli 2.37.9 or latest as well.
    More likely an issue on RDS API.

  5. juliankock commented on Nov 16, 2026

    @juliankock

    Works now on eu-west-1.

  6. jorjuth commented on Nov 16, 2026

    @jorjuth
    Author

    Confirmed working in us-east-2 as well.

  7. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    This issue is now closed. Comments on closed issues are hard for our team to see.
    If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugThis issue is a bug.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions