Yep, an m1.Small will handle this place unless we suddenly get 250 users on, all posting simultaneously. Arguably you could boost to an m1.Medium at that point, as memory would likely be the bottleneck. Or set up an ELB and spin-up more m1.Smalls on demand behind it. Probably not something to worry about unless the current instance starts running at 100% CPU for extended periods.
The instance will have some ephemeral storage associated with it - I can't remember what the default spin-up sizes are as my estate all runs off custom-sized EBS volumes that replace the image storage as soon as it starts. The trick to remember about ephemeral storage is that if you terminate the instance (or Amazon do, as can happen if the hardware node fails) you lose it. I doubt I need to remind you to take regular snapshots.
The storage I have is 10gb in EBS, that's persistent isn't it? I thought it was Just took a snapshot in case it's not
As for scaling I was thinking of having a much around with using nginx to serve the site; it looks like it's much lighter on RAM and processor load than Apache
The email notifications don't appear to be coming through.
I'm seeing threads on Bleatings that I know I'm subscribed to with new posts, but I'm not getting email notifications for them. I checked the forum settings to be sure and notifications are switched on. It's not erroneous junk mail filtering on my end, as I've checked that. The timing entirely coincides with the server move (so I'm presuming it's probably related).
(If it's just that you haven't got around to setting it up properly yet, that's fine. No rush. Really, I'm just checking that it's not one of those stupid over-zealous ISP blacklisting things. If it's not your end nor my end, then we can begin to suspect someone else might be being stupid with their traffic management en route instead.)
"Words ought to be a little wild - for they are assaults of thought on the unthinking."
- John Maynard Keynes