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

feat: AMI Deregistration Protection #486

Open
schniber opened this issue Jun 7, 2024 · 1 comment
Open

feat: AMI Deregistration Protection #486

schniber opened this issue Jun 7, 2024 · 1 comment

Comments

@schniber
Copy link

schniber commented Jun 7, 2024

Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

AWS released in May 2024 the capability to protect AMIs against mistaken Deregistrations.

It would be nice to take this feature into account in order to streamline the setup of this additional layer of protection at AMI build time through Packer.

Use Case(s)

Some use cases could be:

  • Prevention against mistaken AMI deregistration,
  • legal locks for compliance, ...

Potential configuration

source "amazon-ebs" "basic-example" {
  source_ami_filter {
    filters = {
       virtualization-type = "hvm"
       name = "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*"
       root-device-type = "ebs"
    }
    owners = ["099720109477"]
    most_recent = true
    deregistration_protection {
      enabled = true
      cooldown_period = "24h"
    }
  }
}

Potential References

AWS References:

@lbajolet-hashicorp
Copy link
Contributor

Hi @schniber,

Thanks for bringing this one up! This looks like a good candidate for a first contribution, would you be interested in contributing this? We can provide help if you're interested, let us know!

Otherwise we can see to include this in the future, can't promise when as other priorities clash with this, but we'll keep an eye open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants