Part 3 - Configure the Dev Server
1. First you will want to create a new IAM User so that you can access your AWS resources through programatic access, follow these steps:
In the AWS console, under Services select IAM.
2. On the left hand side of the screen, click Users
3. Click Add user
Give the user a username like VSDev, and check the checkbox for Programmatic access under Access type
Now click Next: Permissions
4. Select “Attach existing policies directly” at the top of the screen, then select AdministratorAccess under the list of policies
6. Click Create user
This will send you to a screen that shows you both the Access Key and Secret Access key that you just created that is linked to the new user.
MAKE SURE YOU NOTE BOTH THE ACCESS KEY AND SECRET ACCESS KEY AS YOU WILL NEED THEM IN A LATER STEP
Now you are ready to configure your Development machine.
In this task we will RDP in to our dev server and configure Visual Studio and the AWS Toolkit for Visual Studio.
7. Let’s RDP into your dev server. From the EC2 admin interface click on Running instances and then select the WIN314 Dev Server, click on Connect, then click on Download Remote Desktop File and finally launch the RDP file.
8. When you are prompted for credentials first click on More choices, then click on Use a different account and then enter the following credentials:
9. Once we have established an RDP connection to the dev server let’s configure the AWS CLI with your AWS account information. Open a command prompt as an administrator (right-click the command prompt, select more and the select Run as administrator) and enter the command: aws configure, when prompted enter your Access Key and Secret Access Key that was noted in step #6.
If you get a prompt that Docker needs to start, click the Start button
10. Now let’s open Visual Studio (VS) 2019 Community Edition and open our sample .NET application. Select the MvsMusicStore-Wed-F2017 Solution (located at C:\Source)
Once you change the Region you can expand the ECS item and double-click your ECS cluster to see it’s current status
12. Once the solution has loaded let’s run it locally to make sure the application is working. You may receive some warnings regarding SSL, self-signed certificates, the current debug mode, etc. Simply accept those warnings and then the application should render:
Now that have confirmed we have a running application let’s start the process of containerizing our application.