fix(amplify-e2e-tests): handle InvalidClientTokenId in getAmplifyApps opt-in region cleanup#3512
Merged
svidgen merged 1 commit intoJul 9, 2026
Conversation
… opt-in region cleanup Opt-in regions (ap-east-1/eu-south-1) are not enabled on test accounts, causing getAmplifyApps to throw InvalidClientTokenId which propagates to process.exit(1) and fails the cleanup_e2e_resources shard. Mirror the existing getStacks() guard by also skipping on InvalidClientTokenId. Backport of the fix already on main (#3304) to release-api-plugin-stable. e2e-cleanup only, not customer-facing.
svidgen
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Opt-in regions (
ap-east-1,eu-south-1) are not enabled on the e2e test accounts. WhengetAmplifyAppscalls the Amplify client in those regions, it throwsInvalidClientTokenId, which currently propagates out of the cleanup script →process.exit(1)→ fails thecleanup_e2e_resourcesshard.This mirrors the existing guard in
getStacks()by also skipping onInvalidClientTokenId(in addition to the existingUnrecognizedClientException), logging and continuing rather than failing.This is a backport of the fix already on
main(#3304) to therelease-api-plugin-stablebranch.Scope