Closed Bug 1149589 Opened 10 years ago Closed 9 years ago

whitelist s3 domains for nightly/release updates

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: mshal, Unassigned)

References

Details

For nightly and release builds to be fully off of ftp, we'll need to have balrog support S3.
To be clear: Balrog doesn't need any special support for S3, we just need to configure our instances of it to whitelist the s3 domains we'll be serving updates off of. I'm not sure what s3 domains normally look like, but we should make sure that these domains are only used by us. Eg, we don't want a bad person to be able to able to serve files off of a domain that we have whitelisted, otherwise we've negated the security of the whitelist.
Summary: Update balrog to support S3 → whitelist s3 domains for nightly/release updates
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.