Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Move Route 53 zones for SSO dashboard into IAM account #120

Open
danielhartnell opened this issue Dec 21, 2018 · 5 comments
Open

Move Route 53 zones for SSO dashboard into IAM account #120

danielhartnell opened this issue Dec 21, 2018 · 5 comments
Assignees
@andrewkrug

Comments

@danielhartnell
Copy link
Contributor

danielhartnell commented Dec 21, 2018 •
edited by ghost
Loading

The current production and dev zones need to be moved to the IAM account. I will manage this migration. Once this is complete, we should remove the old zones from the InfoSec accounts and remove the the unused ACM certificates. The domains in question are sso.mozilla.com and sso.allizom.org.

cc @andrewkrug @gene1wood
@danielhartnell danielhartnell added this to the Migrate the SSO dashboard to Kubernetes milestone Dec 21, 2018
@danielhartnell danielhartnell self-assigned this Dec 21, 2018
@danielhartnell
Copy link
Contributor Author

Quick update: sso.allizom.org has been moved to the IAM account. Making sure everything works and then I'll move the prod zone. We can rollback if anyone reports an issue.

@danielhartnell
Copy link
Contributor Author

sso.mozilla.com has been moved to the IAM account as well. I'll keep an eye on things today and we can probably remove the old zones when we're back after the holiday.

@danielhartnell
Copy link
Contributor Author

Records were deleted from the old zones. I'll follow up in an hour or so to delete those hosted zones. Providing a little time just in case an unexpected issue occurs.

@the-smooth-operator the-smooth-operator removed this from the Migrate the SSO dashboard to Kubernetes milestone Jan 29, 2019
@gene1wood
Copy link
Contributor

gene1wood commented Feb 25, 2019 •
edited
Loading

@andrewkrug Can the SSO dashboard cloudformation stacks and constituent resources in infosec-prod and infosec-dev be deleted?

Once that's done I can delete the

  • 8f0dfce8-88c1-4b9c-b3bd-850af8dcc0a5 certificate in infosec-prod us-west-2 for sso.mozilla.com
  • 3b209342-6faa-4e4e-a6d2-eaa6936a598a certificate in infosec-dev us-east-1 for
    person-api.sso.allizom.org

Also, can you confirm that person-api.sso.mozilla.com is setup in the mozilla-iam AWS account so I can delete the expired person-api.sso.mozilla.com cert in infosec-prod us-west-2

Same for person-api.sso.allizom.org which has an expired cert in infosec-dev us-west-2

@gene1wood
Copy link
Contributor

@andrewkrug will take care of this in https://jira.mozilla.com/browse/EIS-849

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andrewkrug andrewkrug

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@danielhartnell @gene1wood @andrewkrug @the-smooth-operator