Closed Bug 1137851 Opened 11 years ago Closed 10 years ago

Sort out the various incoming.telemetry.mozilla.org SSL certs

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: whd, Assigned: whd)

References

Details

We've got various telemetry certs in the old dev IAM (which is serving production traffic): exp20150917_telemetry.mozilla.org, telemetry-2014-06-09, telemetry-2014-10-08, telemetry.mozilla.org-heartbleed. We're currently serving prod incoming telemetry and the tee from telemetry-2014-06-09, but we should figure out which cert is the most recent for incoming and switch to that. There are other *.telemetry.mozilla.org domains that the certs might map to, but it wasn't obvious to me if that information is retrievable from IAM (so might have to inspect the certs manually).
Priority: -- → P3
Assignee: nobody → whd
See Also: → 1193832
I had to look at this due to bug #1193832, and it turns out they all expire at the same time so they likely uploads of the same cert to AWS with different names. As we have a new cert issued anyway, I am closing this.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.