awslabs
How to specify AssignPublicIpEnabled ?
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?
No, not currently. How should we approach supporting it?
On Thu, Apr 26, 2018 at 2:43 PM, Alan Gilmor [email protected] wrote:
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?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jpignata/fargate/issues/53, or mute the thread https://github.com/notifications/unsubscribe-auth/AABNPyxtEAl7X99LjOVbu4FphQ484OARks5tshVAgaJpZM4TmxcX .
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
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
We wanted to disable public ip addresses so here is a pull request. https://github.com/jpignata/fargate/pull/57
anyone got an an example how to start tasks without public IPs? we tried this, but failed to talk to the docker registry.
Without public IPs, fargate tasks cannot pull container image. That is the default behavior.
