aws-cloud9

List all Cloud9 development environment identifiers

$ aws cloud9 list-environments

$ aws cloud9 create-environment-ec2 --name [name] --instance-type [instance_type]

$ aws cloud9 describe-environments --environment-ids [environment_ids]

$ aws cloud9 create-environment-membership --environment-id [environment_id] --user-arn [user_arn] --permissions [permissions]

$ aws cloud9 describe-environment-status --environment-id [environment_id]

$ aws cloud9 delete-environment --environment-id [environment_id]

$ aws cloud9 delete-environment-membership --environment-id [environment_id] --user-arn [user_arn]

aws cloud9 <subcommand> [options] [parameters]

Common Subcommands:
aws cloud9 create-environment-ec2 --name <string> --instance-type <string> [options]
aws cloud9 describe-environments [--environment-ids <string>...] [options]
aws cloud9 delete-environment --environment-id <string> [options]
aws cloud9 list-environments [options]
aws cloud9 update-environment --environment-id <string> [options]

Generic AWS CLI Options (applicable to most commands):
--region <string>
--output <string> (json, text, table)
--query <string>
--profile <string>

--environment-id <string>
    Specifies the unique ID of an existing AWS Cloud9 development environment. This is required for commands like describe-environments, delete-environment, and update-environment.

--name <string>
    The name to assign to a new AWS Cloud9 development environment. This is a required parameter for the create-environment-ec2 subcommand.

--instance-type <string>
    Defines the Amazon EC2 instance type (e.g., t2.micro, m5.large) that will power the new Cloud9 environment. Required for create-environment-ec2.

--description <string>
    A user-friendly description for the Cloud9 development environment. Can be used with create-environment-ec2 and update-environment.

--owner-arn <string>
    The Amazon Resource Name (ARN) of the user who owns the environment. Optional for create-environment-ec2.

--subnet-id <string>
    The ID of the VPC subnet in which to launch the EC2 instance for the environment. Optional for create-environment-ec2.

--tags Key=string,Value=string ...
    A list of key-value pairs to apply as tags to the environment and its associated resources. Used with create-environment-ec2.

The command "aws-cloud9" typically refers to the functionality provided for AWS Cloud9 via the aws Command Line Interface (CLI), specifically as the subcommand aws cloud9. AWS Cloud9 is a cloud-based integrated development environment (IDE) that allows users to write, run, and debug code directly from a web browser. It includes a code editor, debugger, and terminal.

The aws cloud9 CLI commands empower users and administrators to programmatically manage their Cloud9 development environments. This includes creating new environments, listing existing ones, describing their detailed properties, updating configurations, and deleting them. It's a critical tool for automating environment provisioning, integrating Cloud9 into CI/CD pipelines, or performing bulk operations on multiple environments without manual console interaction.

To use this command, the AWS CLI must be installed and configured with appropriate AWS credentials and IAM permissions.

Using the aws cloud9 commands necessitates a correctly installed and configured AWS CLI with appropriate IAM permissions. Without the necessary permissions (e.g., cloud9:CreateEnvironmentEC2, cloud9:DeleteEnvironment), commands will fail with 'Access Denied' errors.

Creating Cloud9 environments provisions underlying AWS resources, primarily EC2 instances, which incur costs. It is crucial to monitor usage and delete environments when they are no longer needed to prevent unexpected charges. The available options and required parameters vary significantly depending on the specific subcommand being used.

It's important to understand that aws cloud9 is not a single executable command, but rather a namespace within the AWS CLI. All operations are performed via specific subcommands (e.g., create-environment-ec2, describe-environments). Each subcommand has its own unique set of required and optional parameters, and users should consult the official AWS CLI documentation for the most accurate and detailed information on each specific operation.

While aws cloud9 commands are excellent for managing environments, directly 'opening' an environment in a browser from the CLI is typically handled differently. The aws cloud9 open-environment command can generate a temporary URL, but in many workflows, users will simply access environments through the AWS Management Console after creation, or integrate with single sign-on solutions for direct access.

AWS Cloud9 originated as Cloud9 IDE, an independent cloud-based development environment company. Amazon Web Services (AWS) acquired Cloud9 IDE in 2016, subsequently integrating it into its suite of developer tools and officially launching it as an AWS service in December 2017. Following this integration, the aws cloud9 subcommands were introduced within the AWS CLI, providing a robust programmatic interface for managing Cloud9 environments. Its evolution continues in tandem with the AWS Cloud9 service, receiving updates and new features through AWS CLI releases.

aws(1), aws ec2(1), aws iam(1)