Overview of managing access permissions to your AWS CodeBuild resources

Every AWS resource is owned by an AWS account, and permissions to create or access a resource are governed by permissions policies. An account administrator can attach permissions policies to IAM identities (that is, users, groups, and roles).

When you grant permissions, you decide who is getting the permissions, the resources they can access, and the actions that can be performed on those resources.

AWS CodeBuild resources and operations

In AWS CodeBuild, the primary resource is a build project. In a policy, you use an Amazon Resource Name (ARN) to identify the resource the policy applies to. Builds are also resources and have ARNs associated with them. For more information, see Amazon Resource Names (ARN) and AWS Service Namespaces in the Amazon Web Services General Reference.

For example, you can indicate a specific build project (myBuildProject) in your statement using its ARN as follows:

"Resource": "arn:aws:codebuild:us-east-2:123456789012:project/myBuildProject"

To specify all resources, or if an API action does not support ARNs, use the wildcard character (*) in the Resource element as follows:

"Resource": "*"

Some CodeBuild API actions accept multiple resources (for example, BatchGetProjects). To specify multiple resources in a single statement, separate their ARNs with commas, as follows:

"Resource": [
  "arn:aws:codebuild:us-east-2:123456789012:project/myBuildProject",
  "arn:aws:codebuild:us-east-2:123456789012:project/myOtherBuildProject"
]

CodeBuild provides a set of operations to work with the CodeBuild resources. For a list, see AWS CodeBuild permissions reference.

Understanding resource ownership

The AWS account owns the resources that are created in the account, regardless of who created the resources. Specifically, the resource owner is the AWS account of the principal entity (that is, the root account, an user, or an IAM role) that authenticates the resource creation request. The following examples illustrate how this works:

Managing access to resources

A permissions policy describes who has access to which resources.

Policies attached to an IAM identity are referred to as identity-based policies (IAM policies). Policies attached to a resource are referred to as resource-based policies. CodeBuild supports identity-based policies, and resource-based policies for certain read only APIs for the purpose of cross-account resource sharing.

Secure access to S3 buckets

We strongly recommend that you include the following permissions in your IAM role to verify the S3 bucket associated with your CodeBuild project is owned by you or someone you trust. These permissions are not included in AWS managed policies and roles. You must add them yourself.

If the owner of an S3 bucket used by your project changes, you must verify you still own the bucket and update permissions in your IAM role if not. For more information, see Allow users to interact with CodeBuild and Allow CodeBuild to interact with other AWS services.

Specifying policy elements: Actions, effects, and principals

For each AWS CodeBuild resource, the service defines a set of API operations. To grant permissions for these API operations, CodeBuild defines a set of actions that you can specify in a policy. Some API operations can require permissions for more than one action in order to perform the API operation. For more information, see AWS CodeBuild resources and operations and AWS CodeBuild permissions reference.

The following are the basic policy elements:

To learn more about IAM policy syntax and descriptions, see AWS IAM Policy Reference in the IAM User Guide.

For a table showing all of the CodeBuild API actions and the resources they apply to, see the AWS CodeBuild permissions reference.