Open IsmaelMartinez opened 4 years ago
The requires investigation into how to correctly use x-amazon-apigateway-endpoint-configuration
option in the OpenAPI definition.
Is there any plan to fix this? Or perhaps enable SpecRestAPI to use the EndpointConfiguration interface ?
let api = new SpecRestAPI(...)
(api.node.defaultChild as CfnRestApi).endpointConfiguration = {
types: [EndpointType.PRIVATE],
vpcEndpointIds: [ 'xyz' ],
};
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: Bug Report