AboutFree templates
How-to library

AWS how-tos

2 step-by-step AWS jobs with official downloads, exact clicks and checks.

2 how-tosUpdated
Moving servers to AWS? Start with the VMware to AWS guideApplication Migration Service, replication, test launches and cutover.Read the guide →
Install AWS CLI version 2 and configure credentials

At the end you will have the aws command installed, a working profile signed in through IAM Identity Center (or access keys), and proof of which account and role you are using. If you cannot install software, use AWS CloudShell.

9 stepsAWSInstall the AWS Replication Agent on a source server

At the end your Windows or Linux source server will have the AWS Replication Agent installed, appear on the Source servers page of AWS Transform MGN and be running its initial sync to your chosen AWS Region.

9 stepsAWS

Playbooks that use these how-tos

How to migrate between clouds or bring workloads back on premises

A practical approach to moving servers, databases and storage from AWS to Azure, from Azure to AWS, or back to your own data centre or colocation.

15 min readHow to migrate SQL Server and MySQL to Amazon RDS and Aurora

Pick the right method for each database (native backup and restore, physical backup to Aurora, or AWS DMS with change data capture), then test and cut over.

17 min readVMware alternatives after the Broadcom licensing changes

What Broadcom changed, which platforms replace vSphere, how to compare them on features, backup support, clustering, skills and migration tooling, and what the move involves.

16 min readHow to migrate VMware and physical servers to AWS

Rehost servers to Amazon EC2 with AWS Transform MGN (formerly AWS Application Migration Service): install the replication agent, test, cut over and finalise.

16 min read

Common AWS errors and fixes

All errors →
command not found: aws

Your shell cannot find the aws program, so the AWS CLI is not installed properly or is not on your PATH.

AWSAn error occurred (AccessDenied) when calling the ListBuckets operation: Access denied.

The AWS CLI ran, but the identity it used is not allowed to call the S3 API the command needs.

AWSAn error occurred (InvalidAccessKeyId) when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.

The access key the AWS CLI sent is not a valid key, so AWS rejected the request.

AWSAn error occurred (SignatureDoesNotMatch) when calling the ListBuckets operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.

AWS could not verify the request signature, usually because the computer clock is wrong or the secret key is mishandled.

AWS[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

The AWS CLI does not trust the TLS certificate it receives, often because a corporate proxy is inspecting traffic.

AWSAgent not seen

AWS Application Migration Service (MGN) is not hearing from the replication agent on the source server.

AWSNOT_CONVERGING (Not converging)

MGN replication backlog keeps growing because data is written to the source faster than it can be sent.

AWSSNAPSHOTS_FAILURE (Snapshot failure)

MGN cannot take a consistent EBS snapshot of the replicated disks.

AWS