Thread 106586136

what are some subtle ways to drive up the costs of an AWS account without doing something glaringly obvious like spinning up hundreds of compute instances

Get a student account.

My bad, you said "drive up" costs kek >>106586138.
I have no idea, but I'm sure there is some kafkaesque way to do it. AWS is a fucking labyrinth of nightmares

>>106586136 (OP)
Your best bet is causing traffic. Take a few nodes that already have high traffic and make it more. Only outgoing traffic get's billed.

Just keep using it. AWS will raise the bill on their own, they don't need help

Good morning SIR!

>>106586136 (OP)
add a bunch of db replicas or increase compute instance sizes maybe, increase lambda memory, etc.. there may be some strange pattern you could "accidentally" introduce like a cyclical sns/sqs system that will just create a cost by simply existing. Not sure how if it needs to be a hidden change though

That's a crime.

>>106586136 (OP)
Just be inefficient. I scan all paper documents at work at 400dpi to waste storage space. No one knows what it does so they leave the setting alone.

Just make slightly bad choices no one can fault you for . Make deployments slightly too big. Use the second best algorithms for things. Run that test one more time just for good measure . Make the "mistakes" small and make sure it's not obvious.

>>106589183
>>106587504
>>106586159
>>106586136 (OP)
>wonders why Indians are taking their jobs

dirtbags itt.

>>106586136 (OP)
Lots of DNS requests if they use route 53. I used to use them and only paid like $5 a year for my domain I only use for email, but I got scared after reading about people who got $80k bills because of DNS DDoS attacks. Then I just started using my registrar's DNS hosting instead.

>>106590477
I am on my way out and I dont give a fuck I just want these faggota to eat shit and fail

>>106590619
There is no way aws charges you when someone looks up your dns lmao. Next thing your gonna tell me every time I exhale in an aws datacenter someone is paying for it

>>106586136 (OP)
Egress

>>106587504
>there may be some strange pattern you could "accidentally" introduce like a cyclical sns/sqs system that will just create a cost by simply existing
yeah draw tons of sqs and lambda in an atchitectural diagram

If you want to make a VM slow, just have a fork bomb program run. You can adjust it to your liking and bring a system to its knees. Or you can just have it slowly load the system over time. Eventually you run out of processes and logging in becomes impossible and the machine will have to be rebooted from the management console.

There are many ways to fork bomb, you can get creative with it.

elasticcache

>>106586159
route53 health check rapes your server with 10 request per second starting and you can go up to 100rps
The only thing in AWS that's completely free of charge

>>106587504
>lambda
This. Just lambda can rake up 100k bill

>>106590955
Egress isnt as bad as cloudflare shills make it out to be.

>>106590863
>electricity charges for HVAC equipment
technically, yes.

>>106589070
A victimless one.

>>106586136 (OP)
If the codebase manages scaling you can put some small logic bugs or race conditions that periodically prevent a cluster from scaling down during periods of low use. The ECS bill can get out of hand fast.

>>106586136 (OP)
start migrating everything to amazon services. it adds up and locks you in. start storing things on s3--that's the easiest way to lock someone into aws. if you need help, ask your account rep for a recommended way to do something and watch him recommend 20 different services.

>>106590863
They do though

>>106586136 (OP)
Inter-region traffic
Sneaky lambdas
Public bucket and fetch from outside the org

>>106590477
Not currently in tech but my boss only hires Indians.

>>106586136 (OP)
shit ton of outbound internet traffic