-
Notifications
You must be signed in to change notification settings - Fork 83
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.
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
session-manager-plugin support #48
Comments
I also have a feeling the session manager plugin isn't working properly using this action. I didn't manage to workaround it by installing the AWS SSM plugin on the GH runner as part of another step within the same GH workflow job. |
I think the only option may be to add it to the docker file like this aws/session-manager-plugin#12 (comment) - trying to evaluate it, or switch from packer:light to other docker, like ubuntu based but it seems this is not desired based on hashicorp/docker-hub-images#100 If the trick with docker RUN on alpine will work I will try to add a PR that will allow such steps, if not - only fork locally and adjust for your needs, also one more customisation I can think of is |
This worked for my case - but only in fork of this repo, as I'm changing the base Docker image |
Got the same error Getting the following error when packer trying to connect to an EC2 instance via SSM: |
Expected Behavior
Be useful for AWS packer builds
Current Behavior
Not useful - forked
Dockerfile that works in my case:
Maybe it can be useful to allow to specify dockerfile content and override default one?
Steps to Reproduce
Try to build AMI in AWS with SSM session
Environment
AWS account with SSM session for connections
The text was updated successfully, but these errors were encountered: