-
Notifications
You must be signed in to change notification settings - Fork 4.4k
(apigatewayv2-integrations): Set SecureServerName with higher level HTTP API libraries #14036
Copy link
Copy link
Closed
Labels
@aws-cdk/aws-apigatewayv2-integrationsRelated to AWS APIGatewayv2 IntegrationsRelated to AWS APIGatewayv2 Integrationseffort/smallSmall work item – less than a day of effortSmall work item – less than a day of effortfeature-requestA feature should be added or improved.A feature should be added or improved.feature/enhancementA new API to make things easier or more intuitive. A catch-all for general feature requests.A new API to make things easier or more intuitive. A catch-all for general feature requests.p2
Description
I'd like to have the ability to set the SecureServerName for HTTP APIs with L2 or L3 constructs. Setting the SecureServerName through Cloudformation can be done through AWS::ApiGatewayV2::Integration's property TlsConfig.
Use Case
Functionality only exists in L1 construct, would like to be able to set SecureServerName using higher level libraries
Proposed Solution
tbd
Other
Sourced from guidance issue #13673
- 👋 I may be able to implement this feature request
-
⚠️ This feature might incur a breaking change
This is a 🚀 Feature Request
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
@aws-cdk/aws-apigatewayv2-integrationsRelated to AWS APIGatewayv2 IntegrationsRelated to AWS APIGatewayv2 Integrationseffort/smallSmall work item – less than a day of effortSmall work item – less than a day of effortfeature-requestA feature should be added or improved.A feature should be added or improved.feature/enhancementA new API to make things easier or more intuitive. A catch-all for general feature requests.A new API to make things easier or more intuitive. A catch-all for general feature requests.p2