Aws cognito presigned url getting error as token expiration
I developing an android mobile app in which it is used to upload the image and save in s3. When I am uploading the photo I am generating a pre-signed URL for that image and saving the URL in my database so whenever the application loads the saved URL gets called from my database and display the image.B ut in my case, the pre-signed URL gets an error stating that token expired. I need to access the image from s3 using the URL which was generated while uploading

add a comment |
I developing an android mobile app in which it is used to upload the image and save in s3. When I am uploading the photo I am generating a pre-signed URL for that image and saving the URL in my database so whenever the application loads the saved URL gets called from my database and display the image.B ut in my case, the pre-signed URL gets an error stating that token expired. I need to access the image from s3 using the URL which was generated while uploading

add a comment |
I developing an android mobile app in which it is used to upload the image and save in s3. When I am uploading the photo I am generating a pre-signed URL for that image and saving the URL in my database so whenever the application loads the saved URL gets called from my database and display the image.B ut in my case, the pre-signed URL gets an error stating that token expired. I need to access the image from s3 using the URL which was generated while uploading

I developing an android mobile app in which it is used to upload the image and save in s3. When I am uploading the photo I am generating a pre-signed URL for that image and saving the URL in my database so whenever the application loads the saved URL gets called from my database and display the image.B ut in my case, the pre-signed URL gets an error stating that token expired. I need to access the image from s3 using the URL which was generated while uploading


edited Jan 2 at 7:45


Jaymin
1,70721028
1,70721028
asked Jan 2 at 7:09
SriSri
95
95
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
For security purposes, pre-signed URLs have an expiry time associated with them that you can specify when you create the pre-signed URL. For the expiry time, the minimum value you can set is 1, and the maximum is 604800 (seven days). (See https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html)
While you haven't mentioned what the expiry time is set for your pre-signed URLs, in general the approach of generating the URL, storing it in your database and using it going forward in the app is bound to fail. You should consider either computing the URL on the fly ( by storing the location details of the file) or optimize it by tracking when the URL has expired (you could have a expiry-time field in your database) and updating the URL as needed
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54002533%2faws-cognito-presigned-url-getting-error-as-token-expiration%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
For security purposes, pre-signed URLs have an expiry time associated with them that you can specify when you create the pre-signed URL. For the expiry time, the minimum value you can set is 1, and the maximum is 604800 (seven days). (See https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html)
While you haven't mentioned what the expiry time is set for your pre-signed URLs, in general the approach of generating the URL, storing it in your database and using it going forward in the app is bound to fail. You should consider either computing the URL on the fly ( by storing the location details of the file) or optimize it by tracking when the URL has expired (you could have a expiry-time field in your database) and updating the URL as needed
add a comment |
For security purposes, pre-signed URLs have an expiry time associated with them that you can specify when you create the pre-signed URL. For the expiry time, the minimum value you can set is 1, and the maximum is 604800 (seven days). (See https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html)
While you haven't mentioned what the expiry time is set for your pre-signed URLs, in general the approach of generating the URL, storing it in your database and using it going forward in the app is bound to fail. You should consider either computing the URL on the fly ( by storing the location details of the file) or optimize it by tracking when the URL has expired (you could have a expiry-time field in your database) and updating the URL as needed
add a comment |
For security purposes, pre-signed URLs have an expiry time associated with them that you can specify when you create the pre-signed URL. For the expiry time, the minimum value you can set is 1, and the maximum is 604800 (seven days). (See https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html)
While you haven't mentioned what the expiry time is set for your pre-signed URLs, in general the approach of generating the URL, storing it in your database and using it going forward in the app is bound to fail. You should consider either computing the URL on the fly ( by storing the location details of the file) or optimize it by tracking when the URL has expired (you could have a expiry-time field in your database) and updating the URL as needed
For security purposes, pre-signed URLs have an expiry time associated with them that you can specify when you create the pre-signed URL. For the expiry time, the minimum value you can set is 1, and the maximum is 604800 (seven days). (See https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html)
While you haven't mentioned what the expiry time is set for your pre-signed URLs, in general the approach of generating the URL, storing it in your database and using it going forward in the app is bound to fail. You should consider either computing the URL on the fly ( by storing the location details of the file) or optimize it by tracking when the URL has expired (you could have a expiry-time field in your database) and updating the URL as needed
answered Jan 23 at 15:14
BommasBommas
18815
18815
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54002533%2faws-cognito-presigned-url-getting-error-as-token-expiration%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown