Using Postman API results in Bubble API and getting error

The error you're encountering is related to a common issue with AWS API requests known as "RequestExpired". This occurs when there's a mismatch between the timestamp on the request and the server time.

In your specific case, the error message indicates that the signature has expired. This typically happens when:

1. There's a time synchronization issue between your client (in this case, Bubble) and AWS servers.
2. The request is taking too long to reach the AWS service.
3. The client's clock is not accurately set.

The error message suggests that the request timestamp (20241021T214628Z) is now considered earlier than the current time on the AWS server. AWS allows for a 15-minute window of difference between the timestamp on the request and the current time.

To resolve this issue:

1. Ensure that the clock on the machine running your Bubble application is accurately synchronized with a reliable time server.
2. Check if there are any network latency issues that might be causing delays in request transmission.
3. Verify that your AWS credentials are current and haven't expired.
4. If you're using temporary credentials (like those from AWS STS), make sure they haven't expired.

If the issue persists after checking these points, you may need to contact Bubble support to investigate if there's a systemic time synchronization issue on their end.

Remember that while Postman might work correctly, Bubble could have a different environment setup, leading to this discrepancy. It's a good idea to compare the exact request headers and timestamps between your successful Postman request and the failing Bubble request to identify any differences.
Sources
Common Errors - Amazon Chime SDK
Common Errors - Amazon Chime