Evaluate exit strategy requirements
You might need a cloud provider exit strategy to comply with regulatory requirements, cloud concentration concerns, or your own corporate policies pertaining to the use of critical third-party service providers. An exit strategy outlines an organization's approach to move one or more workloads from a CSP to another environment.
Some key components of an exit strategy could include:
-
Scope of the exit strategy (for example, the number of workloads)
-
Objectives and success criteria for an exit
-
Key risk indicators (KRIs) and thresholds that might necessitate an exit
-
Target environment for workloads (for example, on premises or alternative service providers)
-
Technical considerations (for example, whether migration to another environment requires refactoring)
-
Operational considerations (for example, staffing and skills required to operate workloads in another environment)
-
Legal considerations (for example, contractual commitments and termination rights)
-
Key assumptions that underlie the exit strategy (for example, the resources available and the time it will take to complete the exit)
-
Plans for testing the exit strategy and challenging key assumptions (for example, tabletop exercises and gamedays)
-
Organizational responsibilities for development, maintenance, and governance of the exit strategy
-
Data residency considerations
Note
To assist customers with a smooth transition, AWS offers free data egress for
planned exits. For more information, see the AWS blog post Free data
transfer out to internet when moving out of AWS
