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.

Sign up for GitHub

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

Add instructions for secure AWS Task IAM Roles #2015

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

Add instructions for secure AWS Task IAM Roles #2015

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4606073
Support secure AWS Task IAM Roles
sodre Nov 19, 2019
50d713a
Match language
sodre Nov 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Support secure AWS Task IAM Roles 
The [Task IAM Rules]  were extracted verbatim from the Amazon documentation [steps 5, 6, and 7]( https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-install.html)

The latter two rules were adapted from [Amazon documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/instance_IAM_role.html) so that system-docker traffic retains access to the instance-metadata, while traffic from user-docker does not.

This documentation change is not sufficient to get Task IAM Roles to work, it requires a modification to the amazon-ecs-agent service, which will follow in a separate commit.
  • Loading branch information
@sodre
sodre authored Nov 19, 2019
commit 4606073f9b8856ca0ebe5adf3f313bdecf22b71e
19 changes: 18 additions & 1 deletion content/os/v1.x/en/installation/amazon-ecs/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,16 @@ rancher:
ECS_AVAILABLE_LOGGING_DRIVERS: |-
["json-file","awslogs"]
# If you have selected a RancherOS AMI that does not have ECS enabled by default,
# you'll need to enable the system service for the ECS agent.
# you'll need to enable the system service for the ECS agent, and configure the
# iptables rules.
sysctl:
net.ipv4.conf.all.route_localnet: 1
network:
post_cmds:
- iptables -t nat -A PREROUTING -p tcp -d 169.254.170.2 --dport 80 -j DNAT --to-destination 127.0.0.1:51679
- iptables -t nat -A OUTPUT -d 169.254.170.2 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 51679
- iptables --insert DOCKER-USER 1 --in-interface docker+ --destination 169.254.169.254/32 --jump DROP
- iptables --insert DOCKER-USER 1 --in-interface docker-sys --destination 169.254.169.254/32 --jump ACCEPT
services_include:
amazon-ecs-agent: true
```
Expand All @@ -48,6 +57,14 @@ rancher:
ECS_AGENT_VERSION: :v1.9.0
# If you have selected a RancherOS AMI that does not have ECS enabled by default,
# you'll need to enable the system service for the ECS agent.
sysctl:
net.ipv4.conf.all.route_localnet: 1
network:
post_cmds:
- iptables -t nat -A PREROUTING -p tcp -d 169.254.170.2 --dport 80 -j DNAT --to-destination 127.0.0.1:51679
- iptables -t nat -A OUTPUT -d 169.254.170.2 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 51679
- iptables --insert DOCKER-USER 1 --in-interface docker+ --destination 169.254.169.254/32 --jump DROP
- iptables --insert DOCKER-USER 1 --in-interface docker-sys --destination 169.254.169.254/32 --jump ACCEPT
services_include:
amazon-ecs-agent: true
```
Expand Down