-
Notifications
You must be signed in to change notification settings - Fork 274
RDSC-4040 add note for RDS proxy #2203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset. In case there are security findings, they will be communicated to you as a comment inside the PR. Hope you’ll enjoy using Jit. Questions? Comments? Want to learn more? Get in touch with us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds documentation clarifying that RDS Proxy is not compatible with PostgreSQL databases and provides alternative setup instructions. The changes address a gap in the current documentation which incorrectly suggested using RDS Proxy for all source databases.
- Added warning about RDS Proxy incompatibility with PostgreSQL databases
- Provided alternative approaches for PostgreSQL in test and production environments
- Updated setup instructions to differentiate between MySQL/SQL Server and PostgreSQL workflows
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Currently we've documented that you should use RDS Proxy for all source databases, but that is not the case for the RDS Proxy. We have an initiative to try and improve this, but for the time being we must document the workaround for that database.
So here it is.