This article walks through the steps for configuring a custom AWS Cloud9 IDE workspace for after the Sinatra project on the Full Stack Web Development Curriculum. 

Setting up cloud 9

Step 1: Set up an AWS account:

First, we’ll want to visit aws.amazon.com. 

We’ll have to fill in a few form fields, and then confirm Our identity by entering a code in response to an automated call.

After it succeeds, we’ll want to choose the basic plan:

Step 2: Login to your Account. 

Next, we’ll want to sign into the console.

We want to sign into your root account first (this is the only account we have at this point, but we’ll create another user account with fewer privileges in a few minutes).

Step 3: Create an IAM Access Group

Then, we’ll want to create a user access group for cloud9. AWS recommends that we give Cloud9 permissions to members of a group with non-root (admin) privileges on our AWS account. To set this up, let’s search for IAM in the services filter.

Then select the groups tab on the left hand navigation.

Next, we’ll want to create a new group. 

We’ll need to filter the policies by cloud9 and add all 3 of the policies to this user group.

Finally, make sure the name and policies have been added correctly and create the group.

Step 4: Create a new User and add it to Our Group

After that, we’ll create a new user and put it into our group.

We’ll want to give our user Programmatic Access and AWS Management Console Access. Also, let’s make sure to uncheck the Require Password Reset checkbox.

After filling out the first part of this multi-page form, we’ll want to assign this new user to be part of your AWS Cloud9 group.

Let’s review our user and make sure it is part of our group and doesn’t require a password reset. Click Create User to continue.

We should receive a confirmation message. Before we click close to continue to the next step, you may want to download the CSV containing your credentials (key and secret for programmatic access to AWS services like Amazon S3 (for assets) and Amazon RDS (for relational database hosting) which you may want to use later on. You’ll be able to generate new credentials later on if you’d like to skip this for now.

To confirm that our new user is part of our group, let’s go back to groups and we should see “1” as our User count.

Step 5: Log in as your non-root IAM user

After we’ve confirmed the creation of our new user, we’ll want to visit the account page briefly before we log out and sign back in with our new user’s credentials.

Once on this page, we’re going to copy the Account ID at the top in the Account Settings section. We’re going to use this ID in the next step to log in as our newly created AWS user.

Now that we’ve got the account id copied, let’s sign out.

Now that we’ve signed out of the root account,  Let’s come back to Sign in the Console.

When we start the Sign in process, we’ll want to click the link to Sign in to a different account instead of signing in as the root user.

Let’s paste in our account ID and log in with the credentials for the AWS Cloud9 user that we created earlier.

Did this answer your question?