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

Add support for fast snapshot restore #463

Open
ziggythehamster opened this issue Mar 5, 2024 · 2 comments
Open

Add support for fast snapshot restore #463

ziggythehamster opened this issue Mar 5, 2024 · 2 comments
Labels
enhancement stage/accepted Confirmed, and intend to work on. No timeline commitment though. sync to jira

Comments

@ziggythehamster
Copy link

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

When images are taken and snapshots copied, Packer users should be able to enable EBS fast snapshot restore on those snapshots for some list of availability zones. Note that the list of AZs would be per snapshot, which could span regions, so the configuration syntax might get a little hairy.

Use Case(s)

Make instance launches not suffer from the degraded performance that comes with launching from an AMI or EBS snapshot while the volume is initializing.

Potential configuration

source "amazon-ebssurrogate" "foo" {
  ami_regions = ["us-east-1", "us-west-2"]

  ami_fast_snapshot_restore {
    region             = "us-east-1"
    availability_zones = ["us-east-1a", "us-east-1b"]
  }

  ami_fast_snapshot_restore {
    region             = "us-west-2"
    availability_zones = ["us-west-2a", "us-west-2b"]
  }
}

Potential References

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-fast-snapshot-restore.html

Copy link

github-actions bot commented Apr 2, 2024

This issue has been synced to JIRA for planning.
JIRA ID: [HPR-1705](https://hashicorp.atlassian.net/browse/HPR-1705)

@lbajolet-hashicorp lbajolet-hashicorp added the stage/accepted Confirmed, and intend to work on. No timeline commitment though. label Apr 2, 2024
@lbajolet-hashicorp
Copy link
Contributor

Hi @ziggythehamster,

Thanks for the suggestion, we've added that issue to our internal tracker, this is definitely something we'll work on eventually.
As always though if you're open to the idea, feel free to open a PR with this implementation, we'll gladly review and help if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement stage/accepted Confirmed, and intend to work on. No timeline commitment though. sync to jira
Projects
None yet
Development

No branches or pull requests

2 participants