I have been using AWS Cloud9 for several months and throughout my entire two years in college for research purposes, mainly for cloud-based development, testing AWS services, and collaborative coding tasks. My main use case for AWS Cloud9 is application development, cloud app development, and managing AWS resources in a single environment. For example, I used it to write and test Python scripts connected directly to EC2 instances and deploy small applications to AWS without needing to configure a local development setup. One thing I appreciate about AWS Cloud9 is how convenient it is for collaborative development. I have used it for small team projects where multiple developers needed quick access to the same cloud environment without spending time on local setup. It was especially helpful for testing serverless applications and automating AWS tasks using the built-in terminal and AWS CLI integration.
My main use case for AWS Cloud9 is cloud-based development and testing, specifically for quickly setting up environments and working with AWS services. I primarily use AWS Cloud9 as an online IDE to run, develop, and debug applications directly in the browser without needing a local setup. I use AWS Cloud9 to quickly develop and test a backend script, then deploy it to AWS services like Lambda. For example, I use AWS Cloud9 to write a Python script that processes file uploads to Amazon S3. I code and test everything directly in AWS Cloud9 using its built-in terminal. Once it is working, I deploy the logic to AWS Lambda for automated executions. This workflow helps me avoid local setup, speed up testing, and ensures everything integrates smoothly within the AWS ecosystem. Apart from this, I use AWS Cloud9 for quick debugging, environment consistency, and seamless AWS integration. Beyond development, I use this for debugging issues in a live-like environment, which helps avoid problems like working on my machine and ensures consistency since the environment is pre-configured and runs on AWS infrastructure. I also leverage it for learning and experimenting with services like Amazon EC2 and AWS Lambda as everything is essentially accessible from one place.
Cloud Security Engineer at a manufacturing company with 5,001-10,000 employees
Real User
Top 20
Sep 10, 2025
I have used AWS Cloud9 and ElastiCache. It serves as a cloud VM for DevOps team members to give them access to AWS resources, and then they use that to access different resources in AWS since AWS Cloud9 instances are in the same VPC. AWS Cloud9 can be used as a jump box and for managing AWS Lambda functions. AWS Cloud9 is useful for collaboration capabilities in geographically distributed teams.
An Integrated Development Environment (IDE) is a software application that provides comprehensive facilities to computer programmers for software development. IDEs increase productivity by offering tools such as a source code editor, build automation, and a debugger.
IDEs streamline the development lifecycle by providing a suite of functionalities that only need one installation package. By integrating numerous development tools into one platform, developers reduce the overhead of...
I have been using AWS Cloud9 for several months and throughout my entire two years in college for research purposes, mainly for cloud-based development, testing AWS services, and collaborative coding tasks. My main use case for AWS Cloud9 is application development, cloud app development, and managing AWS resources in a single environment. For example, I used it to write and test Python scripts connected directly to EC2 instances and deploy small applications to AWS without needing to configure a local development setup. One thing I appreciate about AWS Cloud9 is how convenient it is for collaborative development. I have used it for small team projects where multiple developers needed quick access to the same cloud environment without spending time on local setup. It was especially helpful for testing serverless applications and automating AWS tasks using the built-in terminal and AWS CLI integration.
My main use case for AWS Cloud9 is cloud-based development and testing, specifically for quickly setting up environments and working with AWS services. I primarily use AWS Cloud9 as an online IDE to run, develop, and debug applications directly in the browser without needing a local setup. I use AWS Cloud9 to quickly develop and test a backend script, then deploy it to AWS services like Lambda. For example, I use AWS Cloud9 to write a Python script that processes file uploads to Amazon S3. I code and test everything directly in AWS Cloud9 using its built-in terminal. Once it is working, I deploy the logic to AWS Lambda for automated executions. This workflow helps me avoid local setup, speed up testing, and ensures everything integrates smoothly within the AWS ecosystem. Apart from this, I use AWS Cloud9 for quick debugging, environment consistency, and seamless AWS integration. Beyond development, I use this for debugging issues in a live-like environment, which helps avoid problems like working on my machine and ensures consistency since the environment is pre-configured and runs on AWS infrastructure. I also leverage it for learning and experimenting with services like Amazon EC2 and AWS Lambda as everything is essentially accessible from one place.
I would use AWS Cloud9 if I had a business that needed a lot of users with different types of access, since it is all in one place to manage easily.
I have used AWS Cloud9 and ElastiCache. It serves as a cloud VM for DevOps team members to give them access to AWS resources, and then they use that to access different resources in AWS since AWS Cloud9 instances are in the same VPC. AWS Cloud9 can be used as a jump box and for managing AWS Lambda functions. AWS Cloud9 is useful for collaboration capabilities in geographically distributed teams.