AWS BugBust

(1)

AWS BugBust

User Guide

(2)

AWS BugBust: User Guide

Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon.

(3)

What is AWS BugBust?

AWS BugBust is a code challenge that helps you improve your code quality and optimize your

applications. It is used by administrators who create a fun and challenging bug bash and by players who are invited to compete to see who can ﬁx the most bugs and make the greatest eﬃciency improvement in your applications.

AWS BugBust works with the following machine learning AWS services that ﬁnd issues in your applications and generate recommendations to help solve them.

• Amazon CodeGuru Reviewer – An AWS BugBust event can include issues found by CodeGuru Reviewer during a repository analysis of your Java or Python code. A repository analysis reviews code in a repository that you specify, then identiﬁes problems and provides recommendations to help solve them. For more information, see Get recommendations using repository analysis and Create code reviews with security analysis in the Amazon CodeGuru Reviewer User Guide.

• Amazon CodeGuru Profiler – An AWS BugBust event can include issues found by CodeGuru Profiler during analysis of runtime performance data from your live applications in a profiling group. A profiling group is a set of applications that are profiled together as a unit. For each performance issue found, CodeGuru Profiler generates a recommendation to help address it. CodeGuru Profiler finds issues such as latency concerns and problems with heap and CPU utilization. For more information, see Working with profiling groups in the CodeGuru Profiler User Guide.

As an administrator, you create an AWS BugBust bug bash event with a new or existing repository analysis, a specified profiling group, or both. You invite players from your organization who compete to see who can fix the most bugs and make the most performance improvements. To get started as an administrator, create an event. For more information, see Create an AWS BugBust event (admin) (p. 3).

As a player, you fix bugs identified by CodeGuru Reviewer, performance issues identified by CodeGuru Profiler, or both. You accumulate points with each fixed issue and compete with other players to see who can earn the most points. To get started as a player, join an event. For more information, see Joining an AWS BugBust event (p. 24).

Note

In the AWS BugBust player portal, a player is referred to as a BugBuster.

(6)

What is the AWS BugBust player portal?

The AWS BugBust player portal is a meeting place for AWS BugBust players and administrators. Both players and administrators need AWS BugBust player portal accounts to use AWS BugBust. To learn how to create a AWS BugBust player portal account, see Accessing the AWS BugBust player portal for AWS BugBust events (p. 22).

AWS BugBust players and administrators can use the AWS BugBust player portal to do the following.

• View your standing on the global AWS BugBust leaderboard.

• View your standing in individual AWS BugBust events.

• View your AWS BugBust achievements.

• Customize your player avatar.

• Customize your player nickname.

• Add authorized email addresses.

For more information, see How to customize your AWS BugBust player proﬁle (p. 27).

Your authorized email addresses are the keys to scoring points in AWS BugBust events.

If you create pull requests on GitHub with an email address diﬀerent than the one you used to create your AWS BugBust player portal account you must authorize that email address by adding it to your AWS BugBust player portal account to score points. For more information, see Adding authorized email addresses in the AWS BugBust player portal (p. 28).

For more information about creating your ﬁrst AWS BugBust event, see Create an AWS BugBust event (admin) (p. 3).

(7)

Create an AWS BugBust event (admin)

An AWS BugBust administrator can create a bug bash event. When you create an event, you specify issues for your players to fix. Players fix bugs, improve the performance of an application, or both. For each fixed bug or performance improvement, a player earns points.

To let players fix bugs, you specify a repository analysis for your event in Amazon CodeGuru Reviewer in your AWS account and Region. All issues CodeGuru Reviewer finds during the analysis are available for your players to claim and fix.

To let players improve the performance of an application, you specify a profiling group for your event in Amazon CodeGuru Profiler in your AWS account and Region. All performance issues CodeGuru Profiler finds during the analysis are available for your players to claim and fix.

For both bugs and performance enhancements, a player creates a pull request with the code changes that address the issue. After the updated code is merged, CodeGuru Reviewer and CodeGuru Profiler analyze the updated code base. If AWS BugBust doesn't detect the issue that the player attempted to fix, then it considers the issue fixed and awards points to the player. After a player checks in code to improve the performance of a profiling group, the AWS BugBust event administrator evaluates the performance effect of the checked-in code and awards points based on the complexity of fixed bugs and the level of performance improvement on a profiling group. For more information, see Rules and scoring in AWS BugBust (p. 25).

After you create your event, you can do the following.

• Invite players to your event. For more information, see Invite AWS BugBust event players (admin) (p. 7).

• Import work items (bugs, proﬁling groups, or both) into your event for your players to work on. For more information, see Import work items into an event (admin) (p. 11).

• Edit your event before it starts. You can edit your event's name, description, start and end dates, prizes, work items, and players. After the event starts, the only change you can make is to invite more players.

For more information, see Update an AWS BugBust event (admin) (p. 8).

Important

To create an AWS BugBust event, your AWS user must be granted permissions in the AWSBugBustFullAccess AWS managed policy.

Topics

• Step 1: Provision an IAM user to create an AWS BugBust event (p. 4)

• Step 2: Review rules and scoring (p. 4)

• Step 3: Create or log in to a player account (p. 5)

• Step 4: Enter AWS BugBust event details (p. 5)

• Step 5: Review your AWS BugBust event (p. 6)

(8)

Provision an IAM user

Step 1: Provision an IAM user to create an AWS BugBust event

An AWS BugBust administrator must have permissions to create an AWS BugBust event. To create an event, you must have permissions in the AWSBugBustFullAccess managed policy attached to your IAM user, group, or role. For more information, see AWSBugBustFullAccess managed policy for AWS BugBust event administrators (p. 42).

Follow these instructions to prepare an IAM user for an AWS BugBust event administrator to create and update an event.

Provision an IAM user to use AWS BugBust and create events

1. Create an IAM user, or use one that is associated with your AWS account.

• If you're unfamiliar with creating an IAM user, see Creating an IAM User and Overview of AWS IAM Policies in the IAM User Guide.

2. Grant the IAM user access to AWS BugBust.

• Option 1: Use the AWSBugBustFullAccess AWS managed policy. For more information, see AWSBugBustFullAccess managed policy for AWS BugBust event administrators (p. 42).

Important

The AWSBugBustFullAccess policy grants access to all AWS BugBust resources. We recommend that you always use the minimum permissions required to accomplish your task. For more information, see IAM Best Practices in the IAM User Guide.

• Option 2: Create a custom IAM policy. With a custom IAM policy, you can provide the minimum required permissions. For more information, see Identity-based policies for AWS BugBust (p. 41).

Continue creating your AWS BugBust event in Step 2: Review rules and scoring (p. 4).

Step 2: Review rules and scoring

To start creating an event, open the AWS BugBust console page and then review details about event rules and scoring.

Open the create event console page

1. Open the AWS BugBust console at https://console.aws.amazon.com/codeguru/bugbust/#/home.

2. If an AWS BugBust information page is displayed, choose Create AWS BugBust event. Otherwise, in the navigation pane, expand AWS BugBust, choose Getting started, and then choose Create AWS BugBust event.

3. To understand how scoring works in your event, review its rules. For more information, see Rules and scoring in AWS BugBust (p. 25). When you are done, choose Next.

Continue creating your AWS BugBust event in Step 2: Review rules and scoring (p. 4).

(9)

Create or log in to a player account

Step 3: Create or log in to a player account

To create an event, you must have an AWS BugBust player account so you can receive an AWS BugBust badge for creating the event. An AWS BugBust player account is not an AWS account. To create an AWS BugBust event, you must have a player account and an AWS account.

Note

Create or log in to an AWS BugBust player account

1. Do one of the following:

• If you have an AWS BugBust account, choose Sign in, then enter your email address and password.

• If you are new to AWS BugBust, choose Create an AWS BugBust player account, enter your email address and a password, then choose Sign in.

2. Choose Next.

Continue creating your AWS BugBust event in Step 4: Enter AWS BugBust event details (p. 5).

Step 4: Enter AWS BugBust event details

You must enter details for your event, including its name, description, start and end dates, and its prizes.

You can change any of these details after you create the event, but not after the event's start date and time. The only changes you can make to an event after it starts is to add more players and update its tags. For more information, see Invite AWS BugBust event players (admin) (p. 7).

Add details for your AWS BugBust event

1. In Information about your AWS BugBust event, enter the following information.

a. In Event name, enter a name for your event.

b. In Event description, enter a name for your event.

c. In Start time, enter the date and time your event starts. Players can start claiming bugs after the start time.

d. In End time, enter the date and time your event ends. Players can submit bug ﬁxes and performance improvements for claimed bugs and proﬁling groups until the end time.

2. In Prizes, for each Prize description text box, enter a description of your ﬁrst, second, and third place prizes.

3. (Optional) Expand Tags to add one or more tags to your event. For more information, see Tagging an event in AWS BugBust (admin) (p. 9).

a. Expand Tags.

b. Choose Add new tag.

c. In Key, enter a name for the tag. You can add an optional value for the tag in Value.

d. (Optional) To add another tag, choose Add new tag again.

4. Choose Next.

Continue creating your AWS BugBust event in Step 5: Review your AWS BugBust event (p. 6).

(10)

Review your AWS BugBust event

Step 5: Review your AWS BugBust event

Review the details of your AWS BugBust event. Choose Edit in any section to make changes. After you've reviewed your event, choose Create event.

Next, you must do the following.

• Invite players to participate in your event. For more information, see Invite AWS BugBust event players (admin) (p. 7).

• Import work items (bugs and proﬁling groups) for your event players to claim and ﬁx after you create the event. For more information, see Import work items into an event (admin) (p. 11).

After you create your event, you can update it before its start date by following the steps in Working with an AWS BugBust event (admin and player) (p. 7).

Note

When you create an event, the AWS BugBust service-linked role is created on your behalf. You can safely delete this role after the state of the event is closed. For more information, see Using Service-Linked Roles for AWS BugBust (p. 52) and View the state of an AWS BugBust event (p. 19).

(11)

Invite players (admin)

Working with an AWS BugBust event (admin and player)

The event page contains detailed information about an AWS BugBust bug bash event. You can see how many bugs and proﬁling groups are available to claim, and you can see how many players joined your event. If the event hasn't started, you can see when it starts. If the event already started, you can see how much time remains.

On the event page, an AWS BugBust administrator can edit and view details of an AWS BugBust event before the event starts. After the event starts, the event can't be changed. An AWS BugBust event player can claim bugs and proﬁling groups, see how many points they earned, and view event details.

During the lifecycle of an event, it goes the following three or four states. For more information, see View the state of an AWS BugBust event (p. 19).

• Coming soon – An event is coming soon after it is created and before its start time.

• Active– An event is active after its start time and before its end time.

• Finalizing points– An event enters the finalizing points state only if it contains profiling groups to work on. A event enters the finalizing points state after its end time and before all profiling groups have been evaluated to determine how many points each checked-in profiling group improvement is worth.

• Closed– An event is closed immediately after its end time if it only contains bugs. If it contains proﬁling groups, then it is closed after all proﬁling groups are evaluated and all points are allocated.

Topics

• Invite AWS BugBust event players (admin) (p. 7)

• Update an AWS BugBust event (admin) (p. 8)

• Tagging an event in AWS BugBust (admin) (p. 9)

• Import work items into an event (admin) (p. 11)

• Work with bugs in an AWS BugBust event (admin and player) (p. 12)

• Work with proﬁling groups in an AWS BugBust event (admin and player) (p. 15)

Invite AWS BugBust event players (admin)

After you create your event, an AWS BugBust administrator can start inviting players to it. An invited player cannot who joins an event cannot be removed.

Players who join your event can claim work items and compete with other players to see who can earn the most points by ﬁxing bugs and improving the performance of applications. An invited player receives a special URL. When the invited player visits that URL, they choose Join event, which grants them the required permissions. An event player cannot invite another player into an event. For more information, see Joining an AWS BugBust event (p. 24).

For a player to access an event, you must do the following.

1. Grant each player the permissions in the AWSBugBustPlayerAccess AWS managed policy. For more information, see AWSBugBustPlayerAccess managed policy for players (p. 43).

(12)

Update an event (admin)

2. Send them a URL to join your event.

• If your organization uses a SSO (single sign-on) sign-in URL to log in to AWS, send them that URL.

• If your organization doesn't use a SSO (single sign-on) sign-in URL to log in to AWS, send them the automatically generated URL that appears in the email text in the AWS BugBust console. For more information, see the procedure later in this topic.

If you use AWS SSO, see How to sign in to the player portal in the AWS SSO User Guide for more information.

Invite players to an event

2. On the navigation pane, expand AWS BugBust, choose Events, and then choose the name of the event to which you want to add players.

3. Do one of the following.

• Choose the Invite players.

• Choose Dashboard, then choose Invite players.

• Choose Leaderboard, then choose Invite players.

4. Choose Copy all to copy the event invitation. The invitation includes the link your players use to join the event and information about AWS BugBust events.

