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
When extending the subnet reach to public it still seems necessary to change the ingress rules to allow access to, say port 80 from the internet, to the container. I can't see a way to access a container from the internet using this template without using an Alb. I had to change the ingress rules through the AWS console.
It seems a high overhead to run an Alb for demo / CI type apps of which we will have many,
Maybe I have missed something?
Best Regards
The text was updated successfully, but these errors were encountered:
You are right, this module assume that you use an LB to route traffic.
I believe the beest option without an LB would be to port https://github.com/widdix/aws-cf-templates/blob/master/fargate/service-cloudmap.yaml to the modules. This way you con't have to mess around with IP addresses that change every time you deploy. Instead, you get a DNS name. Would that work? We have a few requests for this new module and I would like to add it if there is a need.
Hi.
When extending the subnet reach to public it still seems necessary to change the ingress rules to allow access to, say port 80 from the internet, to the container. I can't see a way to access a container from the internet using this template without using an Alb. I had to change the ingress rules through the AWS console.
It seems a high overhead to run an Alb for demo / CI type apps of which we will have many,
Maybe I have missed something?
Best Regards
The text was updated successfully, but these errors were encountered: