DBProxy | redis proxy、ssdb proxy（使用脚本控制sharding | Proxy library

Following extensive research, a two hour call with AWS support and very few search results for the error: PENDING_PROXY_CAPACITY

I stumbled across the following discussion: https://github.com/hashicorp/terraform-provider-aws/issues/16379

I had a couple of issues with my config:

1. Outbound rules for my RDS proxy security group was limited to internal traffic only. This causes problems as you need public internet access to access AWS Secrets manager!

2. At the time of writing the Terraform documentation here suggests you can pass a "username" option to the Auth block for the rds_proxy resource (see: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_proxy). This does not work, and returns an error stating the username option is not expected. This is because the rds_proxy expects all the information for Auth to be contained in one json object within the secret arn provided. For this reason I created a 2nd secret containing all the auth information like so:

A likely reason why your template fails is that your AWS::SecretsManager::Secret is not used and has incorrect values.

Your DB uses:

I tried to recreate the issues using my own Aurora cluster. I had to fill out a lot of blanks as there are only few bits and pieces provided in the question.

Havever, I had no problems creating proxy with the fixed role. The full template that I've used is below: