1 Answer
- Newest
- Most votes
- Most comments
1
Hello Kat!
Let's see if we can get this sorted:
- Check the Amplify Console: First stop is the AWS Amplify Console in your AWS account. It's the best place to find any error messages or hints on what might have gone wrong.
- Review Your Build Settings: Double-check your amplify.yml file or any build settings. It's often in the details where things can go awry.
- Permissions Check: Make sure your IAM role has all the necessary permissions. A small oversight here can cause big headaches.
- Local Logs Insight: If you started deploying from your local machine, your local logs might hold some valuable clues.
- Session Identifier: Keep your Session Identifier (372ea0b0-1237-415b-a8c2-c25e25653d8b) close. It's really useful, especially if you need to reach out to AWS Support.
- Common Issues: Keep an eye out for common pitfalls like environment variable issues or build dependency problems.
Best of luck, and hope this helps!
I'm here if you need anything else!
answered 3 months ago
Relevant content
- asked 3 years ago
- asked a year ago
- asked 9 months ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Is there a way I can use the session identifier in aws to find exact issue? How can I use the session Identifier? Also, deployment works first time and getting issue in recent deployment times due to some reason!