-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(aws-rds): Add lookup functonality #31720
Comments
Hi @JoshMcCullough , thanks for requesting this. As far as current implementation goes and mentioned in the linked issue as well,
Having an instance lookup method would definitely be useful. Thanks for volunteering for this implementation. Looking forward to your PR! |
I'd prefer if someone else would do the PR, but I can try ... maybe. |
If no one is currently working on this, I can take it. |
@pcheungamz , thanks for volunteering. please feel free to work on it. Looking forward to your PR! |
Hi @khushail, I would like your advice on my approach. After looking at .fromLookup in aws-route53.HostedZone, aws-ec2.Vpc, and aws-kms.Key. I think these are the steps:
Am I going down the right path? I don't think this is a small effort. Would appreciate your guidance. Thanks. |
Describe the feature
See related ticket: #7295
We would like a lookup function so we can fetch an RDS Database Instance reference by id, similar to other constructs.
Use Case
Currently, we need to provide many things (
instanceIdentifier
,instanceEndpointAddress
,port
,securityGroups
) in order to use an existing RDS Database Instance in the stack. This is "untenable" as hard-coding them is not a good idea.Proposed Solution
Add a lookup, e.g.:
Other Information
No response
Acknowledgements
CDK version used
2.161.0
Environment details (OS name and version, etc.)
Manjaro Linux
The text was updated successfully, but these errors were encountered: