Issue link: https://resources.awscloud.com/i/1496544
Determine opportunities for architectural changes You might find that choices you made on-premises are no longer right for the new environment in the cloud. For instance, you might be able to consolidate shards. Set up the cloud database accounts Set up general accounts for users in the cloud through IAM before you set up the users, roles, and groups in the database. Upgrade and test applications You might need to rewrite code to work with the new database. Some of the migration of applications may be automatable, just as with the database itself. Readiness Assessment A readiness assessment helps you to estimate the costs, the architec‐ ture of the cloud database, migration plans, and the impact of the move to the cloud on compliance regulations. The result of a cloud readiness assessment is a detailed report of your company's readi‐ ness to move its databases to the cloud. Following are brief descriptions of the key steps during a cloud readiness assessment. Stakeholder interviews Talking to application developers, business users, and others concerned with the use of data within your organization team will help you to determine requirements pertaining to perfor‐ mance, high availability, and the features and capabilities of the cloud-based databases. Analysis of current on-premises databases Go back over your current databases to determine growth pat‐ terns of data, backup and recovery strategies, ongoing data exports and imports, and so on. Understanding the current database usage patterns will help you when it's time to decide what databases to use in the cloud, and whether you'll need a particular database offering in order to get the capabilities you need. Prioritization of the databases to move Pick the databases that you'd like to move to the cloud first. One important criterion is the extent of changes to pass:[