-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support AWS Frankfurt #62
Comments
We need this and could contribute a patch if you could give us a few pointers of where to start. |
Hey @afterthought , Sorry for the delay here. This has been actively on our radar and we've already started up our baking process again and have the new account we'll be using going forward. Optimistically we'll have it some time this week. Pessimistically in 2 weeks. Sorry again for the delay, |
Removing the 2.6-blocker tag. Packer doesn't yet support v4 signatures, which means it's can't build to eu-central-1 (Frankfurt) or cn-north-1. Progress on this fix can be tracked upstream, and once there's a Packer release with support for Frankfurt, it will be quick for us to push an AMI there. Relevant upstream bugs:
|
Looks like hashicorp/packer#1646 is closed. Does that mean there is nothing left preventing support for AWS Frankfurt? |
That bug has a crazy scroll, but if v4 sigs are now supported it's likely that Frankfurt AMI's can be built. I have no immediate plans for firing up another build-process myself, though, so there won't be official images baked anytime soon. However, since the move to packer the baking process is not terribly complex and is extensively documented at: https://github.com/riptano/ComboAMI/tree/2.6/build You're welcome to try a build from your own AWS account to make a private ComboAMI that works in Frankfurt. |
No description provided.
The text was updated successfully, but these errors were encountered: