Overview of managing access permissions to your AWS BugBust 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 (users, groups, and roles).

Note

An account administrator (or administrator user) is a user with administrator privileges. For more information, see IAM Best Practices in the IAM User Guide.

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 BugBust resources and operations

AWS BugBust contains one resource, an AWS BugBust event. In a policy, you use an Amazon Resource Name (ARN) to identify the resource to which the policy applies. In the following ARN, the repository association ID and the code review ID are universally unique identifiers (UUIDs). For more information, see Amazon Resource Names (ARNs) in the Amazon Web Services General Reference.

Resource type	ARN format
AWS BugBust event	arn:aws:bugbust:region-ID:account-ID:event:event-uuid

For example, you can indicate an AWS BugBust event with a my-event-id id in your statement using its ARN, as follows.

"Resource": "arn:aws:bugbust:us-east-2:123456789012:event:my-event-id"

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

"Resource": "*"

To specify multiple resources in a single statement, separate their ARNs with commas, as follows.

"Resource": [
     "arn:aws:bugbust:us-east-2:123456789012:event:my-event-id-1",
     "arn:aws:bugbust:us-east-2:123456789012:event:my-event-id-2"
   ]

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

Understanding resource ownership

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

• If you use the root account credentials of your AWS account to create a rule, your AWS account is the owner of the AWS BugBust resource.

• If you grant permissions to create AWS BugBust resources to a user, the user can create AWS BugBust resources. However, your AWS account, to which the user belongs, owns the AWS BugBust resources.

• If you create an IAM role in your AWS account with permissions to create AWS BugBust resources, anyone who can assume the role can create AWS BugBust resources. Your AWS account, to which the role belongs, owns the AWS BugBust resources.

Managing access to resources

A permissions policy describes who has access to which resources.

Note

This section discusses the use of IAM in AWS BugBust. It doesn't provide detailed information about the IAM service. For complete IAM documentation, see What Is IAM? in the IAM User Guide. For information about IAM policy syntax and descriptions, see IAM JSON Policy Reference in the IAM User Guide.

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. AWS BugBust supports identity-based (IAM policies) only.

Identity-based policies

You can attach policies to IAM identities. To grant a user permissions to view repository associations and code reviews in the AWS BugBust console, you can attach a permissions policy to a user or group to which the user belongs.

In AWS BugBust, identity-based policies are used to manage permissions to the resources related to associated repositories and code reviews. For example, you can control access to code reviews.

You can create IAM policies to restrict the calls and resources to which users in your account have access, and then attach those policies to IAM users. For more information about how to create IAM roles and to explore example IAM policy statements for AWS BugBust, see Identity-based policies for AWS BugBust.

Specifying policy elements: actions, effects, and principals

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

The following are the basic policy elements:

• Resource – You use an ARN to identify the resource to which the policy applies.

• Action – You use action keywords to identify resource operations to allow or deny. For example, the bugbust-slug:CreateEvent permission gives the user permissions to perform the CreateEvent operation.

• Effect – You specify the effect, either allow or deny, when the user requests the action. If you don't explicitly grant access to (allow) a resource, access is implicitly denied. You can also explicitly deny access to a resource. You might do this to make sure that a user cannot access a resource, even if a different policy grants access.

• Principal – In identity-based policies (IAM policies), the user to whom the policy is attached is the implicit principal. For resource-based policies, you specify the user, account, service, or other entity that you want to receive permissions.

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 AWS BugBust API actions and the resources to which they apply, see AWS BugBust permissions reference.