Why my AWS Lightsail instance for WordPress site using Amazon stack keeps getting stopped
byu/DigitalSplendid inWordPress

---

When I first set up WordPress on AWS, I believed the Amazon Lightsail WordPress blueprint would be the easiest and most reliable option.

It wasn’t.

After struggling with downtime and repeated reboots, I revisited Bitnami WordPress stack—despite its painful migration process—and surprisingly found it more stable.

This post is a practical breakdown of:

• Why Bitnami feels painful during migration
• Why Lightsail Blueprint can be unreliable in practice
• Which one you should actually choose

👉 Inspired by:
Why Bitnami WordPress Stack Makes Migration Painful (Hard Lessons) (reference conceptually aligned article)

---

⚙️ Understanding the Two Approaches

1. Bitnami WordPress Stack

Bitnami provides a pre-configured stack with:

• Apache / Nginx
• PHP
• MySQL/MariaDB
• WordPress

Everything is tightly integrated under /opt/bitnami.

👉 Official guide:
Bitnami WordPress Documentation

👍 Pros

• Production-ready configuration
• Better default security & permissions
• Consistent environment across providers

👎 Cons

• Migration is complex
• Non-standard file paths
• Requires SSH familiarity

---

2. Amazon Lightsail WordPress Blueprint

Lightsail offers a one-click WordPress install with:

• Fixed pricing (₹ equivalent of $5–$20/month tiers)
• Simple UI
• Preinstalled WordPress

👉 Setup guide:
Deploy WordPress on AWS Lightsail (Step-by-Step)

👍 Pros

• Beginner-friendly
• Fast setup (2–3 minutes)
• Predictable pricing

👎 Cons

• Limited control
• Burstable CPU limitations
• Stability issues under load

---

⚠️ The Real Problem: Lightsail Blueprint Downtime

From practical experience (and widely reported cases), Lightsail WordPress instances can:

• Become unresponsive suddenly
• Require manual reboot or even hard shutdown
• Fail under moderate CPU usage

Example real-world issues:

• Users report needing daily reboots to restore site functionality
• Instances becoming completely unresponsive, requiring shutdown from console
• Performance drops due to CPU burst credit exhaustion

💡 Why This Happens

Lightsail uses a burstable CPU model:

• You get “credits” for CPU usage
• Once exhausted → performance throttles drastically
• Result → site slowdown or crash

👉 This is fine for:

• Small blogs
• Low traffic

👉 But problematic for:

• Dynamic WordPress sites
• Plugins-heavy setups
• Traffic spikes

---

🤯 Bitnami Migration Pain (Yes, It’s Real)

Bitnami is frustrating when you try to:

• Move hosting providers
• Change server structure
• Extract WordPress manually

Why it’s painful:

• Files are inside /opt/bitnami (non-standard)
• Permissions are tightly controlled
• Services are managed via custom scripts

But here’s the truth:

👉 That complexity is also why it’s stable.

---

⚖️ Bitnami vs Lightsail: Honest Comparison

Feature	Bitnami Stack	Lightsail Blueprint
Setup	Moderate	Very easy
Migration	Hard	Easy
Stability	High	Medium / inconsistent
Performance	Predictable	Depends on CPU credits
Control	Full	Limited
Downtime risk	Low	Higher

---

🧠 Key Insight (From Experience)

👉 Lightsail Blueprint is easy to start, hard to scale reliably
👉 Bitnami is hard to migrate, but stable once running

This creates a paradox:

The more “beginner-friendly” option may cost you more time in maintenance later.

---

🛠️ When to Choose What

✅ Choose Bitnami if:

• You want long-term stability
• You can handle SSH and configs
• You are building:
  • Business site
  • SaaS MVP
  • Blog with growth potential

---

⚠️ Choose Lightsail Blueprint if:

• You are just experimenting
• You want quick deployment
• Downtime is acceptable

---

🔧 Best Hybrid Approach (Recommended)

Here’s what works best in practice:

1. Start with Lightsail (for learning)
2. Move to:
   • Bitnami on EC2 OR
   • Custom LAMP stack
3. Add:
   • CloudWatch monitoring
   • Auto-restart scripts
   • CDN (Cloudflare)

---

🚀 Final Verdict

• Bitnami = Pain upfront, peace later
• Lightsail Blueprint = Easy upfront, pain later

If you’ve already experienced:

• Random downtime
• Frequent reboots
• Performance drops

Then your conclusion is valid:

👉 Bitnami is still the better choice for serious projects.

---

✍️ Closing Thought

In cloud hosting, simplicity is often an illusion.

The real goal is not:

“How fast can I launch?”

But:

“How long can it run without breaking?”

---