Maintenance: E2E tests credentials time out after 1h

[phipag]

Summary

After adding more E2E tests via PR #2378, we see them failing with a credential expiration error message. Example: http://github.com/aws-powertools/powertools-lambda-java/actions/runs/22578090517/job/65423856282

Error:    ParametersE2ET.setup:65 » Sts The security token included in the request is expired (Service: Sts, Status Code: 403, Request ID: 47ebf533-6153-4e71-a7f4-424ba103fde1) (SDK Attempt Count: 1)

The reason for this is that the temporary fetched credentials have a validity of one hour. We should fix this problem.

Why is this needed?

We need reliable E2E tests to understand potential regressions in code changes.

Which area does this relate to?

Automation

Solution

There are two potential solutions that need to be investigated:

1. Increase duration of credentials
2. Understand if we can parallelize the E2E tests to reduce the overall runtime duration (preferred)

Acknowledgment

• This request meets Powertools for AWS Lambda (Java) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, TypeScript

[phipag]

Created PR #2398

[phipag]

Merged.