You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using generatePresignedUrl(), if temporary credentials are used the resulting URL does not have the required X-Amz-Security-Token parameter (the Session Token from generated credentials). AWS will report that the URL has a missing or invalid token. Note that a session token is not required when using normal key and secret credentials and the generatePresignedUrl() works as expected.
If the token is uuencoded and is manually appended to the generated URL then the AWS server accepts it but complains that the signature is not correct.
My guess is that the token needs to be given as part of the credentials for setting up the client. This would then produce the correct URL with token and signature (here's a Java version I have in another project I worked on):
When using generatePresignedUrl(), if temporary credentials are used the resulting URL does not have the required X-Amz-Security-Token parameter (the Session Token from generated credentials). AWS will report that the URL has a missing or invalid token. Note that a session token is not required when using normal key and secret credentials and the generatePresignedUrl() works as expected.
If the token is uuencoded and is manually appended to the generated URL then the AWS server accepts it but complains that the signature is not correct.
My guess is that the token needs to be given as part of the credentials for setting up the client. This would then produce the correct URL with token and signature (here's a Java version I have in another project I worked on):
The text was updated successfully, but these errors were encountered: