AWS instructions need an update
Bug #1201833 reported by
Jorge Castro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juju Website |
Fix Released
|
Undecided
|
Unassigned | ||
| juju-core |
Fix Released
|
Critical
|
Brandon Clark | ||
| Docs |
Fix Released
|
Critical
|
Nick Veitch | ||
Bug Description
The new AWS console looks different and they're moving away from allowing you access to your secret key right from the Web UI so we'll need to redo these directions to follow AWS best practices:
| Changed in juju-core: | |
| assignee: | nobody → Nick Veitch (evilnick) |
| importance: | Undecided → Critical |
| status: | New → In Progress |
| Changed in juju-core: | |
| assignee: | Nick Veitch (evilnick) → Brandon Clark (web-brandon) |
Revision history for this message
| Brandon Clark (web-brandon) wrote | #1 |
Revision history for this message
| Jorge Castro (jorge) wrote | #2 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-website: | |
| status: | New → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-website: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Made changes to reflect the new security credentials but I cannot submit them: https:/