- Newest
- Most votes
- Most comments
Hi TergelE,
Please try the below steps it will be helpful to you to Resolve your Issue.
Update AWS Credentials: If you are using the AWS Command Line Interface (CLI), make sure your credentials are up to date. Run aws configure and enter the new credentials if needed. If you are using temporary credentials (like from an IAM role or AWS Single Sign-On), make sure to refresh them. For AWS SSO, you might need to run aws sso login again.
Clear Cache: Clear any stored data that might be causing issues. This can be browser cache, local storage, or other cached app data related to your old project.
Check Amplify Configuration: Make sure your Amplify project settings are correct. Go to the Amplify Console and review the build settings to ensure everything is set up properly.
Update Environment Variables: If you are using environment variables for AWS credentials in your build settings, make sure they are correct and up to date.
Check Permissions: Ensure the IAM roles and policies associated with your Amplify project have the correct permissions and are not expired.
Check Logs: Go to the AWS Management Console and check the CloudWatch logs for specific error messages related to your deployments.
Validate Domain and SSL: In the Amplify Console, check that your custom domain and SSL certificate are correctly configured.
Re-deploy the App: If nothing else works, try deleting the Amplify app and creating it again from scratch. This ensures no old settings or tokens are carried over.
Relevant content
- asked 4 months ago
- asked a year ago
- asked 3 months ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 months ago
- How do I resolve the IAM credentials error "The security token included in the request isn’t valid"?AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 3 years ago