I understand that you want to achieve persistence with Amplify Cognito session. As per the shared Amplify.configure(), there are few configuration issues such as the region is being passed into the incorrect location, and by default, Amplify uses the local storage already, so there is no need to define that.
We need additional information to troubleshoot this issue, and some information are account-specific, which cannot be shared publicly. If you have AWS support plan, kindly open a support case with AWS using the following link.
In support case, please include following additional information:
- What does lack of "persistence" mean here? Is the user receiving tokens? If yes, do they see the tokens stored within the local storage of the browser?
- How long are the tokens set to live for, when configuring the Auth resource?
- Do you see any errors, after setting set window.LOG_LEVEL = 'DEBUG';, as described here, around the time the user signs in, as well as when the tokens are expected to be refreshed.
- How are you defining the localStorage object?
- How is the user signing into the application? Is it the Authenticator module, or the SDK methods? What function is used from the Amplify SDK?
- What is the version of SDK?
Aws Ampify Cognito Session Persistanceasked 2 months ago
Custom auth with adminInitiateAuthAccepted Answerasked 8 months ago
Combining Basic Auth & Cognito Auth in ESAccepted Answerasked 2 years ago
access Cognito User Pool secured AppSync app via alternate auth mechanismasked 4 years ago
AWS ALB Cognito JWT/OIDC authenticationasked 8 months ago
Sync Session Token Expired in iOS AWS cognito SDKasked 5 months ago
Application Load Balancer and Cognito cookie session time (SessionTimeout) can't be adjusted - logout problemasked 15 days ago
Logout from an ALB session that is authenticated by Cognitoasked 3 years ago
Cognito - Azure AD - Amplify - flow of the SSO auth from application perspectiveAccepted Answerasked 2 years ago