AWS Cloud9
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject ManagementapiKey13 EndpointsREST
For Agents
Provision Cloud9 cloud IDE environments on EC2, manage their members and permissions, and tag or delete them when no longer needed.
Use for: I need to create a Cloud9 environment for a new engineer, Add a teammate as a read-write member of a Cloud9 environment, List all Cloud9 environments in this account, Get the status of a specific Cloud9 environment
Not supported: Does not run code, build pipelines, or store source repositories. Use for managing Cloud9 IDE environments and their members only.
AWS Cloud9 is a cloud-based IDE that runs in the browser and is backed by an Amazon EC2 instance or an SSH-accessible server. The API lets you create, list, describe, update, and delete Cloud9 development environments, manage environment members and their permission levels (READ_ONLY, READ_WRITE, OWNER), tag resources, and read environment status. It is most often used to provision short-lived, pre-configured development environments for new joiners, contractors, or workshop attendees without each person installing a full local toolchain.
Install Jentic One Beta
Connect the AWS Cloud9 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Cloud9, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS Cloud9 API.
Create EC2-backed Cloud9 environments with a chosen instance type, subnet, and idle auto-stop window
Add or remove environment members with READ_ONLY, READ_WRITE, or OWNER permissions
List and describe Cloud9 environments owned by the account
Get current status of an environment (creating, ready, error, deleting)
Update environment settings such as name, description, and managed credentials
Tag environments for cost allocation and team-level reporting
Delete an environment and terminate its underlying EC2 instance
Use Cases
Patterns agents use AWS Cloud9 API for, with concrete tasks.
★ Workshop Environment Provisioning
Spin up identical Cloud9 environments for every workshop attendee minutes before the session starts. Use CreateEnvironmentEC2 for each attendee with a small instance type and a 30-minute idle auto-stop, then CreateEnvironmentMembership to invite them as READ_WRITE members. After the session, DeleteEnvironment cleans up everything in one call so there is no leftover EC2 cost.
Loop attendee emails: CreateEnvironmentEC2 with name=workshop-2026-06-{i}, instanceType=t3.small, automaticStopTimeMinutes=30, then CreateEnvironmentMembership with userArn=<attendee> and permissions=READ_WRITE.
New Joiner Onboarding
Give a new engineer a pre-configured browser-based IDE on day one without waiting for laptop setup. Create a Cloud9 environment from a template AMI that already has the team's repos cloned, language toolchains installed, and AWS credentials configured. Add the engineer as OWNER so they can manage their own environment.
CreateEnvironmentEC2 with name=onboarding-jane-doe, ownerArn=arn:aws:iam::...:user/jane.doe, instanceType=t3.medium, subnetId=subnet-xxx, then verify status reaches READY via DescribeEnvironmentStatus.
Contractor Off-Boarding
When a contractor's engagement ends, revoke their Cloud9 access in seconds. List the environments they belong to, call DeleteEnvironmentMembership to remove them from each, or DeleteEnvironment for environments dedicated to their work. Pair with IAM access removal for full off-boarding.
List environments via DescribeEnvironmentMemberships filtered by userArn=<contractor>, then for each call DeleteEnvironmentMembership.
Agent-Driven IDE Provisioning
Let an internal IT agent take a JIRA ticket like 'provision a Cloud9 environment for the new contractor on Project Atlas' and execute it end-to-end. The agent calls Cloud9 through Jentic to create the environment, add the member, and tag it for billing. AWS credentials never leave the vault and the same playbook runs across multiple AWS accounts in an organisation.
Search Jentic for 'create a Cloud9 EC2 environment', execute it with parameters from the ticket, then 'add a member to a Cloud9 environment' with permissions=READ_WRITE, and tag the environment with Project=Atlas and CostCenter=IT.
Key Endpoints
13 endpoints — aws cloud9 is a cloud-based ide that runs in the browser and is backed by an amazon ec2 instance or an ssh-accessible server.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.CreateEnvironmentEC2
Create an EC2-backed Cloud9 environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DescribeEnvironments
Describe one or more environments
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.ListEnvironments
List environment IDs
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.UpdateEnvironment
Update environment name or description
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DeleteEnvironment
Delete an environment and its EC2 instance
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.CreateEnvironmentMembership
Invite a user to an environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DescribeEnvironmentMemberships
List members of an environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DeleteEnvironmentMembership
Remove a member from an environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.CreateEnvironmentEC2
Create an EC2-backed Cloud9 environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DescribeEnvironments
Describe one or more environments
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.ListEnvironments
List environment IDs
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.UpdateEnvironment
Update environment name or description
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DeleteEnvironment
Delete an environment and its EC2 instance
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.CreateEnvironmentMembership
Invite a user to an environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DescribeEnvironmentMemberships
List members of an environment
POST
/#X-Amz-Target=AWSCloud9WorkspaceManagementService.DeleteEnvironmentMembership
Remove a member from an environment
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access key ID and secret access key for AWS Cloud9 are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing credentials and the raw IAM secrets never enter the agent context. Jentic computes the AWS Signature Version 4 signature server-side for every request.
Intent-based discovery
Agents search Jentic by intent (for example, 'create a Cloud9 environment') and Jentic returns matching AWS Cloud9 operations with their input schemas, the correct AWS service endpoint, and the required IAM action, so the agent can invoke the right call without crawling the AWS docs.
Time to first call
Direct AWS Cloud9 integration: 1-3 days for AWS SDK setup, IAM role configuration, Sigv4 signing, and error handling. Through Jentic: under 1 hour, search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Cloud9 API through Jentic.
What authentication does the AWS Cloud9 API use?
All requests are signed with AWS Signature Version 4 using an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in the vault and Jentic performs the signing server-side; the agent only sees a scoped Jentic credential reference.
Can I provision a Cloud9 environment on a specific instance type?
Yes. Pass instanceType to CreateEnvironmentEC2, along with subnetId and an optional automaticStopTimeMinutes for idle auto-stop. Cloud9 launches the chosen EC2 instance, configures the IDE, and reports status via DescribeEnvironmentStatus.
What are the rate limits for the AWS Cloud9 API?
Cloud9 applies standard AWS service throttling and returns ThrottlingException when exceeded. Workshop-style provisioning of dozens of environments at once should pace CreateEnvironmentEC2 calls and use exponential backoff.
How do I add a user to a Cloud9 environment through Jentic?
Search Jentic for 'add a member to a Cloud9 environment', load the CreateEnvironmentMembership schema, and execute it with environmentId, userArn, and permissions set to READ_WRITE or READ_ONLY. The operation maps to CreateEnvironmentMembership and returns the resulting member record.
Is AWS Cloud9 still being supported?
AWS announced that no new customer access to Cloud9 is granted as of mid-2024 for new accounts, but existing customers can continue to use the service and the API remains operational. New deployments should evaluate alternatives such as AWS CodeCatalyst Dev Environments or self-hosted code-server.
Is AWS Cloud9 free to use?
Cloud9 itself has no separate charge. You pay for the underlying EC2 instance, EBS volume, and any data transfer the environment uses. The automaticStopTimeMinutes setting is the simplest way to limit cost when environments are idle.
GET STARTED