AWS Amplify cannot connect to Bitbucket — OAuthToken exceeds 1000 character limit after Bitbucket JWT token change

Question

After Bitbucket Cloud's OAuth 2.0 changes (gradually rolled out, confirmed broken as of 2026-08-05), the access tokens from client_credentials grant are now JWT format (~1879 characters). AWS Amplify's OauthToken parameter has a hard limit of 1000 characters, making it impossible to connect Bitbucket repositories.

## How to reproduce

Following the official AWS guide: https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/integrate-a-bitbucket-repository-with-aws-amplify-using-aws-cloudformation.html

1. Create OAuth Consumer in Bitbucket with required permissions
2. Request token:
```
curl -X POST -u "KEY:SECRET" https://bitbucket.org/site/oauth2/access_token -d grant_type=client_credentials
```
3. Token returned is now ~1879 characters (JWT format)
4. Any attempt to use this token fails:
```
Error: "1 validation error detected: Value at 'oauthToken' failed to satisfy constraint: Member must have length less than or equal to 1000"
```

## Affected surfaces

- AWS CLI (aws amplify create-app / update-app)
- AWS CloudFormation (AWS::Amplify::App OauthToken property)
- AWS CDK
- AWS Console (Amplify Hosting UI — connecting Bitbucket)

ALL methods fail with the same 1000-character validation error.

## Token length comparison
| Period | Token Format | Length | Amplify Limit |
|--------|-------------|--------|---------------|
| Before 2026-05-04 (per Atlassian announcement) | Opaque string | ~88 chars | 1000 chars (OK) |
| Confirmed working on 2026-07-30 | Opaque string | ~88 chars | 1000 chars (OK) |
| 2026-08-05 (today) | JWT | ~1879 chars | 1000 chars (FAIL) |

## Context

- Bitbucket deprecated App Passwords on 2026-06-09
- Bitbucket changed OAuth tokens to JWT format (announced 2026-05-04, gradually enforced)
- Repository Access Tokens return "This API is not accessible by this authentication mechanism" because Amplify calls workspace-level APIs
- There is currently NO viable workaround for new Bitbucket integrations with Amplify

## Expected behavior

Amplify should increase the OauthToken maxLength limit, or provide an alternative connection mechanism compatible with Bitbucket's new token format.

## References

- Atlassian announcement: https://community.developer.atlassian.com/t/oauth-2-0-and-api-authentication-changes-for-bitbucket-cloud/99003
- App Password deprecation: https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation
- AWS official guide (now broken): https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/integrate-a-bitbucket-repository-with-aws-amplify-using-aws-cloudformation.html

## Error Pages

This problem also exists in Amplify console, not just CFN and API
![This problem also exists in Amplify console, not just CFN and API](/media/postImages/original/IM7ZERz0LTRpO0ofxhWhtAZg)

Matt D · Answer

Following, as I have exact same scenario and errors: 
 - I cannot provision new Amplify apps from Bitbucket because of the errors show in OPs post. 
 - All of my existing deployments are also broken. 
Timing is the same, and affecting every workload in my organization.

Titan Lin · Answer

It looks list Amplify team fixed this issue in AWS management console **BUT** still get error in Cloudformation.

```
7:24:23 AM | CREATE_FAILED           | AWS::Amplify::App           | AppF1B96344
Properties validation failed for resource AppF1B96344 with message:
#/OauthToken: expected maxLength: 1000, actual: 1879

❌  oo-xx failed: DeploymentError: Resource updates failed:
```

AWS Amplify cannot connect to Bitbucket — OAuthToken exceeds 1000 character limit after Bitbucket JWT token change

How to reproduce

Affected surfaces

Token length comparison

Context

Expected behavior

References

Error Pages

Add your answer

Relevant content

Period	Token Format	Length	Amplify Limit
Before 2026-05-04 (per Atlassian announcement)	Opaque string	~88 chars	1000 chars (OK)
Confirmed working on 2026-07-30	Opaque string	~88 chars	1000 chars (OK)
2026-08-05 (today)	JWT	~1879 chars	1000 chars (FAIL)