Bitbucket blocks AWS CodeConnections app with "You can only install for a team"

[Steve Anger]

I'm trying to connect a Bitbucket Cloud repository to AWS via AWS CodeConnections. When I reach the "Install a new app" step, Bitbucket immediately returns:

"You can only install for a team. You must be an admin for a team to install AWS CodeStar. Create a team or contact your team admin to begin installation."

No workspace-selection ("Authorize for") prompt appears — the error shows instead. The Bitbucket authorize URL reached is:

https://bitbucket.org/site/addons/authorize?addon_key=aws-codestar&redirect_uri=https%3A%2F%2Fcodestar-connections.webhooks.aws%2Fredirect

My account is a workspace administrator (member of the admin user group) and a confirmed direct member in the workspace User directory. There is only one workspace in the account. The original workspace owner reproduces the identical error with their own account.

MFA and IP filtering are not enabled.

I seem to have exhausted everything I can try on my end. Is there any way to check on Bitbucket's end why the connection is not being authorized?

[HEMANT SAINI]

@Steve Anger 

The error “You can only install for a team” is outdated Bitbucket Cloud wording from before Workspaces existed. It appears when the AWS CodeStar app thinks you’re trying to install to a personal account, even if you’re actually in a Workspace.

AWS CodeConnections / CodeStar installs only at the Workspace level and cannot be added to personal repositories.

Why this happens:
Bitbucket checks if the install target is a “team” (now called a Workspace). If the OAuth flow can’t detect a valid Workspace context, it shows this message and skips the “Authorize for” screen.

Since you and the original owner both hit this, and you are Workspace admins, it usually means one of the following:

Fixes to try:

1. Workspace must not be a personal workspace
   AWS won’t install to the default personal workspace Bitbucket creates for every user.
   Check: bitbucket.org/ → Workspace settings → Plan details.
   If it says “Personal” under Workspace type, create a new Workspace, transfer the repo there, and install the app on that Workspace. Personal workspaces don’t support app installs.

2. You need at least one repo in the Workspace
   CodeStar won’t install into empty Workspaces. Even a dummy repo is enough. Bitbucket won’t show the auth screen if there’s nothing to connect.

3. Try installing from the Workspace settings page
   Don’t start from AWS. Go directly to:
   https://bitbucket.org/<workspace-id>/workspace/settings/addon-management → Install app from URL → paste aws-codestar.
   If it installs there, go back to AWS CodeConnections and it should detect it.

If none of this works:
It’s likely a Bitbucket bug where the Workspace context isn’t passed to the OAuth flow. Contact Atlassian Support and include:

• The exact authorize URL you used
• Your Workspace ID
• The requestId from your browser’s DevTools Network tab when the error appeared
• Confirmation that the Workspace isn’t “Personal” type

They can investigate why the addon_key=aws-codestar request didn’t map to a Workspace.

Note: AWS has a known issue where the redirect sometimes drops the Workspace parameter. Starting the install flow from Bitbucket instead of AWS avoids this.