use rds proxy port instead of proxy target port#35347
Conversation
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
smallinsky
left a comment
There was a problem hiding this comment.
Linter seems to complain about unused getRDSProxyTargetPort function Otherwise LGTM.
greedy52
left a comment
There was a problem hiding this comment.
If removing getRDSProxyTargetPort, we can also remove the corresponding IAM action from AWS configurator
|
The PR changelog entry failed validation: The changelog entry must start with a letter. |
|
The PR changelog entry failed validation: The changelog entry must start with a letter. |
|
🤖 Vercel preview here: https://docs-pu7etpl3q-goteleport.vercel.app/docs/ver/preview |
|
@GavinFrazar See the table below for backport results.
|
Backport #35347 to branch/v12.
* [v12] use rds proxy port instead of proxy target port Backport #35347 to branch/v12. * remove unused test mock func
fixes #35268
I tested that discovery works correctly with this change for MySQL, Postgres, and MSSQL Server, and that connections work as well regardless of target database port.
changelog: IAM permissions for rds:DescribeDBProxyTargets are no longer required for RDS Proxy discovery.