I am trying to connect my AWS App Runner service to an Amazon RDS database that is privately accessible and located in the default VPC. Here is the configuration I've set up:

RDS Configuration:

The RDS instance is in the default VPC.
It has associated subnets and security groups.
App Runner Configuration:

Incoming Traffic: Set to be publicly accessible.
Outgoing Traffic: Created a VPC connector and added it to the outgoing traffic configuration.
Selected the same VPC, subnets, and security groups as those used by the RDS instance.
However, when I save these changes and deploy the App Runner service, the deployment fails and rolls back with the message: "Successfully rolled back update of my-service-name."

Question:
Do I need to make changes in both incoming and outgoing traffic settings in App Runner, or just in the outgoing traffic, to successfully connect to the privately accessible RDS instance? What specific settings should I use for the VPC, subnets, and security groups in the VPC connector?

Additional Details:

The RDS security group allows inbound traffic from the App Runner service.
The App Runner service needs to have network connectivity to the RDS instance to perform database operations.
Any help or suggestions on how to resolve this issue would be greatly appreciated. Thank you!

All Content tagged with AWS Clean Rooms ML

How to Successfully Connect AWS App Runner with a Privately ...