
Note: You only need to do this the first time you perform this process. This also follows best practices by not having you administer using your root account. What we’ll do below is create a new user for us to use to test these tasks, and take note of the access key id and secret access code, so we can use them later. When you are running AWS CLI commands, you will typically use an access key id and secret access code instead of your usual username and password. Ok, so you already have an AWS root account. Step 2: Setup an AWS user for this process Here is a guide to get that downloaded and installed. Adding browsers, productivity software, or whatever you might need on it.

Most of that time is waiting on an OS to install plus uploads and conversions. Time it: For a 15GB machine, this entire guide can take up to 4hrs to complete, depending on connection speed.

So how do you get yourself a Windows 10 instance running up there? Fear not! Thats what this guide is for. Its true, Windows 10 is not one of the pre-built AMIs offered by AWS. Whatever the case, you went to AWS figuring you’d launch a new Windows 10 instance, and then you realized: Windows 10 isn’t one of the choices. Maybe its for a jump box, maybe its for direct access to some RDS instances or other services. You want a Microsoft Windows 10 instance in your EC2 environment.
