AWS CodeDeploy
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdhmac47 EndpointsREST
For Agents
Trigger AWS CodeDeploy deployments to EC2, on-premises servers, ECS, and Lambda, monitor their progress, and stop or roll back failed releases. Backed by 47 endpoints across applications, deployment groups, and deployments.
Use for: I need to trigger a CodeDeploy deployment from an S3 revision, Stop a deployment that is failing, Get the status of an in-progress deployment, List the last 10 deployments for an application
Not supported: Does not handle source compilation, container image building, or pipeline orchestration — use for deploying revisions to EC2, on-premises, ECS, or Lambda compute targets only.
Jentic publishes the only available OpenAPI specification for AWS CodeDeploy, keeping it validated and agent-ready. AWS CodeDeploy automates code deployments to EC2, on-premises servers, ECS services, and Lambda functions with blue/green and in-place strategies. The API covers applications, deployment groups, deployments, deployment configs, and on-premises instances, so an agent can trigger releases, monitor deployment progress, and roll back failed deployments programmatically.
Install Jentic One Beta
Connect the AWS CodeDeploy to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS CodeDeploy, 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 CodeDeploy API.
Create CodeDeploy applications and deployment groups for EC2, on-premises, ECS, or Lambda compute
Trigger deployments with revision pointers to S3, GitHub, or ECS task definitions
Monitor deployment status, instance-level state, and lifecycle event details
Stop or roll back deployments mid-flight using StopDeployment and ContinueDeployment
Define custom deployment configurations with traffic-shifting rules for blue/green
Register and deregister on-premises instances and tag them for deployment-group targeting
List deployment history and filter deployments by application, group, or status
Use Cases
Patterns agents use AWS CodeDeploy API for, with concrete tasks.
★ Blue/Green Deployments to ECS or Lambda
Teams running ECS services or Lambda functions use CodeDeploy for blue/green releases that shift traffic gradually and roll back automatically on alarm. CreateDeployment with a revision that points to an appspec.yaml drives the cutover, while GetDeployment and BatchGetDeployments track the lifecycle. ListDeploymentInstances exposes per-target state so an agent can pinpoint which task or alias is unhealthy.
Trigger a deployment for application web-svc and deployment group ecs-prod from the S3 revision s3://artifacts/web/build-42.zip
EC2 and On-Premises Fleet Releases
For EC2 Auto Scaling groups or on-premises servers running the CodeDeploy agent, CreateDeployment installs the new revision in-place or with rolling updates. RegisterOnPremisesInstance and AddTagsToOnPremisesInstances let an agent onboard a new server and target it via deployment group tag filters. BatchGetDeploymentInstances exposes per-instance lifecycle event status for triage.
Register an on-premises instance with name datacenter-edge-1, tag it with Env=prod, and trigger a deployment to deployment group on-prem-prod
Automated Rollback on Failure
An ops agent watching deployment progress can call StopDeployment with autoRollbackEnabled to halt a failing rollout and revert to the prior successful revision. The API returns DeploymentStatus values like Failed and Stopped that an agent can poll on, and the rollback itself is created as a new deployment that ListDeployments will surface for downstream notifications.
Stop deployment d-ABC123 with autoRollbackEnabled=true and confirm the new rollback deployment reaches Succeeded
AI Agent Integration via Jentic
Through Jentic, an AI agent uses CodeDeploy by searching for an intent like 'trigger a CodeDeploy deployment', loading the CreateDeployment schema, and executing it with application name, deployment group, and revision. Jentic signs the SigV4 request server-side using IAM credentials in the MAXsystem vault.
Search Jentic for 'trigger a CodeDeploy deployment', load the CreateDeployment schema, and execute it for application web-svc, deployment group prod, and an S3 revision
Key Endpoints
47 endpoints — jentic publishes the only available openapi specification for aws codedeploy, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateApplication
Create a CodeDeploy application
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeploymentGroup
Create a deployment group inside an application
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeployment
Trigger a deployment from a revision
POST
/#X-Amz-Target=CodeDeploy_20141006.GetDeployment
Get full status of a deployment
POST
/#X-Amz-Target=CodeDeploy_20141006.StopDeployment
Stop or roll back a running deployment
POST
/#X-Amz-Target=CodeDeploy_20141006.ContinueDeployment
Resume a deployment that is waiting for traffic shift
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeploymentConfig
Define a custom deployment configuration
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateApplication
Create a CodeDeploy application
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeploymentGroup
Create a deployment group inside an application
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeployment
Trigger a deployment from a revision
POST
/#X-Amz-Target=CodeDeploy_20141006.GetDeployment
Get full status of a deployment
POST
/#X-Amz-Target=CodeDeploy_20141006.StopDeployment
Stop or roll back a running deployment
POST
/#X-Amz-Target=CodeDeploy_20141006.ContinueDeployment
Resume a deployment that is waiting for traffic shift
POST
/#X-Amz-Target=CodeDeploy_20141006.CreateDeploymentConfig
Define a custom deployment configuration
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access key ID and secret are stored encrypted in the Jentic MAXsystem vault. Jentic computes the SigV4 signature server-side for every CodeDeploy call, so raw IAM credentials never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g. 'trigger a CodeDeploy deployment' or 'roll back a failed deployment') and Jentic returns the matching CodeDeploy operation with its input schema, so the agent calls CreateDeployment or StopDeployment directly without browsing AWS docs.
Time to first call
Direct AWS SDK integration: 1-3 days for SigV4, IAM permissions, deployment polling, and rollback logic. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS CodeDeploy API through Jentic.
Why is there no official OpenAPI spec for AWS CodeDeploy?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS CodeDeploy via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AWS CodeDeploy API use?
CodeDeploy uses AWS Signature Version 4 (HMAC) signed requests with an IAM access key and secret. Through Jentic, IAM credentials live encrypted in the MAXsystem vault and the SigV4 signature is computed server-side, so the agent context never holds the raw secret.
Can I trigger a deployment from an S3 or GitHub revision through the API?
Yes. Call CreateDeployment with applicationName, deploymentGroupName, and a revision object referencing either an S3Location (bucket, key, bundleType) or a GitHubLocation (repository, commitId). The deployment ID is returned synchronously; poll GetDeployment to track Status and DeploymentOverview.
How do I roll back a failed deployment programmatically?
Call StopDeployment with the deploymentId and autoRollbackEnabled=true. CodeDeploy stops the in-flight deployment and creates a new rollback deployment that reverts to the last successful revision; ListDeployments returns it with createdBy=rollback.
What are the rate limits for the AWS CodeDeploy API?
AWS enforces per-account, per-region throttling on CodeDeploy control-plane calls; CreateDeployment is limited to a small number of TPS per account. Throttled responses return ThrottlingException — the AWS SDKs that Jentic wraps implement exponential backoff automatically.
How do I trigger a CodeDeploy release through Jentic with an AI agent?
Run pip install jentic, then have the agent search for 'trigger a CodeDeploy deployment', load the CreateDeployment schema, and execute it with applicationName, deploymentGroupName, and a revision pointer. Poll GetDeployment for status, and call StopDeployment with autoRollbackEnabled=true if the deployment fails.
GET STARTED