All users were logged out of Bugzilla on October 13th, 2018

Route traffic to public-artifacts.taskcluster.net via the IGW

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: carterbilly979, Unassigned)

Tracking

Details

(Whiteboard: sdk add-ons)

(Reporter)

Description

3 years ago
+++ This bug was initially created as a clone of Bug #1263742 +++

Spun out from bug 1262652.

Test jobs get their installers/packages/test zips from taskcluster, which redirects to public-artifacts.taskcluster.net. That's Cloudfront serving S3, and currently has an address which is not routed via IGW. So the traffic flows 
   S3 -> Cloudfront -> SCL3 -> VPC -> AWS instance

(Side note: we resolve back in SCL3, so we get a suboptimal result for usw2 and use1 anyway!).

dcurado reported on IRC that the releng firewall in SCL3 is very busy, so lets at least route via IGW to get
   S3 -> Cloudfront near SCL3 -> AWS instance
(Reporter)

Updated

3 years ago
Whiteboard: sdk add-ons
(Reporter)

Updated

3 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME

Updated

3 years ago
Group: core-security-release
Resolution: WORKSFORME → FIXED
Component: Autocomplete → General
Product: SeaMonkey → Invalid Bugs
You need to log in before you can comment on or make changes to this bug.