Set up subdomain routing to AWS EC2 instance for MDN samples dev server

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: sheppy, Assigned: bhourigan)

Tracking

Details

(Reporter)

Description

4 years ago
In bug 1128040 (https://bugzilla.mozilla.org/show_bug.cgi?id=1128040), we set DNS for the new MDN samples server, which is being used to host code that manages samples that need to run on the server rather than a browser client (or for samples that for various reasons can't be run in-place on the MDN site itself).

This bug is to set up another subdomain name (mdn-samples-dev.mozilla.org or similar) which routes to a secondary EC2 instance used while code is in development.

While the previously set up server is technically a "dev" server, that's only because it's being maintained by the MDN docs team rather than by ops. We still have need of a dev server for in-progress work and testing.

We used an EIP for the main server; should we do the same for the dev server or is there a better way?
(Assignee)

Comment 1

4 years ago
Hi Eric

If you would like us to provision a EC2 instance for development work we can do so, but I would suggest filing another bug for the Webops folks and they will get you squared away.

I would suggest adding all non-production DNS entries to allizom.org as opposed to mozilla.org. Any DNS entries we add to m.o must first be approved by opsec, and that typically requires your infrastructure to be audited and pass a security review.

If you only plan to have one instance and can tolerate AZ failures pointing to an EIP is fine. If you want it to be a little more robust you could configure an auto scaling group behind an ELB and then we can point DNS there.
(Reporter)

Comment 2

4 years ago
I have the EC2 instance up and running. And you're right; it should be mdn-samples.allizom.org. I knew I was doing something wrong.

Just need the one instance to have a subdomain name routed to it, just like I did in bug 1128040, but to a different server.

I will add the canonical name to this bug shortly.
(Reporter)

Comment 3

4 years ago
The canonical name for the dev server: ec2-52-5-80-241.compute-1.amazonaws.com

Please establish mdn-samples.allizom.org for this. Thank you!
(Assignee)

Comment 4

4 years ago
(In reply to Eric Shepherd [:sheppy] from comment #3)
> The canonical name for the dev server:
> ec2-52-5-80-241.compute-1.amazonaws.com
> 
> Please establish mdn-samples.allizom.org for this. Thank you!

I've added a CNAME for mdn-samples.allizom.org to point to ec2-52-5-80-241.compute-1.amazonaws.com, it will take about 30 minutes for our name servers to begin announcing the resource record.

Please reopen or feel free to ping me on irc if you need anything else. :)
Assignee: infra → bhourigan
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.