greedy52
commented
9 months ago Workarounds:
- Make Aurora custom endpoints, and assign the instance to that custom endpoint. Auto-discover does detect custom endpoints. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.Endpoints.html#Aurora.Endpoints.Custom
- Manually register the RDS instance (without auto-discovery)
What would you like Teleport to do
Add the ability to target and connect to individual RDS instances within a cluster, not just the RDS cluster's endpoint. Currently, a single Teleport database object is created for a given Cluster endpoint, even if there are more instances in the cluster.
While this request is specifically about RDS clusters, other cloud-hosted databases would benefit from this additional capability if they also have a similar limitation.
What problem does this solve?
Sometimes, direct connections to specific instances within an RDS cluster are required for operational tasks. This may include executing ad-hoc commands, adjusting configurations, or terminating an abnormal request that is running on a specific instance.
This limitation can hinder database management efficiency and can impact operational tasks, especially in emergency scenarios where teams need to directly connect to specific instances within a cluster.