AWS RDS Proxy Not Redirecting Traffic to Newly Created DB Instances
I'm building a feature where I'm updating my dependencies and I've searched everywhere and can't find a clear answer. I'm having a challenging scenario with AWS RDS Proxy where new database instances aren't being recognized by the proxy after they are created. I have set up the proxy to manage connections for my Aurora PostgreSQL cluster, but when I add a new instance to the cluster, the proxy still routes traffic only to the existing instances. I verified that the new instance is part of the cluster and is in the available state, but it seems like the proxy is not picking it up. I've tried the following steps: 1. **Rebooting the RDS Proxy** to see if it refreshes the connection pool. 2. **Updating the proxy configuration** to ensure it includes the new instance. 3. **Checking IAM permissions** to confirm that the proxy has the necessary access to the new instance. 4. **Reviewing CloudWatch logs** for any anomalies or errors. Here is the configuration I used when creating the RDS Proxy: ```json { "Name": "my-db-proxy", "EngineFamily": "POSTGRESQL", "RoleArn": "arn:aws:iam::123456789012:role/rds-proxy-role", "VpcSubnetIds": ["subnet-abc123", "subnet-def456"], "VpcSecurityGroupIds": ["sg-abc123"], "IdleClientTimeout": 300, "RequireTLS": true } ``` Despite these efforts, the new instance does not appear in the proxy's target group. The documentation mentions that it should automatically discover new instances, so I'm unsure why this isn't happening. Is there a specific setting I might be missing, or could it be a bug with the proxy? Any help or insights on how to troubleshoot this further would be greatly appreciated. For context: I'm using Json on macOS. What am I doing wrong? This is part of a larger application I'm building. Am I missing something obvious? I'm coming from a different tech stack and learning Json. Could this be a known issue? Thanks for taking the time to read this!