-
Notifications
You must be signed in to change notification settings - Fork 343
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
ec2_instance enable hibernate option for instance_initiated_shutdown_behavior #969
Comments
Files identified in the description:
If these files are inaccurate, please update the |
@RonneGisun Thank you for this feature idea. Would you be willing to work on this functionality and open a pull request? |
@alinabuzachis Sorry, but I couldn't justify spending time on this right now. I'm a team of one, and have a long to do list. |
@RonneGisun Could you please try this PR #972 and let us know if it addresses what you requested? Thanks. |
@alinabuzachis Sorry I'm on holiday now, it might be sometime before I can get to this. |
…eys (#972) ec2_instance : Add hibernation_options and volumes->ebs->encrypted keys Signed-off-by: GomathiselviS [email protected] SUMMARY May Fix #969 In order to support Stop-hibernate behavior for an ec2 instance the following keys are added to the ec2_instance module "hibernation_option": true "volumes": [ { "ebs": { "encrypted": true } } ], ISSUE TYPE Bugfix Pull Request Docs Pull Request Feature Pull Request New Module Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> Reviewed-by: GomathiselviS <None> Reviewed-by: Mike Graves <[email protected]> Reviewed-by: Gonéri Le Bouder <[email protected]> Reviewed-by: Mark Chappell <None>
Summary
I am trying to launch new EC2 instances with the 'stop hibernate' option enabled, as per options available in AWS Console.
https://aws.amazon.com/about-aws/whats-new/2019/10/amazon-ec2-hibernation-now-available-on-windows/
Issue Type
Feature Idea
Component Name
ec2_instance
Additional Information
Code of Conduct
The text was updated successfully, but these errors were encountered: