feat: aws ssm support#74
Open
acoronels wants to merge 4 commits into
Open
Conversation
acoronels
force-pushed
the
acs/aws-ssm-support
branch
from
3525728 to
a1c339f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add AWS SSM support for Ansible runs
This change adds the pieces needed to run atlas-ansible-utils playbooks against EC2 instances through AWS Systems Manager instead of SSH. The Docker image now installs the Session Manager plugin and the required Ansible collections, while
requirements.ymlandmake requirementsmake the same dependencies available for local runs.The README now documents the SSM workflow, including controller prerequisites, the S3 staging bucket required by the
aws_ssmconnection plugin, example playbook commands, and a smoke-test path. A small example inventory andscripts/ssm-smoke-test.shwere added to make connectivity validation repeatable before running complex playbooks that might use SSM.The storage backup role now supports EC2 instance profile credentials for S3 uploads. When explicit AWS access keys are omitted, the upload task leaves the AWS environment empty so the AWS CLI can use the target host's default credential provider chain.