-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
EMR Security Configuration #11830
Comments
I was thinking of implementing this myself. Before I do have either of you made any progress? |
I have not made any progress- I created this issue mostly to follow-up on a feature request I encountered when answering a question on StackOverflow, I did not have a need for it myself. Good luck with the implementation! |
A new resource I'd like to close this if you're ok with it 😄 |
Any update on list security configurations? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
EMR Security Configuration is a new feature released on Sep 21 2016 that allows a JSON document to be created and associated with an EMR cluster to configure encryption keys, at-rest and in-transit encryption properties for the cluster. Security Configurations are implemented through the following new resource-oriented EMR service APIs:
CreateSecurityConfiguration
DescribeSecurityConfiguration
ListSecurityConfigurations
DeleteSecurityConfiguration
A Security Configuration is associated with an EMR cluster through the
SecurityConfiguration
Request Parameter of theRunJobFlow
API.The text was updated successfully, but these errors were encountered: