-
Notifications
You must be signed in to change notification settings - Fork 32
MDN Cutover plan #43
Comments
After a conversation with our TAM (technical account manager) this is solution that we have
Read this as well: https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-error/ |
Original comment from @limed:
|
We have opened a support request to clarify more on the CDN migration and this is what they responded with
So this means our migration will involve AWS staff in some way or another |
FYI. I posted this question to AWS today:
and their response was really encouraging:
|
We will want to do a dry run migration as well on the stage instance where we roll forward to the new cluster and test out what AWS is saying here, and then roll it back to the old cluster. |
Follow-on work is tracked in #90 |
Define a detailed, step-by-step plan for switching from the MozMEAO-based to the MozIT-based infrastructure.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: