rds.NewCluster InvalidParameterCombination error when trying to enable advanced DBInsights Mode

[raywonkari]

Describe what happened

I am trying to enable the advanced db insights mode on an existing RDS cluster.. It already has performance insights enable and the default 7 day retention period set.

I have updated the provider to the latest v6.71.0 version, where the DBInsights feature was shipped.

When trying to set the advanced mode and with the retention period of 465 days, I get the InvalidParameterCombination error.

Full error:

InvalidParameterCombination: To enable the Advanced mode of Database Insights, modify your cluster to enable Performance Insights and set the retention period for Performance Insights to at least 465 days.: [email protected]

Sample program

rdsClusterArgs := rds.ClusterArgs{
  // other parameters
  PerformanceInsightsEnabled: pulumi.Bool(true),
  PerformanceInsightsRetentionPeriod: pulumi.Int(465)
  DatabaseInsightsMode: pulumi.String("advanced"),
}

auroradb, err := rds.NewCluster(ctx, dbName, &rdsClusterArgs, nil)

Log output

No response

Affected Resource(s)

No response

Output of pulumi about

NAME                                        VERSION
github.com/aws/aws-sdk-go-v2                v1.21.2
github.com/aws/aws-sdk-go-v2/config         v1.15.15
github.com/aws/aws-sdk-go-v2/service/ecs    v1.9.0
github.com/pulumi/pulumi-aws-native/sdk     v0.13.0
github.com/pulumi/pulumi-random/sdk/v4      v4.2.0
github.com/pulumi/pulumi/sdk/v3             v3.153.1
github.com/stretchr/testify                 v1.10.0
github.com/aws/aws-sdk-go                   v1.44.298
github.com/chartmogul/chartmogul-go/v3      v3.1.1
github.com/docker/docker                    v24.0.7+incompatible
github.com/go-git/go-git/v5                 v5.13.1
github.com/opencontainers/image-spec        v1.0.2
github.com/pulumi/pulumi-archive/sdk        v0.0.6
github.com/pulumi/pulumi-aws/sdk/v6         v6.71.0
github.com/pulumi/pulumi-cloudflare/sdk/v5  v5.16.0
github.com/pulumi/pulumi-command/sdk        v0.11.1
github.com/pulumi/pulumi-fastly/sdk/v8      v8.4.1
github.com/pulumi/pulumi-kubernetes/sdk/v4  v4.9.1
github.com/pulumi/pulumi-newrelic/sdk/v5    v5.32.1
github.com/pulumi/pulumi-tailscale/sdk      v0.13.3
github.com/tdewolff/minify/v2               v2.20.16
github.com/pulumi/pulumi-cloudflare/sdk/v3  v3.5.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[raywonkari]

I just tried to manually modify the cluster from the console and then run pulumi, it succeeded but in the first run it fails, so I am not sure if its pulumi/terraform or the AWS API rejecting the first request..

[corymhall]

@raywonkari thanks for reporting the issue. Can you provide a full example of your cluster configuration? I want to make sure I can reproduce it with your setup.

[raywonkari]

my code looks something like this

rdsClusterArgs := rds.ClusterArgs{
	AvailabilityZones:          az,
	BackupRetentionPeriod:      pulumi.Int(2),
	ClusterIdentifier:          pulumi.String("my-db"),
	CopyTagsToSnapshot:         pulumi.Bool(true),
	DatabaseName:               pulumi.String("postgres"),
	Engine:                     pulumi.String("aurora-postgresql"),
	EngineVersion:              pulumi.String("14.13"),
	MasterPassword:             pulumi.String("password"),
	MasterUsername:             pulumi.String("postgres"),
	DbSubnetGroupName:          pulumi.String("my-subnet-group"),
	VpcSecurityGroupIds:        pulumi.StringArray{
		pulumi.String("my-sg-id")
	},
	StorageEncrypted:           pulumi.BoolPtr(true),
	EnabledCloudwatchLogsExports: pulumi.StringArray{
		pulumi.String("postgresql"),
	},
	DbClusterParameterGroupName:        pulumi.String("my-cluster-pg"),
	IamDatabaseAuthenticationEnabled:   pulumi.Bool(true),
	MonitoringInterval:                 pulumi.Int(30),
	MonitoringRoleArn:                  pulumi.String("my-monitoring-role-arn"),
	PerformanceInsightsEnabled:         pulumi.Bool(true),
	DatabaseInsightsMode:               pulumi.String("advanced"),
	PerformanceInsightsRetentionPeriod: pulumi.Int(465),
}

auroradb, err := rds.NewCluster(ctx, dbName, &rdsClusterArgs)

I hope this example is good enough to reproduce..

[corymhall]

@raywonkari thanks, that helped! I was also able to reproduce this error in Terraform and based on my testing it might be an issue with AWS itself not allowing you to enable this on an existing cluster.

hashicorp/terraform-provider-aws#41792

[raywonkari]

Thanks @corymhall for following up, if it helps, I also have another observation..

if we update db insights to advanced mode on an existing cluster manually via the AWS console, it works, and then when we run pulumi again, it succeeds.. so not sure where the issue is..

Hope this observation helps figure out next steps

[raywonkari]

this was fixed and released via https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.92.0
can we bump the provider please? 🙌🏻

[raywonkari]

Thanks team, this is now resolved in the latest release v6.74.0 which contains the terraform provider bump to v5.92.0 by @guineveresaenger in #5372