Skip to content
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

Closed
wjordan opened this issue Feb 9, 2017 · 5 comments
Closed

EMR Security Configuration #11830

wjordan opened this issue Feb 9, 2017 · 5 comments

Comments

@wjordan
Copy link

wjordan commented Feb 9, 2017

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:

A Security Configuration is associated with an EMR cluster through the SecurityConfiguration Request Parameter of the RunJobFlow API.

@heyarnold1
Copy link

I was thinking of implementing this myself. Before I do have either of you made any progress?

@wjordan
Copy link
Author

wjordan commented Apr 11, 2017

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!

@catsby
Copy link
Contributor

catsby commented Apr 28, 2017

A new resource emr_security_configuration was added in #14080. It does not cover ListSecurityConfigurations, that should be a separate data source I think.

I'd like to close this if you're ok with it 😄

@catsby catsby closed this as completed Apr 28, 2017
@agalazis
Copy link

Any update on list security configurations?

@ghost
Copy link

ghost commented Apr 7, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants