You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Feature Request
Is your feature request related to a problem? Please describe.
We have a Private API Gateway attached to a VPC where the API gateway URL is http://##########-vpce-???????????????????.execute-api.<aws region>.amazonaws.com
From what I understand, the route53 address is linked to the AWS CloudFront Distribution.
Describe the solution you'd like
It would be nice to have an option to link the Route53 address to the VPC Endpoint URL
The configurations for the VPC Endpoint are in serverless.xml
provider:
......# AWS API Setting for a private interfaceendpointType: PRIVATEvpcEndpointIds:
- ${self:custom.vpcendpoint.${self:provider.stage}}
Not sure if the npm plugin can read the existing serverless.xml configs and make the appropriate logical decisions or if additional configurations are required under customDomain:
custom:
customDomain:
vpcEndpoint: true
If this feature is developed, then from my knowledge, the A record needs to be linked to the API Gateway URL and not a CloudFront Distribution URL.
The text was updated successfully, but these errors were encountered:
txynidakis
changed the title
Support for a private API Gateway attached to a VPC Endpoit
Support for a private API Gateway attached to a VPC Endpoint
Sep 1, 2022
Community Note
Feature Request
Is your feature request related to a problem? Please describe.
We have a Private API Gateway attached to a VPC where the API gateway URL is
http://##########-vpce-???????????????????.execute-api.<aws region>.amazonaws.com
From what I understand, the route53 address is linked to the AWS CloudFront Distribution.
Describe the solution you'd like
It would be nice to have an option to link the Route53 address to the VPC Endpoint URL
The configurations for the VPC Endpoint are in serverless.xml
Not sure if the npm plugin can read the existing serverless.xml configs and make the appropriate logical decisions or if additional configurations are required under customDomain:
If this feature is developed, then from my knowledge, the A record needs to be linked to the API Gateway URL and not a CloudFront Distribution URL.
The text was updated successfully, but these errors were encountered: