-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the JWT Token refresh also updates the service-specific objects, such as S3? #6
Comments
Thank you Vladimir! Yes the idea is aws-amplify takes care of service-specific objects. Developer access S3 or DDB through aws-amplify, don't need to hold those service-specific object directly. Thanks, |
Great! So when the JWT tokens are refreshed, the service-specific objects are also recreated, correct? |
@vbudilov Yes you are right. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Hi all, great product!
With the current workflow (non-awsamplify), once a user signs in and I retrieve the access tokens for him, I can then create service-specific objects such as S3 and DDB. After an hour I would need to re-generate the objects since the tokens have expired and everything needs to be refreshed. Does aws-amplify take care of re-instantiating the service-specific objects or do the devs need to take care of this themselves?
Thanks,
Vladimir Budilov
The text was updated successfully, but these errors were encountered: