We have three ELBs which should have stable CNAMEs we can point to (http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/using-domain-names-with-elb.html): symbolapi.a.o -> elb_to_symbolapi__http crash-reports.a.o -> elb_for_collectors crash-stats.a.o -> elb_for_webapp There's also elb_for_buildbox but I don't know if it's necessary to have a DNS entry for that since it's not really for public consumption, unlike the above. Note that we're using the entries above - I think it's fine to just point them at AWS, we might want to provide alternate DNS entries for the PHX stage environment until we're out of that environment.
Summary: point allizom DNS entries at stage → point allizom DNS entries at AWS stage
(In reply to Robert Helmer [:rhelmer] from comment #0) > We have three ELBs which should have stable CNAMEs we can point to > (http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/using- > domain-names-with-elb.html): Was a little unclear here - Amazon provides A records (they don't guarantee that ELB IP addresses will be stable, but the A records should be) - the CNAME should be in our allizom.org DNS
What we're going to do here is depend on intermediary DNS entries that we control, and ask Mozilla IT to point to those. The intermediary domains will be the ones that point to the AWS ELB CNAMEs.
Depends on: 1151911
We now have: crash-stats: https://crash-stats.mocotoolsstaging.net/ collector : https://crash-reports.mocotoolsstaging.net/submit This is enough to start testing stage at least, we're not quite ready to point allizom.org at the above yet but that's the plan.
crash-stats.allizom.org is up now and has been working for some time.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.