You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RDS create-blue-green-deployment - The input parameter TargetResourceConfigurations is not supported. #10867
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.
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).
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?
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.
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.
Activity
juliankock commentedon Nov 11, 2026
We are also experiencing the same.
I tried the following directly to the API on eu-west1.
-> InvalidParameterCombination: The input parameter TargetResourceConfigurations is not supported.
TargetResourceConfiguration.TargetResourceConfiguration.1.* -> deployment created,
but green StorageEncrypted=false (parameter silently ignored, like any unknown name).
faizalsomani commentedon Nov 11, 2026
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:
No blue/green deployment is created. Has a supported workaround been identified?
jorjuth commentedon Nov 12, 2026
Confirmed behavior with boto3 too.
Response from the support :
CloudTrail event record from 6.10:
Latest try:
It fails with awscli 2.37.9 or latest as well.
More likely an issue on RDS API.
juliankock commentedon Nov 16, 2026
Works now on eu-west-1.
jorjuth commentedon Nov 16, 2026
Confirmed working in us-east-2 as well.
github-actions commentedon Nov 18, 2026
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.