Cloud Migration: Steps & Issues in Amazon WorkMail Migration Process

This report details the process of migrating mailboxes to Amazon WorkMail, beginning with preparing both the source (e.g., Office 365) and destination (Amazon WorkMail) environments. Key steps include creating administrator accounts, exporting user lists, adding the organization and domain to Amazon WorkMail, and configuring user access. The MSP (Managed Service Provider) steps involve creating source and destination endpoints, purchasing licenses, and carefully managing administrator credentials. The report also addresses potential issues such as security vulnerabilities related to account permissions and password strength, the risk of user omissions during data export, and the importance of accurate domain configuration to prevent misdirected emails. The document highlights the need for robust security measures and careful execution to ensure a smooth and secure migration process.

6.
(a) The following steps are followed in migrating the mail boxes to the Amazon WorkMail.
First you prepare the source environment by:
 Creating an account for the administrator in the Office to be used in migration.
 Exporting the list of users to a file of CSV.
You then prepare the destination environment by:
 Adding the Organization to the WorkMail of Amazon.
 Adding the domain to the WorkMail of Amazon.
 Creating new users or enabling the directory of users that is already existing for the
WorkMail of Amazon.
 Creating an account for the admin to be used for migration containing full permissions of
access for all the mailboxes. Adding a new user who is the admin of migration in the
console of the WorkMail of Amazon or creating the user who is the admin of migration
in the Active Directory and enabling the user for the WorkMail of Amazon. (Varia, J.,
2011)
Importantly, when setting the endpoint of the Destination, the login name of the administrator
ought to be keyed in in the format of email address.
After that, the MSP steps are completed which include:
 Creating the customer, Destination and the Source end points.
For the endpoint of the Source:
 Select Endpoints, Add the Endpoint, enter the name of the endpoint then chose
the category of the endpoint you are sourcing out from.
 Then select the radio button indicating the option of Provide Credentials and then
key in the identifications regarding the account of the admin.
For the endpoint of the Destination:
 Select Endpoints, Add the endpoint, input the name of the endpoint and then
when keying in the type of the endpoint, chose the AWS WorkMail.

 After that then select the radio button indicating Provide Credentials and then
input the identifications regarding the account of the admin for the already set up
account under the section of preparing the Destination Environment in this report.
 Finally chose the region of WorkMail provided in the list of the drop-down.
 After that then, purchase the licenses. (King, T. M., & Ganti, A. S., 2010)
(b) Issues in the above steps.
There are various issues that come about from the execution of the above steps which
include security issues, that is, during setting up of the accounts, the admin account should have
all the permissions while the users should be limited. Therefore, it is vital to be careful when
setting up the accounts so that the unauthorized users may not access information that is not
meant for them. (Varia, J., 2010)
Another issue is setting up of strong passwords when creating the accounts to avoid any
breaches that may arise after the email is migrated to the AWS cloud service.
Also, while exporting the list of the users, it is advisable not to do it manually so that
there will be no omissions of some users as they may miss on important issues regarding the
business operation.
While adding the name of the Organization as well as the domain to the AWS WorkMail,
the credentials should be carefully selected to avoid any mishaps. The domains of organizations
are closely related meaning that any minor mistake may lead to gross error of relaying important
mails to the wrong individuals. (Nadon, J., 2017)

References
King, T. M., & Ganti, A. S. (2010). Migrating autonomic self-testing to the cloud. In
Software Testing, Verification, and Validation Workshops (ICSTW), 2010 Third
International Conference on (pp. 438-443). IEEE.
Nadon, J. (2017). AWS Enterprise Applications. In Website Hosting and Migration with Amazon
Web Services (pp. 235-249). Apress, Berkeley, CA.
Varia, J. (2010). Migrating your existing applications to the aws cloud. A Phase-driven
Approach
to Cloud Migration.
Varia, J. (2011). Best practices in architecting cloud applications in the AWS cloud. Cloud
Computing: Principles and Paradigms, 457-490.