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
We wanted to expose our backend through internet to external API Gateway (not aws!) and also wanted to retain the internal load balancer for vpc endpoint services traffic
Details:
Currently, copilot backend services and load balanced service only support 1 load balancer at a time. As you might aware, when we were to create target group to ECS with dynamic IPs, we can only do it while creating ECS services (in aws management console), not from Load balancer management console.
Observed result:
Only able to create 1 load balancer with existing manifest.yml.
Expected result:
Have another subblock under http to handle more than one load balancers.
Debugging:
The text was updated successfully, but these errors were encountered:
Description:
We wanted to expose our backend through internet to external API Gateway (not aws!) and also wanted to retain the internal load balancer for vpc endpoint services traffic
Details:
Currently, copilot backend services and load balanced service only support 1 load balancer at a time. As you might aware, when we were to create target group to ECS with dynamic IPs, we can only do it while creating ECS services (in aws management console), not from Load balancer management console.
Observed result:
Only able to create 1 load balancer with existing manifest.yml.
Expected result:
Have another subblock under
http
to handle more than one load balancers.Debugging:
The text was updated successfully, but these errors were encountered: