What is required to promote a migrated resource to production?
Promotion to production marks the completion of a workload's migration to the cloud. After the asset and all of its dependencies are promoted, production traffic is rerouted. The rerouting of traffic makes the on-premises assets obsolete, allowing them to be decommissioned.
The process of promotion varies according to the workload's architecture. However, there are several consistent prerequisites and a few common tasks. This article describes each and serves as a kind of pre-promotion checklist.
Each of the following processes should be executed, documented, and validated prior to production deployment:
- Assess: The workload has been assessed for cloud compatibility.
- Architect: The structure of the workload has been properly designed to align with the chosen cloud provider.
- Replicate: The assets have been replicated to the cloud environment.
- Stage: The replicated assets have been restored in a staged instance of the cloud environment.
- Business testing: The workload has been fully tested and validated by business users.
- Business change plan: The business has shared a plan for the changes to be made in accordance with the production promotion; this should include a user adoption plan, changes to business processes, users that require training, and timelines for various activities.
- Ready: Generally, a series of technical changes must be made before promotion.
Best practices to execute prior to promotion
The following technical changes will likely need to be completed and documented as part of the promotion process:
- Domain alignment. Some corporate policies require separate domains for staging and production. Ensure that all assets are joined to the proper domain.
- User routing. Validate that users are accessing the workload through proper network routes; verify consistent performance expectations.
- Identity alignment. Validate that the users being rerouted to the application have proper permissions within the domain to host the application.
- Performance. Perform a final validation of workload performance to minimize surprises.
- Validation of business continuity and disaster recovery. Validate that proper backup and recovery processes are functioning as expected.
- Data classification. Validate data classification to ensure that proper protections and policies have been implemented.
- Chief information security officer (CISO) verification. Validate that the information security officer has reviewed the workload, business risks, risk tolerance, and mitigation strategies.
Final step: Promote
Workloads will require varying levels of detailed review and promotion processes. However, network realignment serves as the common final step for all promotion releases. When everything else is ready, update DNS records or IP addresses to route traffic to the migrated workload.
Promotion of a workload signals the completion of a release. However, in parallel with migration, retired assets need to be decommissioned taking them out of service.