eu-central-1 AWS region V4 signing required and not supported
Bug #1447841 reported by
David Lawson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Katherine Cox-Buday | ||
1.24 |
Fix Released
|
High
|
Katherine Cox-Buday |
Bug Description
The new eu-central-1 AWS region requires V4 signing (see https:/
2015-04-23 22:21:13 INFO juju.cmd supercommand.go:37 running juju [1.23.0-
2015-04-23 22:21:13 INFO juju.provider.ec2 provider.go:49 opening environment "prod4-
2015-04-23 22:21:14 DEBUG juju.provider.ec2 provider.go:129 ec2 request failed: AWS was not able to validate the provided access credentials (AuthFailure)
Changed in juju-core: | |
milestone: | none → 1.24.0 |
no longer affects: | juju-core/1.23 |
tags: | added: ec2-provider |
Changed in juju-core: | |
milestone: | 1.24.0 → 1.25.0 |
Changed in juju-core: | |
assignee: | nobody → Katherine Cox-Buday (cox-katherine-e) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We can probably just switch to V4 everywhere rather than special-casing cn-north-1 now that code has actually been tested and proved to work.