- Newest
- Most votes
- Most comments
There are a few potential reasons why your Lightsail Bitnami LAMP instance might be crashing regularly at 0600 EST:
-
Scheduled tasks: It's possible that there are automated tasks or cron jobs running at that time which are causing resource spikes or conflicts.
-
Automatic updates: Some systems perform automatic updates at set times, which could potentially cause issues if there are conflicts or resource constraints.
-
External traffic patterns: Even if you don't expect heavy use, there might be periodic external access attempts or scans occurring at that time.
-
Resource exhaustion: Despite having 4GB RAM and 2 CPUs, your instance might be hitting resource limits due to accumulated processes or memory leaks.
To troubleshoot, you can:
- Check system logs for errors or unusual activity around the crash time
- Monitor CPU, memory, and disk usage leading up to the crash
- Review any scheduled tasks or cron jobs
- Investigate running processes and services
Regarding publicly flagged IP addresses accessing your instance, AWS doesn't automatically block these because:
- It could interfere with legitimate traffic
- IP reputation can change over time
- Different customers have different security needs
To enhance security, you can:
- Use AWS WAF (Web Application Firewall) for more granular traffic control
- Configure your instance's firewall rules to limit access
- Implement additional security measures at the application level
If the issue persists, consider taking a snapshot before the usual crash time and analyzing it, or reaching out to AWS support for more in-depth assistance.
Sources
lightsail instance down everyday. | AWS re:Post
Something strange with lightsail instance at 2AM | AWS re:Post
AWS Lightsail and EC2 Instances Going Down Daily — WP Rocket Conflict | AWS re:Post
Relevant content
- asked 6 years ago
- asked 3 years ago