5. Choose Done.

6. Paste the copied text into an email, make any edits you'd like to change, then send it to the players you want to invite.

Important

If your company uses a unique SSO (single sign-on) URL to log in to AWS, replace the link to join in the invite email with your organization's SSO URL.

Update an AWS BugBust event (admin)

An AWS BugBust event administrator can update an event after it's created and before it starts. After an event starts, the only update you can make is to invite more players.

Update an event

2. On the navigation pane, expand BugBust, choose Events, and then choose the name of the event for which you want to view tags.

3. Choose Dashboard.

4. Choose Edit event details.

a. Choose Edit in Basic information to update the name, description, start time, or end time of your event. When you are done, choose Save changes.

b. Choose Edit in Prizes to update your event prizes. When you are done, choose Save changes.

c. Choose Manage tags in Tags to add or update event tags. When you are done, choose Save changes. For more information, see Tagging an event in AWS BugBust (admin) (p. 9).

5. Choose Invite players to add players to your event. For more information, see Invite AWS BugBust event players (admin) (p. 7). You can add more players after your event starts. This is the only change you can make to your event after it starts.

6. Choose Import work items to add bugs, proﬁling groups, or both to your event for your players to work on. For more information, see Import work items into an event (admin) (p. 11).

(13)

Tagging an event (admin)

Tagging an event in AWS BugBust (admin)

In AWS BugBust, you can use the AWS BugBust console to add, manage, and remove tags for one

resource type, an AWS BugBust event. In addition to identifying, organizing, and tracking your event with tags, you can use tags in IAM policies to help control who can view and interact with your event.

A tag is a custom attribute label that you or AWS assigns to an AWS resource. Each AWS tag has two parts:

• A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case sensitive.

• An optional ﬁeld known as a tag value (for example, 111122223333, Production, or a team name).

Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case sensitive.

Together these are known as key-value pairs. For limits on the number of tags you can have on an event and restrictions on tag keys and values, see Tags (p. 62).

Tags help you identify and organize your AWS resources. Many AWS services support tagging, so you can assign the same tag to resources from diﬀerent services to indicate that the resources are related. For example, you can assign the same tag to an AWS BugBust event that you assign to an Amazon CodeGuru Reviewer associated repository. For more information about using tags, see the Tagging best practices whitepaper.

Topics

• Add a tag to an AWS BugBust event (p. 9)

• View tags for an AWS BugBust event (p. 10)

• Add, update, or remove AWS BugBust event tags (p. 10)

Add a tag to an AWS BugBust event

Adding tags to an event can help you identify and organize your AWS resources and manage access to them. First, you add one or more tags (key-value pairs) to an AWS BugBust event. Keep in mind that there are limits on the number of tags you can have on an event. There are restrictions on the characters you can use in the key and value ﬁelds. For more information, see Tags (p. 62). After you have tags, you can create IAM policies to manage access to the event based on these tags. You can use the AWS BugBust console to add tags to an event.

You can use the console to add a tag when you create an event or to one that already exists.

Topics

• Add a tag when you create an AWS BugBust event (p. 9)

• Add a tag to an existing AWS BugBust event (p. 10)

Add a tag when you create an AWS BugBust event

You can use the AWS BugBust console to add one or more tags when you create an AWS BugBust event.

Add a tag when you create an event

1. Follow steps 1-3 in the following topic to start creating an AWS BugBust event.

2. In step 4, expand Tags.

3. Choose Add new tag.

4. In Key, enter a name for the tag. You can add an optional value for the tag in Value.

(14)

View tags for an event

5. (Optional) To add another tag, choose Add new tag again.

6. Complete the rest of the steps to create your event.

Add a tag to an existing AWS BugBust event

You can use the AWS BugBust console to add one or more tags to an existing AWS BugBust event.

Add a tag to an existing event

2. On the navigation pane, expand BugBust, choose Events, and then choose the name of the event you want to update.

3. Choose Event details.

4. Choose Manage tags.

5. Choose Add new tag.

6. In Key, enter a name for the tag. You can add an optional value for the tag in Value.

7. Choose Save changes when you are ﬁnished.

View tags for an AWS BugBust event

Tags can help you identify and organize your AWS resources and manage access to them. For more information about tagging strategies, see Tagging AWS resources.

You can use the AWS BugBust console to view the tags associated with an AWS BugBust event.

To view tags for an event

5. Look under Tags to see the tags associated with the event.

Add, update, or remove AWS BugBust event tags

You use the AWS BugBust console to update, add, or remove the tags associated with an event. You can also change the name of the key, which is equivalent to removing the current tag and adding a diﬀerent one with the new name and the same value. Keep in mind that there are limits on the characters you can use in the key and value ﬁelds. For more information, see Limits (p. 62).

To add or update tags for an event

4. Choose Manage tags.

5. Enter new values in key and value to edit tags. Choose Remove next to a tag to remove it. Choose Add new tag to add a new tag.

(15)

Import work items (admin)

Import work items into an event (admin)

A work item is a bug or performance issue for AWS BugBust event players to claim and ﬁx. Players compete with other event players to see who can earn the most points by ﬁxing bugs and performance issues. AWS BugBust administrators import work items when setting up an event. After an AWS BugBust administrator creates an event, the administrator can update the event by importing more work items.

You can import more work items after you create your event, but not after your event starts.

Important

If you import bugs from Amazon CodeGuru Reviewer into your event, do not diasassociate the associated repository that contains the code with the bugs. Players cannot score points by ﬁxing bugs in a disassociated repository. For more information, see Disassociate a repository in the CodeGuru Reviewer User Guide.

Start importing work items

You can import CodeGuru Reviewer work items after you create an AWS BugBust event.

Start importing work items into an event

2. On the navigation pane, expand AWS BugBust, choose Events, and then choose the name of the event into which you want to import work items.

4. Choose Import work items. Continue with one of the import topics later in this section.

Topics

• Import bugs from CodeGuru Reviewer code analyses (p. 11)

• Import performance issues from CodeGuru Proﬁler proﬁling groups (p. 12)

• Import bugs from CodeGuru Reviewer and performance issues from CodeGuru Proﬁler (p. 12)

Import bugs from CodeGuru Reviewer code analyses

Bugs imported from Amazon CodeGuru Reviewer are detected during code analysis of a branch in a repository. For more information, see Working with code reviews in the Amazon CodeGuru Reviewer User Guide. You can choose up to 5 repository analyses.

All bugs CodeGuru Reviewer ﬁnds in the repository analyses you choose are imported into your AWS BugBust event for players to claim and ﬁx.

Note

You cannot import bugs into AWS BugBust found during a CodeGuru Reviewer pull request code review.

Import bugs using repository analysis

1. In Import work items, choose Only import bugs from CodeGuru Reviewer.

2. In Choose a repository analysis in your AWS account and Region, choose up to ﬁve repository analyses. You can choose from the repository analyses in associated repositories in your AWS account and Region. For more information, see Working with repository associations in CodeGuru Reviewer in the Amazon CodeGuru Reviewer User Guide.

3. If you want to import a new repository analysis, choose Create new repository analysis. Follow the steps in CodeGuru Reviewer. For more information, see Get recommendations using repository

(16)

Import performance issues from proﬁling groups

analysis and Create code reviews with security analysis in CodeGuru Reviewer in the Amazon CodeGuru Reviewer User Guide.

4. Choose Next.

Import performance issues from CodeGuru Proﬁler proﬁling groups

An Amazon CodeGuru Profiler profiling group is a group of applications that CodeGuru Profiler analyzes for performance issues. You can import up to 25 profiling groups.

Note

It takes approximately one or two days of profiling by CodeGuru Profiler to populate a profiling group with information required to improve it. Because of this, you should import profiling groups that are at least two days old. If you choose to create a new profiling group in the following procedure, be sure to do that at least two days before your event starts.

Import proﬁling groups

1. In Import work items, choose Only import proﬁling groups from CodeGuru Proﬁler.

2. In Choose a proﬁling group in your AWS account and Region, choose one or more proﬁling groups.

You can choose from the profiling groups in your AWS account and Region. For more information, see Working with profiling groups in the Amazon CodeGuru Profiler User Guide.

3. If you want to import a new profiling group, choose Create new profiling group. Follow the steps in CodeGuru Profiler. For more information, see Create a CodeGuru Profiler profiling group in the Amazon CodeGuru Profiler User Guide.

4. Choose Next.

Import bugs from CodeGuru Reviewer and performance issues from CodeGuru Proﬁler

You can import bugs and performance issue work items for into your AWS BugBust event. These work items are available to your event's players to claim and ﬁx.

Import bugs and performance issues

1. In Import work items, choose Import bugs from CodeGuru Reviewer and proﬁling groups from CodeGuru Proﬁler.

2. Follow the steps in Import bugs from CodeGuru Reviewer code analyses (p. 11) to import bugs from CodeGuru Reviewer beginning with step 2. Do not choose Next until you complete the next step.

3. Follow the steps in Import performance issues from CodeGuru Profiler profiling groups (p. 12) to import performance issues from CodeGuru Profiler beginning with step 2. Be sure to choose Next in the last step.

Work with bugs in an AWS BugBust event (admin and player)

On an AWS BugBust event page, you can view the event's bugs, see how many are claimed and unclaimed, and see how many are ﬁxed. On an event page, players can also claim bugs to work on. A

(17)

Find bugs in an AWS BugBust event (admin and player)

player can claim up to ten bugs at a time. For information about how many points are awarded for ﬁxing a bug, see Scoring with Amazon CodeGuru Reviewer bug ﬁxes (p. 25).

Topics

• Find bugs in an AWS BugBust event (admin and player) (p. 13)

• Setting the status of a bug (admin) (p. 13)

• Claim or unclaim a bug (player) (p. 14)

• Submit a bug ﬁx (player) (p. 14)

• View bug ﬁx pull requests (player) (p. 15)

Find bugs in an AWS BugBust event (admin and player)

You can view your event's bugs on its event page. Your event page has bugs if the AWS BugBust event administrator imported bugs for players to work on. For more information, see Import bugs from CodeGuru Reviewer code analyses (p. 11).

View an event's imported bugs

1. If you are not on your event details page, follow the appropriate steps in View AWS BugBust event information (admin and player) (p. 19) to open it.

2. Choose Bugs.

An event can have many more bugs than can appear in the event console page at a time. Enter a term in Find bugs to ﬁnd a bug you want to claim and ﬁx. You can search on the following properties.

• Repository – The name of the repository that contains the code in which a bug is found.

• Branch – The branch in a repository that contains the code in which a bug is found.

• Path – The path of the ﬁle that contains the code in which a bug is found.

• Status – The status of the bug, which is claimed, unclaimed, or ﬁxed.

• Category – The category of the bug, which determines how many points it's worth. For the list of categories, see Scoring with Amazon CodeGuru Reviewer bug ﬁxes (p. 25).

• Points – The number of points awarded when a bug is ﬁxed. The valid scores are 5, 3, and 1. For more information, see Scoring with Amazon CodeGuru Reviewer bug ﬁxes (p. 25).

You can also sort the bugs by how many points they are worth.

Setting the status of a bug (admin)

You can set the status of a bug to unclaimed, fixed, or false positive. If you set the status of a bug to unclaimed, then any player can claim that bug to fix. After a bug is marked false positive or fixed, its status cannot be updated again.

A false positive bug is a bug found by Amazon CodeGuru Reviewer that isn't actually a bug. Because CodeGuru Reviewer uses machine learning to detect bugs, on rare occasions it detects a bug that doesn't exist in clean code.

To override the review process, set the status of a bug to fixed. This automatically assigns the player the number of points that corresponds with the bug's category and bypasses the process to submit its fix. For more information, see Submit a bug fix (player) (p. 14).

(18)

Claim or unclaim a bug (player)

Change the status of a bug

2. Choose Bugs.

3. Select a bug. For information about ﬁnding a speciﬁc type of bug, see Find bugs in an AWS BugBust event (admin and player) (p. 13).

4. From the Mark as dropdown list, choose Mark as unclaimed, Mark as ﬁxed or Mark as false- positive.

Claim or unclaim a bug (player)

You must claim a bug before you start working on fixing it. When you claim a bug, no one else can claim the bug. If the code you submit doesn't actually fix the bug, then the status of the bug returns to unclaimed for any player in your event to claim. You can claim up to ten bugs at a time To earn points, you must fix and then submit a claimed bug before your event ends. For more information, see Submit a bug fix (player) (p. 14).

Claim or unclaim a bug

2. Choose Bugs.

3. Select a bug. For information about ﬁnding a speciﬁc type of bug, see Find bugs in an AWS BugBust event (admin and player) (p. 13).

a. Choose Claim to claim a bug. You can only claim bugs with a status of unclaimed.

b. Choose Unclaim to unclaim a bug. You can only unclaim bugs that are claimed by you.

Submit a bug ﬁx (player)

After you are done ﬁxing your bug, submit it to earn points for your bug ﬁx. Do the following to submit your bug.

• Create a pull request to submit the code with your bug ﬁx. The pull request initiates a new Amazon CodeGuru Reviewer code review.

• Merge your code into its branch.

If the bug you ﬁxed is not found during the code review, then you are assigned the number of points associated with your bug's category.

If the code review determines your submitted code did not fix the bug, then the bug continues to be claimed by you until you fix or unclaim it. You can attempt to fix the same bug multiple times until a code review no longer detects it. For each attempted fix, create a new pull request and merge your code to submit it again. When the bug is no longer detected, you earn points. For more information, see Rules and scoring in AWS BugBust (p. 25).

Important

If the email you use for the commit that creates the pull request to submit a bug ﬁx is not added as an authorized email in your AWS BugBust player portal, you cannot score points. To learn how to add additional authorized email addresses, see Adding authorized email addresses in the AWS BugBust player portal (p. 28)

(19)

View bug ﬁx pull requests (player)

After you submit a bug ﬁx, you can view the pull request you used to check in the code. All your pull request appear in the same place.

Your pull requests appear with their status. A pull request can have one of six statuses.

• Analyzing – An analyzing pull request has been recently submitted and Amazon CodeGuru Reviewer is analyzing the updated code.

• Error – An error pull request is in an error state.

• No fix detected – CodeGuru Reviewer has analyzed a no fix detected pull request and found the bug you attempted to fix. You do not earn points when the bug was not fixed. You can continue to try fixing the bug by submitting an updated bug fix with a new pull request.

• Waiting for merge – CodeGuru Reviewer has analyzed a waiting for merge pull request and it did not find the bug you attempted to fix. This means your bug fix succeeded. You must merge the code of pull requests in this state in order to earn points for the bug fix.

• Merging – A merging pull request is merging. A pull request enters this state after the code merge into its branch is initiated.

• Success – A success pull request is merged. The code in the pull request ﬁxed the bug and points for the bug have been assigned to you.

View your pull requests

2. Choose Bugs.

3. Choose My pull requests.

Important

If you created a pull request for a bug ﬁx and don't see it in your event, try the following.

• Make sure the email you used to create your pull request is added as an authorized email to your AWS BugBust account. For more information, see Adding authorized email addresses in the AWS BugBust player portal (p. 28).

• Make sure the email you use to create your pull request is public, not private. Refer to your repository vendor's documentation to learn how to verify this.

If you see your pull request, but have not received points for ﬁxing the bug, make sure you have merged the request. To earn points for a bug ﬁx, you must create a pull request and merge it into your branch.

Work with proﬁling groups in an AWS BugBust event (admin and player)

On an AWS BugBust event page, you can view the event's profiling groups, see how many are claimed and unclaimed, and see how many have been improved. On an event page, players can also claim profiling groups to work on. A player can claim up to three profiling groups at a time. A player can work on a profiling group until the state of the event is set to finalizing points. When an event's state is finalizing points, the event is over and players' scores and rankings are being calculated. For more

(20)

Find proﬁling groups in an AWS BugBust event (admin and player)

information, see View the state of an AWS BugBust event (p. 19) and Scoring with Amazon CodeGuru Proﬁler performance improvements (p. 25).

Topics

• Find proﬁling groups in an AWS BugBust event (admin and player) (p. 16)

• Evaluate a proﬁling group (admin) (p. 16)

• Setting the status of a proﬁling group (admin) (p. 17)

• Claim a proﬁling group (player) (p. 17)

• Submit a proﬁling group improvement (player) (p. 17)

Find proﬁling groups in an AWS BugBust event (admin and player)

You can view your event's profiling groups on its event page. Your event page has profiling groups if its administrator imported profiling groups for players to work on. For more information, see Import performance issues from CodeGuru Profiler profiling groups (p. 12).

View an event's imported proﬁling groups

2. Choose Proﬁling groups.

An event can have more profiling groups than can appear in the event console page at a time. To find a profiling group you want to claim and work on, you can search for the following properties by entering a term in Find bugs.

• Proﬁling group – The name of the proﬁling group that contains the set of applications on which you want to work.

• Status – The status of the proﬁling group, which is claimed, unclaimed, checked-in, or evaluated.

• Points – The number of points that can be awarded when you check in code that improves the performance of the applications in a proﬁling group. For more information, see Scoring with Amazon CodeGuru Reviewer bug ﬁxes (p. 25).

You can also sort the proﬁling groups by how many points they are worth.

Evaluate a proﬁling group (admin)

The administrator evaluates an update to a profiling group that is submitted by a player. To submit the update, the player creates a pull request to check in their code, then notifies the administrator that their code is checked in. For more information, see Submit a profiling group improvement (player) (p. 17).

Evaluate a checked-in proﬁling group

3. If there are checked-in profiling groups in your event that have not been evaluated, choose Evalute n checked-in profiling groups, where n is the number of checked-in profiling groups that haven't been evaluated.

(21)

Setting the status of a proﬁling group (admin)

When the profiling groups are evaluated, CodeGuru Profiler determines how much more efficient their CPU usage is. Points are assigned based on the percent of improvement. When evaluation is complete, the status of the evaluated profiling groups updates to evaluated.

Setting the status of a proﬁling group (admin)

A proﬁling group can have one of four statuses.

• Unclaimed – An unclaimed proﬁling group is available for any player to claim and work on. After a proﬁling group is claimed, another player cannot claim it.

• Claimed – A claimed proﬁling group is claimed by an event player. Only that player can work on the proﬁling group and check in code to improve it.

• Checked-in – A checked-in proﬁling group has been checked in by the player who claimed it. A checked- in proﬁling group is ready for the admin to evaluate to determine how much the player's code

improved the proﬁling group and then assign the appropriate points.

• Evaluated – An evaluated profiling group has been evaluated and points have been assigned based on how much more efficient the player's code made the profiling group. After the event has ended and all checked-in profiling groups have been evaluated, the event's status updates to closed.

An administrator can set the status of a profiling group from to claimed to unclaimed. If you set the status of a profiling group to unclaimed, then any player can claim that profiling group to improve it.

Change the status of a proﬁling group from claimed to unclaimed.

3. Select a profiling group. For information about finding a specific type of profiling group, see Find profiling groups in an AWS BugBust event (admin and player) (p. 16).

4. From the Mark as dropdown list, choose Mark as unclaimed.

Claim a proﬁling group (player)

You must claim a profiling group before you start working on improving it. When you claim a profiling group, no one else can claim the profiling group. You can claim up to three profiling groups at a time.

Claim a proﬁling group

3. Select a profiling group. For information about finding a specific type of profiling group, see Find bugs in an AWS BugBust event (admin and player) (p. 13). You can also choose Unclaimed profiling groups to view all profiling groups you can claim.

4. Choose Claim on a proﬁling group on which you want to work. When you do this, its status updates to claimed.

Submit a proﬁling group improvement (player)

After you are done writing code that improves a claimed proﬁling group, you submit it by creating a pull request in your code's repository. Next, you check it in from the AWS BugBust console. This notiﬁes

(22)

Submit a proﬁling group improvement

your event's administrator that it is ready to be evaluated. During evaluation of your code, the admin determines how much more eﬃcient your code made the proﬁling group. The greater the improvement, the more points you earn. For more information, see Rules and scoring in AWS BugBust (p. 25).

There is no time limit to improving a proﬁling group as long as it is submitted and checked in before its event ends.

Submit a proﬁling group improvement

1. Submit your updated code by creating a pull request in your code's repository.

4. Find the profiling group you want to check in. Only check in profiling groups for which you have submitted fixes.

5. On the proﬁling group, choose Check in.

(23)

View the state of an event

View AWS BugBust event

information (admin and player)

The event page contains detailed information about an AWS BugBust bug bash event. You can see how many bugs and proﬁling groups are available to claim, and you can see how many players joined your event. If the event hasn't started, you can see when it starts. If the event already started, you can see how much time remains.

An AWS BugBust administrator can edit and view details of an AWS BugBust event before the event starts. A player can view details of an event, but cannot edit it. For more information, see Update an AWS BugBust event (admin) (p. 8).

The steps to view an events details are diﬀerent for administrators and players.

View AWS BugBust event details (admin)

2. Choose Events.

3. Choose the name of the event you want to view.

View AWS BugBust event details (player)

Your event administrator sent you a link to join your event. Visit that link to view your event in the player portal. If you do not have that link, do the following.

1. Open the AWS BugBust console at https://console.aws.amazon.com/codeguru/bugbust/participant.

2. Choose Events.

3. Choose the name of the event you want to view.

On your AWS BugBust event page, you can view the following for more details.

Topics

• View the state of an AWS BugBust event (p. 19)

• View an AWS BugBust event dashboard (p. 20)

• View an AWS BugBust event leaderboard (p. 21)

• View an AWS BugBust event's details (p. 21)

• View AWS BugBust rules and scoring (p. 21)

View the state of an AWS BugBust event

An event can be in one of four states.

1.Coming soon – Immediately after you create an event, its status is coming soon. Its remains coming soon until the event's start date and time. You can update all event details in this state.

(24)

View an event dashboard

2.Active – At the event's start time, its status changes to active. When an event is active, players can claim and ﬁx bugs and performance issues. You can import more items and invite more players to an event while it's active. You cannot update its details, such as its name, description, allowed domains, and prizes while it's active.

3.Finalizing points – If an event contains imported profiling groups, then after its end time, its status changes to finalizing points. When an event is finalizing points, profiling group improvements submitted by players are evaluated to determine by what percentage they improve the profiling group's application's CPU usage. When this process is complete, the appropriate points are assigned to players who submitted profiling group performance improvements.

4.Closed – After the event's end time, and, if the event contains proﬁling groups after the ﬁnalizing points status, the event status changes to closed. When an event is closed, all points are assigned and the ranking of all players is complete. The event administrator is responsible for prize delivery after the event is closed.

Note

After an event is closed, you can safely delete the service-linked role. For more information, see Using Service-Linked Roles for AWS BugBust (p. 52).

View an AWS BugBust event state

2. You can view the state of an event in the following places.

• The state appears next to the name of the event.

• Choose Dashboard. The event states appear on the dashboard and the current state is highlighted.

View an AWS BugBust event dashboard

The dashboard of an AWS BugBust event shows high-level information about its bugs and proﬁling groups. If the event hasn't started, you can also use the dashboard to update some of its details.

View an AWS BugBust event dashboard

The event dashboard shows information about the following.

• Bugs –The total number of bugs in your event, and how many are claimed, unclaimed, and ﬁxed. If you are a player, you can see how many bugs you have claimed and ﬁxed.

• Profiling groups – The total number of profiling groups in your event, how many are claimed, checked in, and evaluated. An evaluated profiling group has been analyzed to determine how many points its checked-in code is worth based its CPU usage performance improvement. If you are a player, you can see how many profiling bugs you have claimed and how many of your claimed profiling groups are evaluated. For more information, see Scoring with Amazon CodeGuru Profiler performance improvements (p. 25). You can also see an estimate of how much money is saved by the improvements in the evaluated profiling groups.

• Points and ranking – If you are a player, you can view your rank among all of the event's players and how many points you have earned.

• The state of the event – For more information, see View the state of an AWS BugBust event (p. 19).

(25)

View an event leaderboard

If the event hasn't started, you can update the following from the dashboard.

• Details – Choose Edit event detail to update an event's name, description, start and end time, and prizes. For more information, see Enter AWS BugBust event details (p. 5).

• Work items – Choose Import work items to import more bugs, proﬁling groups, or both into the event. For more information, see Import work items (admin) (p. 11).

• Players – Choose Invite players to invite more players to the event. For more information, see Invite AWS BugBust event players (admin) (p. 7).

View an AWS BugBust event leaderboard

You can the top scoring players in your event on its leaderboard. The leaderboard is updated as points are assigned from ﬁxing bugs and improving proﬁling groups. For more information, see Rules and scoring in AWS BugBust (p. 25).

View an event's leaderboard

2. Choose Leaderboard.

View an AWS BugBust event's details

An AWS BugBust administrator and player can view details about an event on the event dashboard. A player cannot change an event from the dashboard. An administrator can update an event from the dashboard. For more information, see Update an AWS BugBust event (admin) (p. 8).

View an event's details

2. Choose Event detail.

View AWS BugBust rules and scoring

You can view the AWS BugBust event rules and how points are scored. The rules and scoring for all AWS BugBust events is the same. For more information, see Rules and scoring (p. 25).

View rules and scoring in AWS BugBust

2. Choose Rules and scoring.

(26)

Accessing the AWS Management Console for AWS BugBust events

Creating the AWS BugBust accounts required to use AWS BugBust

AWS BugBust administrators and players are required to have a AWS BugBust player portal account and have access to the AWS Management Console to use AWS BugBust.

Accessing the AWS Management Console for AWS BugBust events

An AWS BugBust administrator uses their AWS credentials to access the AWS BugBust console to create an event. For information about how to create an event and the required permissions, see Create an AWS BugBust event (admin) (p. 3).

For a player to access an AWS BugBust event on the AWS Management Console:

1. Grant each player the permissions in the AWSBugBustPlayerAccess AWS managed policy. For more information, see AWSBugBustPlayerAccess managed policy for players (p. 43).

2. Send them a URL to join your event.

• If your organization uses a SSO (single sign-on) sign-in URL to log in to AWS, send them that URL.

• If your organization doesn't use a SSO (single sign-on) sign-in URL to log in to AWS, send them the automatically generated URL that appears in the email text in the AWS BugBust console. For more information, see Invite players (admin) (p. 7).

To learn how to sign in as an IAM user, see How IAM Users Sign In to AWS in the IAM User Guide.

If you use AWS SSO, see How to sign in to the player portal in the AWS SSO User Guide for more information.

Accessing the AWS BugBust player portal for AWS BugBust events

Before you can join an event, you need to create a AWS BugBust player portal account. To create an account, you need to provide a valid email address and to create a password.

You cannot change the initial email address used to create your AWS BugBust account. To earn points during AWS BugBust events, you might need to add additional authorized email addresses. For more information, see Adding authorized email addresses in the AWS BugBust player portal (p. 28).

Important

(27)

Accessing the AWS BugBust player portal for AWS BugBust events

To create a AWS BugBust player portal account

1. Open the https://bugbust.aws landing page.

2. Choose New to AWS BugBust? Create an account.

3. For Your email address, enter a valid email address.

4. For Choose a password, enter a valid password.

Passwords for AWS BugBust must be at least 8 characters and must contain at least one of the following: an uppercase character, a lowercase character, a number, and a symbol.

5. Choose Create your account.

6. Next, AWS BugBust emails you a veriﬁcation code. Copy your veriﬁcation code.

7. Enter your veriﬁcation code under Veriﬁcation code and then choose Verify.

(28)

Joining an AWS BugBust event

To join an AWS BugBust event, you need an email invitation from your AWS BugBust administrator and access to the AWS Management Console. The invitation comes directly from your AWS BugBust administrator email address, not from AWS. If you can't ﬁnd the invite, contact your AWS BugBust administrator.

Invitations to AWS BugBust events expire when the event has closed.

You may be asked to periodically reauthorize your registered AWS BugBust email address.

If you've received an email invite to a AWS BugBust event and cannot access your event, you might need AWS BugBust speciﬁc permissions added to your IAM user or role. Your event's administrator can grant you the required permissions. For more information see, AWSBugBustPlayerAccess managed policy for players (p. 43).

To join an AWS BugBust event

1. Find the email from your AWS BugBust administrator and locate the link to your AWS BugBust event.

2. Choose the invitation link.

3. On the AWS Management console, use your IAM credentials to log in to AWS BugBust.

Note

If you are not familiar with logging in to the AWS Management Console, see Signing in to the AWS Management Console as an IAM user or root user.

If you receive an error message that says You don't have permission to access this event, contact your AWS BugBust event administrator. They may need to add additional permissions to your IAM users or role. For more information, see AWSBugBustPlayerAccess managed policy for players (p. 43).

4. On the AWS BugBust participants event details page, choose Join event.

After joining an event, you can see the event Dashboard and details about the status of your event. To see your event's leaderboard, choose Leaderboard.

To learn more about how to play the AWS BugBust game, see Rules and scoring in AWS BugBust (p. 25).

To learn how to claim bugs, ﬁx bugs, and submit your changes, see Work with bugs in an event (admin and player) (p. 12).

To learn how to claim profiling groups, fix profiling groups, and submit your changes, see Work with profiling groups in an event (admin and player) (p. 15).

(29)

Scoring with CodeGuru Reviewer bug ﬁxes

Rules and scoring in AWS BugBust

AWS BugBust administrators create bug bash events, then AWS BugBust players earn points by ﬁxing the events' bugs and performance issues. Each bug bash event uses the same rules for scoring and determining how players rank and win.

Note

Topics

• Scoring with Amazon CodeGuru Reviewer bug ﬁxes (p. 25)

• Scoring with Amazon CodeGuru Proﬁler performance improvements (p. 25)

Scoring with Amazon CodeGuru Reviewer bug ﬁxes

If an AWS BugBust event is conﬁgured with bugs found during an Amazon CodeGuru Reviewer repository analysis, players can claim up to ten bugs at a time to work on.

Each bug is classiﬁed into one of 10 categories, and the number of points it is worth is determined by the complexity of its category.

Bug categories , severities, and points

Category Severity Points

Concurrency High 5

Security High 5

AWS best practices Medium 3

Duplicated code Medium 3

Input validations Medium 3

Java best practices Medium 3

Resource leaks Medium 3

AWS CloudFormation issues Low 1

Code maintenance issues Low 1

Python best practices Low 1

For more information, see Recommendations in the Amazon CodeGuru Reviewer User Guide.

Scoring with Amazon CodeGuru Proﬁler performance improvements

If an AWS BugBust event is configured with Amazon CodeGuru Profiler profiling groups, players claim up to three profiling groups at a time. Players earn points by fixing performance issues that CodeGuru

(30)

Scoring with CodeGuru Proﬁler performance improvements

Profiler detected in a profiling group. A claimed profiling group contains recommendations provided by CodeGuru Profiler to help fix the performance issues. You can also use advanced tools such as the flame graph associated with your profiling group. For more information, see Working with anomalies and recommendation reports and Working with visualizations in the Amazon CodeGuru Profiler User Guide.

A player deploys code to address the performance issues. Next, the AWS BugBust event administrator evaluates their solution to determine the percentage improvement in CPU usage. The greater the CPU usage improvement, the more points the player earns. The following shows how many points are scored for a performance improvement.

Scoring is based on the average for the day the improvement is calculated. Because of this, a player might earn more points if the evaluation happens at least one day after their changes are submitted. An administrator can evaluate an improvement more than once.

CPU usage improvement and points

CPU usage percent improvement Points

20% or more 13

11% - 20% 8

6% - 10% 5

1% - 5% 3

(31)

Customizing your player avatar in AWS BugBust

How to customize your AWS BugBust player proﬁle

When you join the AWS BugBust game, you can customize your player proﬁle to reﬂect your personal persona.

Note

The following procedures assume you've signed into the AWS BugBust player portal.

You can customize your AWS BugBust player proﬁle by:

• Customizing your player avatar (p. 27)

• Customizing your player nickname (p. 27)

• Adding authorized e-mail addresses (p. 28)

Customizing your player avatar in AWS BugBust

You can update and change your default avatar at any time. Player avatars are not required to be globally unique.

To customize your player avatar in AWS BugBust

1. Open the AWS BugBust player portal.

2. Choose your Player nickname.

3. Then, choose Your proﬁle.

4. Hover over your current avatar and choose Customize your avatar.

5. On the avatar customization page, update the avatar traits that you want to change.

If you delete your account (p. 64), any avatar customizations you made are lost.

Customizing your player nickname in the AWS BugBust player portal

You can update your player nickname at any time.

Player nicknames must be globally unique. Nicknames have fewer than 24 characters and can contain a mixture of characters, symbols, and numbers.

To customize your player nickname in AWS BugBust

(32)

Adding authorized email addresses in the AWS BugBust player portal 3. Then choose Your account.

4. Under Your account, choose Change nickname.

5. On the Change your nickname modal, update your nickname.

6. Next, choose Save nickname to save your changes.

If you delete your account (p. 64), any changes made to your nickname are lost.

Adding authorized email addresses in the AWS BugBust player portal

Authorized email addresses are used in AWS BugBust events to score points. Points are scored based on pull requests created on GitHub for AWS BugBust Bugs. To collect points, you must link any email addresses you use on GitHub prior to submitting a pull request.

If you check in a bug without ﬁrst linking your email address, contact your AWS BugBust administrator for next steps.

If you delete your account (p. 64), any authorized email addresses you have added are deleted.

Important

To add an authorized email address to your AWS BugBust account

3. Choose Your account.

4. Under Authorized emails, add your email address in the Add an authorized email address ﬁeld.

5. Choose Verify.

6. In your email, you receive an alphanumeric code. Enter that code into the Your secret code ﬁeld.

7. Choose Verify and authorize.

AWS BugBust events use authorized email addresses to award points. You score points based on pull requests created on GitHub for AWS BugBust bugs. To collect points, you must link any email addresses you use on GitHub prior to submitting a pull request.

If you check in a bug without ﬁrst linking your email address, contact your AWS BugBust administrator for next steps.

If you delete your account (p. 64), any authorized email addresses you have added are deleted.

(33)

Data protection

Security in AWS BugBust (admin)

Cloud security at AWS is the highest priority. As an AWS customer, you beneﬁt from a data center and network architecture that is built to meet the requirements of the most security-sensitive organizations.

Security is a shared responsibility between AWS and you. The shared responsibility model describes this as security of the cloud and security in the cloud:

• Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the eﬀectiveness of our security as part of the AWS Compliance Programs.

To learn about the compliance programs that apply to AWS BugBust, see AWS Services in Scope by Compliance Program.

• Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations.

This documentation helps you understand how to apply the shared responsibility model when using AWS BugBust. It shows you how to conﬁgure AWS BugBust to meet your security and compliance objectives.

You also learn how to use other AWS services that help you to monitor and secure your AWS BugBust resources.

Contents

• Data protection in AWS BugBust (p. 29)

• Identity and Access Management for AWS BugBust (p. 31)

• Using tags to control access to AWS BugBust events (p. 54)

• Compliance validation for AWS BugBust (p. 57)

• Logging and monitoring in AWS BugBust (p. 58)

• Resilience in AWS BugBust (p. 61)

• Infrastructure security in AWS BugBust (p. 61)

Data protection in AWS BugBust

The following sections explain what data is captured by AWS BugBust, and where AWS BugBust uses data encryption to protect your data. Based on whether you are a player participating in a AWS BugBust event or an administrator creating AWS BugBust events, diﬀerent sections are relevant to you.

You can learn more about AWS data privacy and data protection commitments on the Privacy Notice page.

Topics

• Captured data in AWS BugBust for players and administrators (p. 30)

• Encryption at rest for AWS BugBust players and administrators (p. 30)

• Encryption in transit for AWS BugBust players and administrators (p. 31)

AWS BugBust

AWS BugBust

User Guide

AWS BugBust: User Guide

Table of Contents

What is AWS BugBust?

Note

What is the AWS BugBust player portal?

Create an AWS BugBust event (admin)

Important

Step 1: Provision an IAM user to create an AWS BugBust event

Provision an IAM user to use AWS BugBust and create events

Important

Step 2: Review rules and scoring

Open the create event console page

Step 3: Create or log in to a player account

Note

Create or log in to an AWS BugBust player account

Step 4: Enter AWS BugBust event details

Add details for your AWS BugBust event

Step 5: Review your AWS BugBust event

Note

Working with an AWS BugBust event (admin and player)

Invite AWS BugBust event players (admin)

Invite players to an event

Important

Update an AWS BugBust event (admin)

Update an event

Tagging an event in AWS BugBust (admin)

Add a tag to an AWS BugBust event

Add a tag when you create an AWS BugBust event

Add a tag when you create an event

Add a tag to an existing AWS BugBust event

Add a tag to an existing event

View tags for an AWS BugBust event

To view tags for an event

Add, update, or remove AWS BugBust event tags

To add or update tags for an event

Import work items into an event (admin)

Important

Start importing work items

Start importing work items into an event

Import bugs from CodeGuru Reviewer code analyses

Note

Import bugs using repository analysis

Import performance issues from CodeGuru Proﬁler proﬁling groups

Note

Import proﬁling groups

Import bugs from CodeGuru Reviewer and performance issues from CodeGuru Proﬁler

Import bugs and performance issues

Work with bugs in an AWS BugBust event (admin and player)

Find bugs in an AWS BugBust event (admin and player)

View an event's imported bugs

Setting the status of a bug (admin)

Change the status of a bug

Claim or unclaim a bug (player)

Claim or unclaim a bug

Submit a bug ﬁx (player)

Important

View bug ﬁx pull requests (player)

View your pull requests

Important

Work with proﬁling groups in an AWS BugBust event (admin and player)

Find proﬁling groups in an AWS BugBust event (admin and player)

View an event's imported proﬁling groups

Evaluate a proﬁling group (admin)

Evaluate a checked-in proﬁling group

Setting the status of a proﬁling group (admin)

Change the status of a proﬁling group from claimed to unclaimed.

Claim a proﬁling group (player)

Claim a proﬁling group

Submit a proﬁling group improvement (player)

Submit a proﬁling group improvement

View AWS BugBust event

information (admin and player)

View AWS BugBust event details (admin)

View AWS BugBust event details (player)

View the state of an AWS BugBust event

Note

View an AWS BugBust event state