fix(parameters): refresh AppConfig session token after 24 hrs

[dreamorosi]

Description of your changes

As discussed in the linked issue, the AppConfig provider in the Parameters utility stores a session token returned by the service that should be used for the subsequent call. By default the token has a duration of up to 24hrs and if the provider attempts to retrieve a configuration using an expired token it'll result in a bad request exception.

For most Lambda-based workloads this is not an issue since the execution environment is likely to have been recycled before the token has the chance to expire. For those customers who use provisioned concurrency or who decide to use the Parameters utility outside of Lambda (i.e. containers or others) this is an issue.

This PR improves the session token handling by storing the expiration timestamp together with the token. The timestamp is then checked by the AppConfigProvider before making a call to the service, and if expired a new session token is requested.

With this change customers using the Parameters utility in long lived execution environments should see decreased bad requests exception.

Related issues, RFCs

Issue number: #1798

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[am29d]

Nice 🛳️