Access to AWS ECS Atlantis container

atlantis.yaml

...

workflows:
  make:
    plan:
      steps:
        - run: '$DIR/run-tmate.sh'
#        - run: "make reset deps"
#        - run: "set -o pipefail; make plan | tfmask | scenery --no-color"
    apply:
      steps:
        - run: "set -o pipefail; make apply | tfmask"
...

run-tmate.sh

#!/bin/bash

tmate -S /tmp/tmate.sock new-session -d
tmate -S /tmp/tmate.sock wait tmate-ready
tmate -S /tmp/tmate.sock display -p '#{tmate_ssh}'
tmate -S /tmp/tmate.sock display -p '#{tmate_web}'

• make a separate branch/PR for tmate (we might include tmate into base geodesic at some point, so we can avoid first three steps)
• add this to Dockerfile RUN apk add tmate@testing
• make a git release with this changes (wait a moment, so ECS will use it, should be new version of task definition)
• Then go back to your working branch, place run-tmate.sh to your module folder, for example conf/vpc/
• then do atlantis plan -p vpc or it can go automatically
• wait for response from atlantis and use ssh or web endpoints to connect to container

NOTE: might fail to run again, because of sock already in use (just remove run: '$DIR/run-tmate.sh' from Atlantis)