You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS SSO service is single-region at this point of time. In some instances, customers wish to move their AWS SSO configuration from one region to another region and this document explains how some of these migration activities could be automated.
4
+
5
+
## Caveats
6
+
7
+
- AWS SSO at this point of time does not have API's to manage identities , instance enablement. These are manual operations.
8
+
- When a customer migrates AWS SSO from one region to another region, the solution only helps automate migration of permission sets and account assignments.
9
+
- The solution assumes that identities (users/groups) are onboarded into the new region using the same naming convention. For ex, if a customer had onboarded a user with user name `alpha-user`, group with display name `beta-group` in region 1 through any of the supported identity sources, the solution assumes that the customer will onboard the user with the same user name `alpha-user` and same group display name `beta-group` in region 2. Only when this condition is met, the solution automatically migrates account assignments from region 1 to region 2.
10
+
11
+
## Seqence
12
+
13
+
-`Discover` component of the solution is deployed in your current AWS SSO account and current AWS SSO region first. This would read all the permission sets, account assignments in your current AWS SSO region and persist them for later usage
14
+
- The customer then manually moves the AWS SSO configuration from their current region to the new region
15
+
- The customer onboards all the required identities in the new region
16
+
-`Deploy` component of the solution is deployed in your current AWS SSO Account and new AWS SSO region. This would then deploy all the permission sets and account assignments similar to how they were provisioned in the old AWS SSO region.
17
+
-`Destroy` components of the solution are then run to remove the artefacts created in the `Discover` and `Deploy` phase.
18
+
19
+
## Execute
20
+
21
+
- Ensure the following [pre-requisites](https://catalog.us-east-1.prod.workshops.aws/workshops/640b0bab-1f5e-494a-973e-4ed7919d397b/en-US/00-prerequisites) are ready and available
- Run `Discover` phase through the following steps by using your Orgmain account and current AWS SSO region credentials:
80
+
- Validate that the configuration and other dependencies are all set up by running `yarn synth-region-switch-discover` from the root of the project.
81
+
- This should not return any errors and should synthesise successfully
82
+
- Run `deploy-region-switch-discover` from the root of the project. Wait until the discover phase Cloudformation stacks are successfully deployed.
83
+
- Set up AWS SSO in the new region, set up identity store and onboard all the identities in the new AWS SSO region, refer to service documentation [here](https://docs.aws.amazon.com/singlesignon/latest/userguide/getting-started.html).
84
+
- Identiies must be on-boarded into the new AWS SSO region before running the next step.
85
+
- Run `Deploy` phase through the following steps by using your Orgmain account and new AWS SSO region credentials:
86
+
- Validate that the configuration and other dependencies are all set up by running `yarn synth-region-switch-deploy` from the root of the project.
87
+
- This should not return any errors and should synthesise successfully
88
+
- Run `deploy-region-switch` from the root of the project. Wait until the deploy phase Cloudformation stacks are successfully deployed.
89
+
- Verify that all your account assignments and permission sets are successfully created in the new AWS SSO region
90
+
- Post verification that everything is deployed correctly in the new AWS SSO region, delete the artefacts created for `Deploy` and `Discover` phases by running the following:
91
+
- Using Orgmain and new AWS SSO region credentials, run `yarn destroy-region-switch-deploy` from the root of the project. This will remove all the deploy phase artefacts.
92
+
- Using Orgmain and old AWS SSO region credentials, run `yarn destroy-region-switch-discover` from the root of the project. This will remove all the discover phase artefacts
0 commit comments