New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re-request MDN stage/prod certs #416
Comments
requested:
|
@escattone dev/stage/prod certs ARNs listed above |
@metadave Thanks so much as well for setting-up DNS for |
@escattone I'll request a new cert for stage with |
cert approved |
@metadave Sorry, but I just realized that we have developer-local.allizom.org as an allowed domain for staging, but I'm not sure if/how it's used. Did you already have that within the cert for staging? Here's what I see for allowed hosts for staging and prod. Do they match with what you have in your certs? STAGE:
PROD:
|
At first, I thought it might be the stage CDN name. Looking at the page source, there doesn't appear to be a CDN domain for staging in SCL3. Static files are served from developer.allizom.org. https://developer-local.allizom.org was the name of the service when running in the Vagrant environment. Vagrant would update I don't think we need to provision a cert for developer-local.allizom.org for AWS. |
our staging cert has |
Thanks @metadave, and thanks for the history on |
new certs requested with the following names:
|
cc @jgmize |
@escattone we'll need to update the prod and stage ELB configs to use the new cert ARN's once they're approved. |
config updated with new certs: #499 |
previous certs deleted from ACM |
do we includemdn.mozillademos.org
on the cert as wellyes
@jgmize can these certs be requested through ACM?yes
The text was updated successfully, but these errors were encountered: