Amazon Lightsail traffic limits

The answer to your question is a very definitive "It Depends". :)

It depends on what apps are you are running, how much activity each user engages in, what kind of traffic you are serving, etc.

Lightsail instances aren't intended for high performance activity ... mostly lower traffic sites with the occasional burst of activity.

Its a static website, but will have a few emdedded youtube videos. and some forms that the user would fill, the form data will be saved in a database.

Sounds like you're well within the scope of Lightsail.

The external videos won't count against your traffic.

I would suggest going with a slightly higher tier instance and see how it goes. If performance turns out to be a problem, you can always snapshot your instance, create a larger instance from the snapshot, and reassign the static IP.

david

Ok that's good to hear,
I should have put it like 100,000 + visitors per day. So here's my plan you

2x USD10 instances of Lightsail
1x Managed Database (Don't know if this resides on a separate light sail instance)
1x Load Balancer

I hope this doesn't sound overkill.
Are you aware how many instances can a load balancer take, that way I can keep adding light sail intances to it once the limit is about to reach.
My only issue now is bandwidth, more users would cross the bandwidth limit pretty fast, and then I'll be in the pay as you go range, which is pretty pricey.

Amaze4Ever wrote:
I hope this doesn't sound overkill.

IMO, your plan is a bit overkill, at least for a new site.

My philosophy has always to use the KISS method (Keep It Simple Stupid) (no offense intended).

Start with a single $10 instance + basic database and see how it performs.

If the performance isn't sufficient, then consider using a load balancer.

If you KNOW what kind of data transfer you're going to experience (using metrics from a current implementation), then maybe it's not overkill.

Are you aware how many instances can a load balancer take, that way I can keep adding light sail intances to it once the limit is about to reach.

I've never actually used the load balancer feature. I'm not sure if there is a limit.

My only issue now is bandwidth, more users would cross the bandwidth limit pretty fast, and then I'll be in the pay as you go range, which is pretty pricey.

Keep in mind that the limitation is on data transfer ... not users. If you design your site well, you can limit the amount of traffic that is served directly from your instance. Use content distribution networks (CDN), host your static content on S3 and use cloudfront to distribute the load, etc.

Thank you for the wonderful answers.
I agree with you with the KISS principle.

However I was thinking if I just start with 1 server and the system is live, how to I scale it without down time then?
I mean lets say if with a single server a threshold is reached where I now need to scale up, then I would probably need to add another instance and load sharing. This would result in downtime wouldn't it.
Or is there a way to increase resources on the fly without affecting downtime?

I would have liked the system to autoscale on load however am not familiar with AWS technology as yet to identify the components needed to get this done.

Thanks again!

Is your traffic estimates based on experience or what you hope the traffic to be?

If this is a new site, then I would start small and ramp up as needed.

If you're migrating a site, where you know the traffic, then set it up the way you are describing.