Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

ECS: supporting x-aws-assign_public_ip #2214

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

BackSlasher
Copy link

Allowing users to choose whether their instances should get a public IP address or not. Defaulting to "no".

What I did
Supporting x-aws-assign_public_ip in the service level.
If not present / set to a falsy value, the service should not get a public IP address.
If set to a truthy value, the current behavior exists (set by the provider's capability).
I'm not touching the EC2 section as it seems a bit messed up anyway, and I suspect it's not covered by tests.
Related issue

#2213

Created new "slightly complex" test to cover my change. I intend to reuse it later as well.

(not mandatory) A picture of a cute animal, if possible in relation with what you did
Called Dubi. A friendly street cat.
image

@github-actions github-actions bot added the ecs label Jan 10, 2023
@BackSlasher BackSlasher force-pushed the public-ip branch 2 times, most recently from 6be1902 to f6725e2 Compare January 10, 2023 22:12
@BackSlasher
Copy link
Author

comment for me: 6be1902

@BackSlasher
Copy link
Author

From testing, it seems that tasks without a public IP are unable to reach docker to pull images:
image

I might change the default to be "true" then, or move to changing the security group structure insteaad

Summary:
Can be used to test service-service interaction, and stacks with more than one service

Test Plan:
This is a test
Allowing users to choose whether their instances should get a public IP address or not.
Defaulting to "no".

Signed-off-by: Nitzan Raz <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant