Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Security Group on Fargate Service #24

Open
nicklester opened this issue May 7, 2020 · 1 comment
Open

Custom Security Group on Fargate Service #24

nicklester opened this issue May 7, 2020 · 1 comment

Comments

@nicklester
Copy link

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

@michaelwittig
Copy link
Contributor

Sorry for the late reply here.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants