Closed Bug 1598758 Opened 5 years ago Closed 5 years ago

Allow configuration of AWS credentials similar to GCP credentials

Categories

(Taskcluster :: Services, enhancement)

Product:
Taskcluster
Component:
Services
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

Currently, the auth service uses its "own" credentials for the awsS3Credentials endpoint. That is confusing for deployers (since it seems like the creds would need scopes for the service itself) and also means that we can only produce S3 credentials for one account.

The GCP credentials are nicer: depending on the requested project, they use different credentials.

Let's do the same thing:

bucketName1:
  accessKeyId: "..."
  secretAccessKey: ".."
bucketName2:
  accessKeyId: "..."
  secretAccessKey: ".."
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.