[Feature request]: Supports for internal and public application load balancers

[rickychew77]

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:

[rubiconjosh]

@rickychew77 Heads up, no new features are under active development: https://github.com/aws/copilot-cli/discussions/5925#discussioncomment-10503700

In fact there are signs that this will receive no support at all: https://github.com/aws/copilot-cli/issues/5987

Full disclosure, I am not an AWS employee or maintainer of this project.

[rickychew77]

Thanks @rubiconjosh for the info. Saw the pr but the link about the announcement was 404 https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-copilot-cli-effective-february-3-2025/

sad news