-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
SSM support should be added #46
Comments
@dudymas couldn't that be done by attaching an ssm iam policy to the iam role created by this module? |
I use this module and can confirm that SSM can be configured on the cluster nodes, you need to:
|
In the PR above, I've added a boolean flag to the module that controls the attachment of the SSM IAM policy to the EC2 instance profile role. I successfully tested this with the default EMR AMI, which appears to have the SSM agent already bundled. Per the AWS documentation, the following Linux-based AMIs come w/ SSM agent preinstalled...
For anyone using a custom AMI outside of this list, the module supports a custom |
Describe the Feature
SSM allows folks to connect to an instance without the need for ssh.
This is described here: https://aws.amazon.com/blogs/big-data/securing-access-to-emr-clusters-using-aws-systems-manager/
Expected Behavior
Users and roles with permission to start and attach to ssm sessions should be able to remotely manage emr clusters.
Use Case
Most emr clusters need some initial boot operations to set things up
Describe Ideal Solution
Not only is ssm a possible flag, but also adding more boot actions is supported via s3 objects or even plain text.
The text was updated successfully, but these errors were encountered: