Skip to main content
Welcome back. In this lesson you’ll provision an AWS Cloud9 IDE and prepare a development workspace for the sample application used throughout this course. Follow the steps below to create the environment, inspect the repository, and run the initial app files.
  1. Open the AWS Management Console and search for Cloud9. Select the Cloud9 service. If you use Cloud9 frequently, bookmark it — bookmarked services appear in the left panel.
The image shows the AWS Cloud9 web page, which describes it as a cloud IDE for writing, running, and debugging code, highlighting features, benefits, and how it works. There are sections for getting started and additional resources on the page.
  1. Create a new Cloud9 environment:
    • Click “Create environment”.
    • Provide a name (this lesson uses CodingGround) and an optional description.
    • Leave other settings at their defaults unless you have specific instance size or networking requirements.
The image shows an AWS Cloud9 environment creation page, where users can name the environment, provide a description, and choose between a new or existing EC2 instance. Different instance types with varying RAM and vCPU specifications are also displayed.
Cloud9 will provision the required backend resources (it creates and configures an EC2 instance for your IDE). Provisioning typically takes 5–10 minutes. When the environment is ready, click “Open” to launch the Cloud9 editor in a new tab and wait for the IDE to initialize and connect.
Cloud9 uses an EC2 instance billed to your account. If you want to avoid ongoing charges, stop or terminate the instance when not in use.
Once connected, the Cloud9 interface provides a complete development workspace: the file tree is on the left, the editor in the center, and an integrated terminal at the bottom.
The image shows an AWS Cloud9 development environment interface with a welcome screen and a terminal at the bottom. The interface includes navigation options and a "Getting started" section on the right.
For example, opening the repository README.md displays the file in the editor while leaving the terminal available for commands.
The image shows an AWS Cloud9 development environment with a README.md file open, displaying a welcome message and instructions. A terminal window is visible at the bottom, ready for user input.
Next: clone the course repository from AWS CodeCommit into your Cloud9 environment.
  1. In the AWS Console, open CodeCommit and copy the repository’s HTTPS clone URL.
The image shows a screenshot of the AWS CodeCommit console displaying a list of repositories, including "aws-microservice-project," "login-page," and "aws-microservice," with options for HTTP and SSH clone URLs.
Important: Your Cloud9 EC2 instance must be able to authenticate to CodeCommit. If you see authentication errors while cloning, ensure either:
  • The Cloud9 EC2 instance has an IAM role attached with the necessary CodeCommit permissions, or
  • You have configured the AWS CLI credential helper / Git credentials for CodeCommit on the instance.
Now switch to the Cloud9 terminal and run the clone command. Example output:
After cloning, a new folder aws-microservice-project appears in the Cloud9 file tree. Expand it to inspect project files. Typical top-level files and folders include: Below is an excerpt from app.py to show the basic Flask structure and where the database client will be integrated later:
If you prefer to work locally instead of in Cloud9, cloning CodeCommit on your machine requires proper authentication (CodeCommit credential helper or SSH keys). For more details, see AWS CodeCommit documentation: Next steps
  • Create a Dockerfile in the repository root to containerize the Flask app.
  • Build and run the container locally inside Cloud9 to validate the app before deploying to AWS services.
That’s it for this lesson. In the next lesson we will add a Dockerfile and prepare the application for container-based deployment. See you there.

Watch Video