canonical: https://jentic.com/apis/amazonaws.com/codestar

# AWS CodeStar

Jentic publishes the only available OpenAPI specification for AWS CodeStar, keeping it validated and agent-ready. AWS CodeStar provides project-template-driven scaffolding that ties together CodeCommit, CodeBuild, CodeDeploy, CodePipeline, and CloudFormation under a single project. The API covers projects, team members, user profiles, and resource listings, so an agent can create a CodeStar project from a template, list its underlying AWS resources, and manage team membership.

## For AI agents

Create AWS CodeStar projects from templates, list their underlying AWS resources, and manage team members and user profiles. Backed by 18 endpoints across projects, team members, and user profiles.

## Scope

Does not handle pipeline execution, deployment orchestration, or source-code editing - use for CodeStar project, team member, and user profile management only.

## Capabilities

- Create a CodeStar project from a built-in or custom template covering source, build, and deploy resources
- List AWS resources (CodeCommit repository, CodePipeline pipeline, EC2 or Lambda targets) backing a CodeStar project
- Associate and disassociate team members on a project with a project role
- Update team member project roles and remote-access permissions
- Manage CodeStar user profile attributes including SSH public key and display name
- Tag CodeStar projects for cost allocation and ownership

## Use cases

### Templated Project Provisioning

CodeStar's CreateProject takes a template (or a toolchain S3 reference for custom templates) and provisions a CodeCommit repository, CodeBuild project, CodePipeline pipeline, and target compute (EC2, Lambda, or Beanstalk) under one project ID. ListResources returns the ARNs of every backing resource, so an agent can hand off ARNs to downstream automation. This is useful when bootstrapping new microservices that follow a standard organisational shape.

Example prompt: Create a CodeStar project named billing-svc from template 'aws-lambda-nodejs' and list the resources it provisioned

### Team Membership Lifecycle

Engineering managers use AssociateTeamMember, DisassociateTeamMember, and UpdateTeamMember to grant or revoke project access with roles such as Owner, Contributor, and Viewer. ListTeamMembers gives a per-project membership snapshot. Remote-access permissions for EC2-backed projects are also toggled here, so agents can offboard a leaving engineer with a single sequence of calls.

Example prompt: Disassociate user-arn arn:aws:iam::..:user/jane from project billing-svc and confirm the resulting team member list

### Project Inventory and Ownership

Platform teams use ListProjects, DescribeProject, and ListTagsForProject to maintain a catalogue of CodeStar projects across an account, including their underlying resource set. This is helpful when consolidating ownership during reorganisations or when migrating projects off CodeStar templates onto custom IaC.

Example prompt: List all CodeStar projects and tag any without an Owner tag with Owner=unassigned

### AI Agent Integration via Jentic

Through Jentic, an AI agent uses CodeStar by searching for an intent like 'create a CodeStar project', loading the CreateProject schema, and executing it with a project name and template. Jentic signs the SigV4 request server-side using IAM credentials in your Jentic One instance.

Example prompt: Search Jentic for 'create a CodeStar project', load the CreateProject schema, and execute it for a Node.js Lambda template

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /#X-Amz-Target=CodeStar_20170419.CreateProject | Create a CodeStar project from a template |
| POST | /#X-Amz-Target=CodeStar_20170419.DescribeProject | Describe a CodeStar project |
| POST | /#X-Amz-Target=CodeStar_20170419.ListProjects | List projects in the account |
| POST | /#X-Amz-Target=CodeStar_20170419.ListResources | List backing AWS resources for a project |
| POST | /#X-Amz-Target=CodeStar_20170419.AssociateTeamMember | Add a team member to a project |
| POST | /#X-Amz-Target=CodeStar_20170419.DisassociateTeamMember | Remove a team member from a project |
| POST | /#X-Amz-Target=CodeStar_20170419.CreateUserProfile | Create a CodeStar user profile |

## Key resources

- **Project** — Create, describe, list, update, and delete CodeStar projects
- **Team Member** — Associate, disassociate, list, and update team members and roles
- **User Profile** — Create, describe, list, update, and delete CodeStar user profiles
- **Resource** — List the underlying AWS resources backing a project
- **Tag** — Tag and list tags for projects

## Why Jentic

- **Setup:** Wiring AWS CodeStar by hand means signing every request with AWS Signature v4 HMAC, choosing the correct regional host like codestar.{region}.amazonaws.com, and dispatching each operation through the X-Amz-Target header rather than a REST path. Through Jentic you install once, import AWS CodeStar from the API Directory, store the AWS access key and secret once, and your agent calls it.
- **Permission scoping:** CodeStar routes operations through the X-Amz-Target header and carries the project id and team member in the request body, not the URL path, so scoping is by operation. You limit the agent to the operations it needs, such as DescribeProject or ListProjects, so DisassociateTeamMember or DeleteProject are not included unless you add them.
- **Credential handling:** Your AWS access key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a CodeStar project' or 'list CodeStar team members', and Jentic returns the matching CodeStar operation with its input schema, so the agent calls CreateProject or ListTeamMembers directly without browsing AWS docs.

## Related APIs

- **AWS CodeCommit** — CodeCommit hosts the source repository created when a CodeStar project is provisioned
- **AWS CodePipeline** — CodePipeline runs the build/test/deploy pipeline scaffolded by CodeStar
- **AWS CodeStar Connections** — CodeStar Connections links AWS services to GitHub, GitHub Enterprise, and Bitbucket source providers

## FAQ

### Why is there no official OpenAPI spec for AWS CodeStar?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS CodeStar via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the AWS CodeStar API use?

CodeStar uses AWS Signature Version 4 (HMAC) signed requests with an IAM access key and secret. Through Jentic, IAM credentials live encrypted in your Jentic One instance and the SigV4 signature is computed server-side, so the agent context never holds the raw secret.

### Can I list the AWS resources backing a CodeStar project?

Yes. Call ListResources with the project id, and the response returns an array of resource ARNs covering the CodeCommit repository, CodeBuild project, CodePipeline pipeline, and target compute resources tied to that project.

### How do I add a team member to a CodeStar project?

Call AssociateTeamMember with the project id, the IAM user ARN, a projectRole (Owner, Contributor, or Viewer), and remoteAccessAllowed. UpdateTeamMember adjusts the role later, and DisassociateTeamMember removes the member.

### What are the rate limits for the AWS CodeStar API?

AWS enforces per-account, per-region throttling on CodeStar; throttled requests return ThrottlingException. CodeStar's own service is being phased down by AWS - verify availability in your target region. The AWS SDKs that Jentic wraps implement exponential backoff automatically.

### How do I create a CodeStar project through Jentic with an AI agent?

Run pip install jentic, then have the agent search for 'create a CodeStar project', load the CreateProject schema, and execute it with id, name, and a sourceCode/toolchain pair (or template). Use ListResources afterwards to capture the provisioned ARNs.

### Can I limit what my agent is allowed to do with the AWS CodeStar API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which CodeStar operations and credentials your agent may use. CodeStar routes every operation through the X-Amz-Target header and carries the project id and team member in the request body rather than the URL path, so scoping is done per operation. You can restrict the agent to read-only calls such as DescribeProject, ListProjects, and ListResources, leaving mutating operations like AssociateTeamMember, DisassociateTeamMember, and DeleteProject out unless you explicitly add them.