Keep responses under one page in length. Anything bigger should go in a file.
Keep files organized. Use a schema, but don't be precious about it.
| *filter | |
| :INPUT DROP | |
| :FORWARD DROP | |
| :OUTPUT ACCEPT | |
| :newconn - | |
| :compliance - | |
| :knocks - | |
| :knock1 - | |
| :knock2 - | |
| :knock3 - |
| #!/bin/bash | |
| _SELF="${0##*/}" | |
| _HERE="$(dirname $(realpath ${0}))" | |
| function aws_instance_profile_arn() { | |
| curl -s http://169.254.169.254/2019-10-01/meta-data/iam/info | jq -r .InstanceProfileArn | |
| } | |
| function aws_instance_profile_name() { |
| #!/bin/bash | |
| _SELF="${0##*/}" | |
| _HERE="$(dirname $(realpath ${0}))" | |
| function parse_url() { | |
| local url _url __url proto uphp user_pass host_port user pass host port path query_string | |
| url="${1}" |
ECS task roles are a great security feature that are hard to set up.
The Amazon ECS documentation on setting up task roles tells you to do some questionable things. Among other things, it tells you to run the ECS agent with host networking (a security risk), use an iptables rule to cut off traffic from bridged containers to the host metadata (brittle), and set up additional iptables rules and sysctl settings to route 169.254.170.2:80 to the ECS agent on 127.0.0.1:51679 (brittle again).
I hereby claim:
To claim this, I am signing this object: