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
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
This is either a question or a feature request, but I would love to be able to run two different services on the same port and then use path prefixes to route to each separately.
For example, svc1 and sc2 both run on port 80, then,
my-alb-1234567.us-east-1.elb.amazonaws.com/svc1 -> svc1 target group
my-alb-1234567.us-east-1.elb.amazonaws.com/svc2 -> svc2 target group
In AWS this is accomplished by creating listener rules for each path pattern. I don't believe it's possible to achieve this using x-aws-cloudformation overlay because the compose cli will attempt to create two listeners on the same port, which is forbidden.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This is either a question or a feature request, but I would love to be able to run two different services on the same port and then use path prefixes to route to each separately.
For example,
svc1
andsc2
both run on port 80, then,my-alb-1234567.us-east-1.elb.amazonaws.com/svc1 -> svc1 target group
my-alb-1234567.us-east-1.elb.amazonaws.com/svc2 -> svc2 target group
In AWS this is accomplished by creating listener rules for each path pattern. I don't believe it's possible to achieve this using
x-aws-cloudformation
overlay because the compose cli will attempt to create two listeners on the same port, which is forbidden.The text was updated successfully, but these errors were encountered: