-
Notifications
You must be signed in to change notification settings - Fork 115
How to specify AssignPublicIpEnabled ? #53
Comments
No, not currently. How should we approach supporting it?
…On Thu, Apr 26, 2018 at 2:43 PM, Alan Gilmor ***@***.***> 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
<#53>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABNPyxtEAl7X99LjOVbu4FphQ484OARks5tshVAgaJpZM4TmxcX>
.
|
The available flags for However adding some of the
https://docs.aws.amazon.com/cli/latest/reference/ecs/create-service.html |
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. |
How to specify AssignPublicIpEnabled ? #53
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. |
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?
The text was updated successfully, but these errors were encountered: