-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[apigateway] SpecRestAPI x-amazon-apigateway-endpoint-configuration
not usable for private API initial deployment
#9684
Comments
The requires investigation into how to correctly use |
Is there any plan to fix this? Or perhaps enable SpecRestAPI to use the EndpointConfiguration interface ? |
Is a workaround until above is implemented for any else facing the same issue. |
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
I also have a use case for the required feature. Is there a plan to address the issue? |
I am also having an issue with this. Same error, no VPC endpoint added to the REST Api after using SpecRestAPI. |
I'm facing the same issue too. Any suggested workaround? The one indicated by @rishavpaul doesn't seem to fix the problem for me. |
2023, and this is still not fixed. @RomainMuller can you help? |
This is still open, and is very annoying. Programmatic deployments shouldn't fail like this. |
It is not possible to use the swagger/openAPI
x-amazon-apigateway-endpoint-configuration
option in conjunction with the private endpointType.If you specify a vpce in the endpoint configuration, you get the following:
If you deploy the stack without the
x-amazon-apigateway-endpoint-configuration
, it does create a usable and private API Gateway, but the vpce is not defined in the 'Settings - Endpoint configuration' section.If you then deploy again the stack with the
x-amazon-apigateway-endpoint-configuration
, it does work, so this issue is only related to the initial creation of the API Gateway.Reproduction Steps
Using the following code:
Where the swagger inline is as shown:
Where the PPL::VPCId is the endpoint id and the PPL::LambdaAliasArn is the lambda alias arn.
We substitute those values dynamically but I don't thinks that is the issue.
What did you expect to happen?
I will expect to get a private API Gateway with the vpce defined in the 'Settings - Endpoint configuration' section.
What actually happened?
The deployment fails with the following message:
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: