1 Answer
- Newest
- Most votes
- Most comments
4
You mentioned that you have already set the default timeout value to 3600 seconds, but you could try increasing it further to see if that helps. You can do this by going to your Elastic Beanstalk environment and navigating to the Configuration > Software tab, where you can increase the "Instance connection timeout" value. It's possible that the deployment is running out of resources on your free tier account. So please check your resource usage. If the issue persists, you may need to optimize your application to reduce its size and improve performance during deployment.
Relevant content
- asked 2 years ago
- asked 7 months ago
- asked a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago