- Newest
- Most votes
- Most comments
Hello.
The only option a colleague suggested was to create a VPC endpoint to Cloudformation and run a small stack there to create the records in Route 53. It might work, but seems a little hacky.
It's true that this is a slightly special workaround, but since Route53's VPC endpoints are currently not supported, I think this method is effective.
If this method cannot be used, you will need to create a NAT Gateway etc. and connect to Route53's API.
You could create a Lambda that you call and pass in a payload with information that you want to put in the Route 53 record. The Lambda will have access to the Route 53 API if you 1/ do not connect it to the VPC and 2/ the IAM role for the Lambda has permissions to create/update/delete records.
Hope this helps.
Relevant content
- Accepted Answerasked 2 years ago
- Accepted Answerasked a year ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago