Closed Bug 1225894 Opened 9 years ago Closed 8 years ago

configure aws for beet mover

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jlund, Unassigned)

References

Details

this includes a dev and prod public reading bucket, iam user, and a policy that grants new user the powers to write to buckets.

Initially we can create a policy that has a non expiring api key/id. But eventually we will likely have a temporary api key/id that is generated by ship-it, submitted to taskcluster secret service global space, and digested by beet mover
this is pretty much done now. can re-open if we want to improve the description of comment 0
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.