VPC Endpoint for Route 53

0

I am prototyping a scenario where a new VPC only has "intra" subnets (private with NO NAT Gateway).

We want to run a service inside the subnet that creates records in Route 53, but I cannot find any VPC endpoint for Route 53 in this list to create. This means our service tries to contact the Route 53 API and fails to do so until a timeout occurs.

I suspect (based on how many other services have an endpoint in the list above) this has not been implemented yet, or there are other ways to achieve this in a private "intra" subnet.

Can anyone advise?

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.

Thanks in advance for any help/guidance!

-gavin

gavin
已提問 2 個月前檢視次數 148 次
2 個答案
2

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.

profile picture
專家
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
profile pictureAWS
專家
已審閱 2 個月前
2

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.

profile pictureAWS
專家
iBehr
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
profile pictureAWS
專家
已審閱 2 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南