billing I owe $7 trillion, what now?
I almost got a heart attack
r/aws • u/alasdairvfr • Oct 20 '25
Anyone know yet root cause of today's shenanigans?
r/aws • u/AssumeNeutralTone • Oct 20 '25
r/aws • u/StealthNet • Oct 20 '25
It all started when I was trying to by something from Mercado Livre, one of the biggest portals here in Brazil. Couldn´t load account specifics, cart or change other profile settings, like adding a credit card.
So I decided to buy it from Amazon, same behavior. Went to Brazil's Down Detector and it seems to me that all services that rely on AWS are failing.
Went to the the US Down Detector site and I am seeing what seems to be the same cascading failure right now.
Any1 facing similar problems?
r/aws • u/doodlebytes • Jun 04 '21
I have the console bookmarked for my daily work but for some reason this morning I was on Google and just searched AWS Login instead. Spotted an interesting result which had me curious; a sponsored result at the very top with a clone of the AWS Console login page.
Hopefully wouldn’t catch more seasoned people but thought I'd share in case some poor person gave away their root credentials in such a scam.
Has been reported to Google.
EDIT: and now reported to AWS, who then asked me to report to Cloudflare.
EDIT2: Cloudflare have taken it down
r/aws • u/doodlebytes • Jul 13 '21
r/aws • u/ZGeekie • Jul 03 '25
Design tool Figma has revealed in its initial public offering filing that it is spending a massive $300,000 on cloud computing services daily.
Source: https://www.datacenterdynamics.com/en/news/design-platform-figma-spends-300000-on-aws-daily/
r/aws • u/chocothrower • Jul 01 '23
r/aws • u/MrPurple2020 • Sep 19 '20
Acloudguru is scamming people and going back on their promise.
When Acloudguru took over LinuxAcademy they assured us that we will have access to both catalog of courses. This was a lie.
I paid for Linuxacademy yearly subscription to access their AWS Architect Pro and Devops Pro courses.
When I logged in a few days ago I found out that ACG removed 50 hour Aws Architect Pro Linuxacademy course by Adrian Cantrill and replaced it with their ACG inferior 14 hour course by Scott Pelter
ACG removed 32 hour Devops Pro course and replaced it with their garbage 6 hour course. In actuality it’s only 4 hours!! Because they sneakily marked each section quiz as 4 hours long and added it to course total.
This is clearly not what I and other Linuxacademy members paid for. We would like the content that we paid for. Ryan Kroonenburg should be ashamed of himself for scamming people.
I opened a ticket and was told by ACG rep that if I didn’t watch any video from Linuxacademy AWS Pro courses before then I won’t have access to them. Which is completely the opposite of what we were told when ACG took over.
They are slowly replacing all LinuxAcademy courses with shorter, vomit inducing ACG products.
Also they sneakily inflate course length by making their quizzes as 4 hour long each. For example there are 6 quiz for AWS Devops Pro exam. So 6 x 4 is 24 hours. The total length of AWS Devops pro course advertised by ACG is 27 hours. So there is only 3 hours of content. No really, go check!
Linux academy had such great courses and content. Acloudguru is completely destroying all of its credibility and scamming people on top of it. I advise not to get any subscription with them.
Rather support people like Stephen Maarek, Adrian Cantrill, Eissa Sharif, Neal Davis etc.
r/aws • u/Averroiis • Aug 02 '25
Today I woke up and checked the blog of one of the open source developers I follow and learn from. Saw that he posted about AWS deleting his 10 year account and all his data without warning over a verification issue.
Reading through his experience (20 days of support runaround, agents who couldn't answer basic questions, getting his account terminated on his birthday) honestly left me feeling disgusted with AWS.
This guy contributed to open source projects, had proper backups, paid his bills for a decade. And they just nuked everything because of some third party payment confusion they refused to resolve properly.
The irony is that he's the same developer who once told me to use AWS with Terraform instead of trying to fix networking manually. The same provider he recommended and advocated for just killed his entire digital life.
Can AWS explain this? How does a company just delete 10 years of someones work and then gaslight them for three weeks about it?
r/aws • u/AWSSupport • Oct 18 '18
Hello /r/aws,
AWS Support has officially landed! 🚀
To better support the thriving community here, we have created an official AWS Support account! We will specialize in Account & Billing questions and do our best to resolve your issue, address your feedback, or point you toward resources that can help.
Please bear with us as we get this program off the ground, and let us know how we’re doing and how we can improve your experience with us. Shout out to moderator u/ckilborn for helping us get started!
Thanks for building on AWS!
r/aws • u/killpowa • Jul 17 '26


As per title, today I received a bunch of billing alerts in my email because I went over my max threshold of 100 usd.
AWS says I owe them about 2.5 billion dollars so far and it's only the 17th of the month. I have only one s3 bucket that hasn't been touched since 2023 and is not public, and I am not even using ecr at all, I have no registry on any region that I am aware of. I tried opening a support ticket but nothing so far.
What should I do? Is there any way to escalate this urgently?
r/aws • u/otterley • May 13 '24
r/aws
•
u/FredWeitendorf
•
Oct 28 '24
No dude you can't fix someone's permission issues by finding their user group and attaching a permission you fucking IDIOT you have to modify the policies in the permission! No bro you can't modify that policy it's an AWS-managed policy you gormless MORON, you need to create a new policy with the specific permission you need as an action and attach it as a permission policy to the group! Wait oh my god what are you even doing you freaking NUMBSKULL did you think you could solve your permissions issue by going to the permissions product and granting them a permission?
My guy it's not the user who needs the permission it's their role! Oh my IDIOTIC friend you didn't seriously think you could add a single permission to that role did you? It's an AWS-managed role from your IAM identity center setup which is an entirely separate config and product so nothing you did so far even worked you absolute BUFFOON. Oh my god, chief, did I just catch you trying to grant the permission in IAM identity center by finding the user or their group and attaching a policy or permission there you complete DONKEY?
How was it not completely obvious that you need to find the user's IAM identity center group and inspect its AWS accounts to find the permissions sets applied to the account where your user lacked permissions, you hopeless NITWIT? Was it not clear that you merely needed to find the IAM identity center multi-account permissions set associated with the user's IAM identity center group and the account in question, and attach an inline policy there you drithering DUNCE?
Because the concepts involved are so intuitively named, you should have no problem understanding the distinctions between policies, actions, permissions, IAM users, IAM groups, IAM policies, IAM roles, AWS accounts, IAM Identity center users, IAM Identity center groups, and IAM identity center permissions sets. Sane people recognize this.
r/aws • u/jeffbarr • Oct 05 '26
My colleagues in the AWS Network Product Lab in Cupertino are tasked with inventing the most advanced networking technology in the world, while also inventing new ways to stress and break it.
With AWS operations in 240 countries and territories, the network includes about 20 million miles of fiber optic cable. We have doubled our total network capacity in the past three years and plan to double it again by 2027.
To learn more about this team and their work, read Inside the AWS lab that makes everything you do online feel effortless.
r/aws • u/Illustrious_Soil_519 • Jul 17 '25
Just got a call from a coworker this AM and he got the email that he was let go. I had been hearing they were doing this now with remote employees..and he IS remote. If you’re not tied to an office they’re cutting ties had been a rumor for a few weeks and it’s proving to be true. Has anyone else heard similar with their team? Sucks.
r/aws • u/AssumeNeutralTone • Oct 23 '25
r/aws • u/CeralEnt • Dec 07 '21
As always their Service Health Dashboard says nothing is wrong.
I'm getting 500/502 errors from two different computers(in different geographical locations), completely different AWS accounts.
Anyone else experiencing issues?
ETA 11:37 AM ET: SHD has been updated:
8:22 AM PST We are investigating increased error rates for the AWS Management Console.
8:26 AM PST We are experiencing API and console issues in the US-EAST-1 Region. We have identified root cause and we are actively working towards recovery. This issue is affecting the global console landing page, which is also hosted in US-EAST-1. Customers may be able to access region-specific consoles going to https://console.aws.amazon.com/. So, to access the US-WEST-2 console, try https://us-west-2.console.aws.amazon.com/
ETA: 11:56 AM ET: SHD has an EC2 update and Amazon Connect update:
8:49 AM PST We are experiencing elevated error rates for EC2 APIs in the US-EAST-1 region. We have identified root cause and we are actively working towards recovery.
8:53 AM PST We are experiencing degraded Contact handling by agents in the US-EAST-1 Region.
Lots more errors coming up, so I'm just going to link to the SHD instead of copying the updates.
r/aws
•
u/2minutestreaming
•
Dec 05 '24
S3 announced two major features this past re:Invent.
S3 Tables
S3 Metadata
Let’s dive into it.
This is first-class Apache Iceberg support in S3.
You use the S3 API, and behind the scenes it stores your data into Parquet files under the Iceberg table format. That’s it.
It’s an S3 Bucket type, of which there were only 2 previously:
S3 General Purpose Bucket - the usual, replicated S3 buckets we are all used to
S3 Directory Buckets - these are single-zone buckets (non-replicated).
They also have a hierarchical structure (file-system directory-like) as opposed to the usual flat structure we’re used to.
They were released alongside the Single Zone Express low-latency storage class in 2023
new: S3 Tables (2024)
AWS is clearly trending toward releasing more specialized bucket types.
The “managed Iceberg service” acts a lot like an Iceberg catalog:
single source of truth for metadata
automated table maintenance via:
compaction - combines small table objects into larger ones
snapshot management - first expires, then later deletes old table snapshots
unreferenced file removal - deletes stale objects that are orphaned
table-level RBAC via AWS’ existing IAM policies
single source of truth and place of enforcement for security (access controls, etc)
While these sound somewhat basic, they are all very useful.
AWS is quoting massive performance advantages:
3x faster query performance
10x more transactions per second (tps)
This is quoted in comparison to you rolling out Iceberg tables in S3 yourself.
I haven’t tested this personally, but it sounds possible if the underlying hardware is optimized for it.
If true, this gives AWS a very structural advantage that’s impossible to beat - so vendors will be forced to build on top of it.
Out of the box, it works with open source Apache Spark.
And with proprietary AWS services (Athena, Redshift, EMR, etc.) via a few-clicks AWS Glue integration.
There is this very nice demo from Roy Hasson on LinkedIn that goes through the process of working with S3 Tables through Spark. It basically integrates directly with Spark so that you run `CREATE TABLE` in the system of choice, and an underlying S3 Tables bucket gets created under the hood.
The pricing is quite complex, as usual. You roughly have 4 costs:
Storage Costs - these are 15% higher than Standard S3.
They’re also in 3 tiers (first 50TB, next 450TB, over 500TB each month)
S3 Standard: $0.023 / $0.022 / $0.021 per GiB
S3 Tables: $0.0265 / $0.0253 / $0.0242 per GiB
PUT and GET request costs - the same $0.005 per 1000 PUT and $0.0004 per 1000 GET
Monitoring - a necessary cost for tables, $0.025 per 1000 objects a month.
this is the same as S3 Intelligent Tiering’s Archive Access monitoring cost
Compaction - a completely new Tables-only cost, charged at both GiB-processed and object count 💵
$0.004 per 1000 objects processed
$0.05 per GiB processed 🚨
Here’s how I estimate the cost would look like:
For 1 TB of data:
annual cost - $370/yr;
first month cost - $78 (one time)
annualized average monthly cost - $30.8/m
For comparison, 1 TiB in S3 Standard would cost you $21.5-$23.5 a month. So this ends up around 37% more expensive.
Compaction can be the “hidden” cost here. In Iceberg you can compact for four reasons:
bin-packing: combining smaller files into larger files.
this allows query engines to read larger data ranges with fewer requests (less overhead) → higher read throughput
this seems to be what AWS is doing in this first release. They just dropped a new blog post explaining the performance benefits.
merge-on-read compaction: merging the delete files generated from merge-on-reads with data files
sort data in new ways: you can rewrite data with new sort orders better suited for certain writes/updates
cluster the data: compact and sort via z-order sorting to better optimize for distinct query patterns
My understanding is that S3 Tables currently only supports the bin-packing compaction, and that’s what you’ll be charged on.
This is a one-time compaction1. Iceberg has a target file size (defaults to 512MiB). The compaction process looks for files in a partition that are either too small or large and attemps to rewrite them in the target size. Once done, that file shouldn’t be compacted again. So we can easily calculate the assumed costs.
If you ingest 1 TB of new data every month, you’ll be paying a one-time fee of $51.2 to compact it (1024 * 0.05).
The per-object compaction cost is tricky to estimate. It depends on your write patterns. Let’s assume you write 100 MiB files - that’d be ~10.5k objects. $0.042 to process those. Even if you write relatively-small 10 MiB files - it’d be just $0.42. Insignificant.
Storing that 1 TB data will cost you $25-27 each month.
Post-compaction, if each object is then 512 MiB (the default size), you’d have 2048 objects. The monitoring cost would be around $0.0512 a month. Pre-compaction, it’d be $0.2625 a month.
The second feature out of the box is a simpler one. Automatic metadata management.
S3 Metadata is this simple feature you can enable on any S3 bucket.
Once enabled, S3 will automatically store and manage metadata for that bucket in an S3 Table (i.e, the new Iceberg thing)
That Iceberg table is called a metadata table and it’s read-only. S3 Metadata takes care of keeping it up to date, in “near real time”.
The metadata that gets stored is roughly split into two categories:
user-defined: basically any arbitrary key-value pairs you assign
product SKU, item ID, hash, etc.
system-defined: all the boring but useful stuff
object size, last modified date, encryption algorithm
The cost for the feature is somewhat simple:
$0.00045 per 1000 updates
this is almost the same as regular GET costs. Very cheap.
they quote it as $0.45 per 1 million updates, but that’s confusing.
the S3 Tables Cost we covered above
since the metadata will get stored in a regular S3 Table, you’ll be paying for that too. Presumably the data won’t be large, so this won’t be significant.
A big problem in the data lake space is the lake turning into a swamp.
Data Swamp: a data lake that’s not being used (and perhaps nobody knows what’s in there)
To an unexperienced person, it sounds trivial. How come you don’t know what’s in the lake?
But imagine I give you 1000 Petabytes of data. How do you begin to classify, categorize and organize everything? (hint: not easily)
Organizations usually resort to building their own metadata systems. They can be a pain to build and support.
With S3 Metadata, the vision is most probably to have metadata management as easy as “set this key-value pair on your clients writing the data”.
It then automatically into an Iceberg table and is kept up to date automatically as you delete/update/add new tags/etc.
Since it’s Iceberg, that means you can leverage all the powerful modern query engines to analyze, visualize and generally process the metadata of your data lake’s content. ⭐️
Sounds promising. Especially at the low cost point!
All this is offered behind a fully managed AWS-grade first-class service?
I don’t see how all lakehouse providers in the space aren’t panicking.
Sure, their business won’t go to zero - but this must be a very real threat for their future revenue expectations.
People don’t realize the advantage cloud providers have in selling managed services, even if their product is inferior.
leverages the cloud provider’s massive sales teams
first-class integration
ease of use (just click a button and deploy)
no overhead in signing new contracts, vetting the vendor’s compliance standards, etc. (enterprise b2b deals normally take years)
no need to do complex networking setups (VPC peering, PrivateLink) just to avoid the egregious network costs
I saw this first hand at Confluent, trying to win over AWS’ MSK.
The difference here?
S3 is a much, MUCH more heavily-invested and better polished product…
And the total addressable market (TAM) is much larger.
I made this funny visualization as part of the social media posts on the subject matter - “AWS is deploying a warship in the Open Table Formats war”
What we’re seeing is a small incremental step in an obvious age-old business strategy: move up the stack.
What began as the commoditization of storage with S3’s rise in the last decade+, is now slowly beginning to eat into the lakehouse stack.
This was originally posted in my Substack newsletter. There I also cover additional detail like whether Iceberg won the table format wars, what an Iceberg catalog is, where the lock-in into the "open" ecosystem may come from and whether there is any neutral vendors left in the open table format space.
What do you think?
r/aws • u/[deleted] • Sep 17 '24
I accepted an offer at AWS last week, and Amazon’s 3 day WFO week was a major factor while eliminating my other offers. I also decided to rent an apartment a bit farther from the office due to less travel days. Today, I read that Amazon employees will return to office 5 days a week starting January! Did I just get scammed for a short term?
r/aws • u/jonathantn • Oct 20 '25
Well, looks like we have a dumpster fire on DynamoDB in us-east-1 again.