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 was archived by the owner on Nov 27, 2023. It is now read-only.
I'm trying to set up some internally-facing docker services using the docker ECS integration, and am currently creating my own load balancer within our private VPC and then defining it using x-aws-loadbalancer. I'm wondering if instead of this, could I put the CloudFormation into the x-aws-cloudformation overlay and maintain everything with the docker compose lifecycle? I think that would be very clean and simplify our setup quite a bit. I've tried using the x-aws-cloudformation overlay with a resource entry like the following to manually set the load balancer:
VPC vpc-id should have at least 2 associated public subnets in different availability zones
Is there any possibility of supporting load balancer configuration in the overlay like this? Essentially I think this would require skipping the automated load balancer setup if LoadBalancer is present in the x-aws-cloudformation Resources entry. Alternatively, having private VPC support would also solve this issue because I wouldn't need to set up a custom LoadBalancer entry, although I saw #1064 so I assume this probably won't be supported.
Thanks for taking a look! I really appreciate docker and the ECS integration is awesome, so I'm hoping to see if I can find a nice way around this.
The text was updated successfully, but these errors were encountered:
x-aws-cloudformation is an opaque attribute for ECS integration, to be applied as a patch to the compose->CF converted templated. So we can't use it to retrieve subnet information and change the conversion process.
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.
Hello!
I'm trying to set up some internally-facing docker services using the docker ECS integration, and am currently creating my own load balancer within our private VPC and then defining it using
x-aws-loadbalancer
. I'm wondering if instead of this, could I put the CloudFormation into thex-aws-cloudformation
overlay and maintain everything with the docker compose lifecycle? I think that would be very clean and simplify our setup quite a bit. I've tried using thex-aws-cloudformation
overlay with a resource entry like the following to manually set the load balancer:but I get the error message:
Is there any possibility of supporting load balancer configuration in the overlay like this? Essentially I think this would require skipping the automated load balancer setup if
LoadBalancer
is present in thex-aws-cloudformation
Resources entry. Alternatively, having private VPC support would also solve this issue because I wouldn't need to set up a customLoadBalancer
entry, although I saw #1064 so I assume this probably won't be supported.Thanks for taking a look! I really appreciate docker and the ECS integration is awesome, so I'm hoping to see if I can find a nice way around this.
The text was updated successfully, but these errors were encountered: