Fix: Refresh AWS Token During Lambda Java Performance Test #450
Conversation
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
Problem: The Lambda Java performance test can take longer than one hour, but the AWS token is only valid for one hour. If the token expires, the performance test will fail. Additionally, Terraform will fail to delete the AWS resources it created. When this happens, subsequent performance tests are blocked because the AWS resources cannot be manually deleted (attempts to delete them in the AWS Console result in "Access Denied," even with admin permissions). Fix: In the performance test workflow, we explicitly renew the AWS token twice: Before running the performance tests. Before tearing down the Terraform-created resources.
liustve
approved these changes
Sep 18, 2025
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.
Problem:
The Lambda Java performance test can take longer than one hour, but the AWS token is only valid for one hour. If the token expires, the performance test will fail. Additionally, Terraform will fail to delete the AWS resources it created. When this happens, subsequent performance tests are blocked because the AWS resources cannot be manually deleted (attempts to delete them in the AWS Console result in "Access Denied," even with admin permissions).
Fix:
In the performance test workflow, we explicitly renew the AWS token twice:
Before running the performance tests.
Before tearing down the Terraform-created resources.