Skip to content
This repository has been archived by the owner on May 6, 2024. It is now read-only.

How to specify AssignPublicIpEnabled ? #53

Open
agwaltz opened this issue Apr 26, 2018 · 6 comments
Open

How to specify AssignPublicIpEnabled ? #53

agwaltz opened this issue Apr 26, 2018 · 6 comments

Comments

@agwaltz
Copy link

agwaltz commented Apr 26, 2018

Digging around the code, I could not find a way to override this setting when creating services.

Is it possible to deploy services without a public IP?

@jpignata
Copy link
Contributor

jpignata commented Apr 26, 2018 via email

@agwaltz
Copy link
Author

agwaltz commented Apr 26, 2018

The available flags for fargate service create are great, especially the rule/ALB/target group which is a hassle to setup with the regular CLI.

However adding some of the aws ecs create-service flags to Fargate would be excellent!

--task-definition, --service-registries, --network-configuration, --health-check-grace-period-seconds are ones I would love to use here.

https://docs.aws.amazon.com/cli/latest/reference/ecs/create-service.html

@agwaltz
Copy link
Author

agwaltz commented Apr 26, 2018

aws elbv2 target-group --health-check-path also, for Express microservices which do not listen or respond to the default health-check on "/".

https://docs.aws.amazon.com/cli/latest/reference/elbv2/create-target-group.html

@vhuhtine
Copy link
Contributor

vhuhtine commented Jun 1, 2018

We wanted to disable public ip addresses so here is a pull request.
#57

PaulMaddox added a commit that referenced this issue Mar 14, 2019
How to specify AssignPublicIpEnabled ? #53
@zeisss
Copy link

zeisss commented Apr 29, 2020

anyone got an an example how to start tasks without public IPs? we tried this, but failed to talk to the docker registry.

@acro5piano
Copy link

Without public IPs, fargate tasks cannot pull container image. That is the default behavior.

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

No branches or pull requests

5 participants