61–70 of 75 posts
I opened a service ticket. My ec2 instances have somehow been running for over 950 hours in one month. I can go back and see my instances run for 744 hours (what i'd expect in a month) in previous months. Amazon invented more hours than actually exist in a month for billing purposes. Bezos is a genius! I should have thought of that!
I opened a service ticket. My ec2 instances have somehow been running for over 950 hours in one month. I can go back and see my instances run for 744 hours (what i'd expect in a month) in previous months. Amazon invented more hours than actually exist in a month for billing purposes. Bezos is a genius! I should have thought of that!
EDIT: deleted
Oh no somebody ran the cron job twice. Call me, aws. I can help. I know cron jobs.
Whenever I hear news like this, part of me feels bad for all the programmers working very long hours to fix the problem. You can be sure that a lot of pagers started to go off as soon as the reports of billing issues started to come in.
I wonder if AWS is prepping for a pricing hike but someone was trigger happy with the big red button :D
Whenever I hear news like this, part of me feels bad for all the programmers working very long hours to fix the problem. You can be sure that a lot of pagers started to go off as soon as the reports of billing issues started to come in.
Whenever I hear news like this, part of me feels bad for all the programmers working very long hours to fix the problem. You can be sure that a lot of pagers started to go off as soon as the reports of billing issues started to come in.
Earlier quoted context omitted.
I've never used AWS so perhaps I'm mistaken, but api gateways normally provide extra functionality on top of just proxying the request. You can still set up a server listening on port 80 or 443 with a public IP and make requests to it without being charged per request.
You can, and if you want to use Lambdas, you can also route to them from ALBs, which has a bit confusing of a pricing model for comparison, but has no per-request cost.
Earlier quoted context omitted.
There is something called the "cost explorer" which I can't use yet, because apparently it takes 24 hours to set up (?), and it's not even clear that it will include my historical activity when it's ready... Cost Explorer itself also charges per use. I'm not kidding: https://aws.amazon.com/aws-cost-management/pricing/
The API charges per use, but not the cost explorer dashboard itself.
I'm highly suspicious toward Amazon behaviour now. This kind or news only flurish the idea that Amazon has taken it's first steps toward being a total a company.