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
I've implemented some changes in a fork to allow using API Gateway as a proxy to a Fargate service. I wanted to check here first if this is something that could be pushed back upstream, and if so how to go about it properly.
There are changes to both aws-apigateway and aws-ecs, and I wasn't sure whether it was fine to make changes to both in the same PR if they're related.
API Gateway Changes
Added connectionType to the IntegrationOptions, to allow specifying VPC_LINK.
Added requestParameters to the MethodOptions to allow setting proxy path variable.
ECS Changes
For LoadBalancedFargateService:
Added loadBalancerType prop to allow specifying a Network Load Balancer.
Added containerEnvironment prop to allow passing environment variables to the container.
I'm not using it personally, but for completeness it wouldn't be much effort to do the same for the LoadBalancedEcsService.
The text was updated successfully, but these errors were encountered:
I've implemented some changes in a fork to allow using API Gateway as a proxy to a Fargate service. I wanted to check here first if this is something that could be pushed back upstream, and if so how to go about it properly.
There are changes to both aws-apigateway and aws-ecs, and I wasn't sure whether it was fine to make changes to both in the same PR if they're related.
API Gateway Changes
Added
connectionType
to theIntegrationOptions
, to allow specifying VPC_LINK.Added
requestParameters
to theMethodOptions
to allow setting proxy path variable.ECS Changes
For
LoadBalancedFargateService
:loadBalancerType
prop to allow specifying a Network Load Balancer.containerEnvironment
prop to allow passing environment variables to the container.I'm not using it personally, but for completeness it wouldn't be much effort to do the same for the
LoadBalancedEcsService
.The text was updated successfully, but these errors were encountered: