Firstly, sorry for the long topic header, and I’m not sure if this call for help is outside the scope of the Bubble forum… but here goes…
Situation: I’ve managed to establish an API connection between my Bubble app and my AWS S3 bucket with AWS SigV4 authorization. I generate the SigV4 authorization header using Python on my local laptop. When Python compiles the SigV4 auth header, it takes in the current time as an input variable as part of compilation (as required by SigV4).
The API initialization is successful and the GET API call to my AWS S3 bucket/dataset executes as expected.
Problem/Complication: After a short period of time (15 mins?) the SigV4 auth header is stale/no longer accepted by AWS; the API call no longer executes as expected and fails. This is expected behaviour for security reasons on the AWS side. A new SigV4 auth header needs to be generated, with an input variable being the current (future) time.
Is there a way to dynamically generate a new SigV4 auth header to enable the API call to AWS S3? [And/Or] Is there the ability to extend the time limit for when a SigV4 auth header is valid?
Appreciate any pointers/suggestions, thanks.