1 Answer
- Newest
- Most votes
- Most comments
2
You should ensure that you are configuring your App Runner instance to run within the VPC. From inside the VPC it should be able to access protected resources like the DocumentDB instance.
You can follow this walkthrough guide to help you configure the desired architecture. https://aws.amazon.com/blogs/containers/observability-for-aws-app-runner-vpc-networking/
I hope this resolves your issues.
Relevant content
- asked a month ago
- asked 2 years ago
- asked 18 days ago
- asked 2 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 8 months ago
Hi Justin, thank you for your quick reply.
I already tried that, but still no luck. I've re-created the VPC, security groups, and everything. I continue having the following timeout error:
I tried also using a DocumentDB cluster with TLS disabled and had the same error
Hey Mario, can you share the App Runner code that you are using to connect to the database from within the application? Please change or redact any sensitive information such as username and/or password.
Hi Justin! Here is a summary of how my App Runner creates a connection to DocumentDB. It works fine when trying to connect a Lamba Function with that DocumentDB cluster (tls is enabled), but not when trying to connect the App Runner.
With the same code, I get the following error messages on the App Runner:
I tried registering this certificate https://truststore.pki.rds.amazonaws.com/global/global-bundle.pem when the app starts, but still does not work :(
I finally fixed the issue. Following some recommendations I've found in this post: https://stackoverflow.com/questions/67013408/cert-error-connecting-to-aws-documentdb-from-docker-c-sharp-app
I've included the following lines on my dockerfile:
I just want to thank Justin who helped me a lot with the walkthrough guide he provided me.
I am glad you resolved your problem! I'm always happy to help.