- Newest
- Most votes
- Most comments
Based on the details provided, the preferred way to connect your VPC Lambda function to the AWS Translate service is by using an interface VPC endpoint. This allows you to securely access the Translate API from within your VPC without using public IPs or traversing the public internet.
Moreover, AWS do have Translate service available in us-east-2 region (Service name - com.amazonaws.us-east-2.translate) and we can create Interface endpoint to access this service from VPC in us-east-2 region. I would suggest you use Interface endpoint to connect Lamda to Translate service in us-east-2 region.
Thank you for your answer. Indeed there is a Translate Service in region us-east-2, that appears in create Endpoint interface only when Ohio region is selected in Management Console (Endpoints can be created only for Services in selected Region).
In your specific case, if AWS Translate service is available only in the US-EAST-1 region and you have your Lambda function deployed in a VPC in another region (e.g., US-EAST-2), you would typically use cross-region VPC peering or a public endpoint. If the service does offer a VPC endpoint, you can use that for private connectivity within your VPC. Using a NAT Gateway is also an option if the service is accessible over the internet
Hope it clarifies and if does I would appreciate answer to be accepted so that community can benefit for clarity, thanks ;)
Relevant content
- asked 2 years ago
- Accepted Answerasked 3 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
After building the Endpoint in US-EAST-1, AWS provides a DNS that could be used by Lambdas in other regions (US_EAST-2).