Our T2.small EC2 instance continues to do its usual 10-15% usage but the CPU credit balance has gone up to maximum and stayed there:
I have contacted AWS support but they just send me a link explaining how credit balance works. I know that this isn't technically a "problem" for us, but this is our important Production Server and it makes me a bit nervous. Has anyone had an issue like this with an EC2 instance?
I am the reluctant "sysadmin" of a medium-sized cooking blog that runs on a t2.small EC2 instance, and utilizes WordPress on the LAMP stack. Despite being a fairly embarrasingly bad "sysadmin" it actually runs really reliably and efficiently despite shipping a LOT of traffic. I've done everything I can but every now and then (about once a year) someone manages to hammer it with a DDOS type attack. What tends to happen is that the apache server dies and anyone request anything from the website gets a HTTP timeout. Restarting the httpd service immediately fixes the problem.
What I'm thinking of doing is scheduling a CRON job to call the website every 5ish minutes and if it finds that it gets a timeout more than twice, it restarts the httpd service and sends me an email. Now, this is NOT one of those "I can't set up my apache server properly so I'll restart it every hour" solutions. The apache is tweaked and runs beautifully when it isn't being hacked. And I've put in as much firewall anti-hacking best practice as I possibly can. My rationale is basically "hackers and crazies are always finding new ways to hammer me and when they do I'd rather have 10 minutes of outage and an email than potentially hours of downtime (if I'm asleep or away)". The question is, is this a good solution or is there a better, more sysadminny way to do this using some existing technology?
NOTE: When I say the apache server dies it actually looks fine when you run top -U apache. WHat it does is writes about 10
(12)Cannot allocate memory: AH00159: fork: Unable to fork new process
to the error_log and just doesn't do anything at all until restarted.
Hi have created a record set for the domain:
lazycatthemes.com
on Route 53 (domain was purchased through route 53) and gave it the 4 NS settings that Route 53 told me to configure:
ns-368.awsdns-46.com
ns-1963.awsdns-53.co.uk
ns-848.awsdns-42.net
ns-1332.awsdns-38.org
When I check it on any one of those DNS servers using the nslookup tool it works:
nslookup lazycatthemes.com ns-1963.awsdns-53.co.uk
Server: UnKnown
Address: 205.251.199.171
Name: lazycatthemes.com
Address: 54.154.51.71
but this doesn't propagate. I've waited 36 hours and I still get this:
nslookup lazycatthemes.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find lazycatthemes.com: Server failed
I'm not sure what to do next?