r/aws • • Jan 23 '20

security AWS engineer uploads customer keys, passwords to GitHub

24 Upvotes

https://www.theregister.co.uk/2020/01/23/aws_engineer_customer_credentials_github/

IAM secret key/secrets were available for five hours before being taken down.

As a precaution we’ve rotated all our IAM keys , no word yet from AWS


r/aws • • Feb 03 '24

discussion Example of why AWS is needlessly complicated

2 Upvotes

So, after like 80+ hours trying to work with AWS setups, and googling "why is AWS so needlessly complicated" to find solidarity with other people who have had similar issues, I figured I'd type out an example to explain why this sentiment is common.

Step 1: spin up an Elastic Beanstalk instance for a backend environment, PHP 8.2 on AmazonLinux 2023.

AWS: fail! Your instance type for whatever reason doesn't work for this availability zone.

Me: Okay...wish ya'll would have said as much beforehand. I'll edit this and fix that.

AWS: Lollll...nope, you can't edit it. Gotta delete and start from scratch!

Me: Ugh. Seems needless. Okay, will do.

[10 tries and 10 similar errors (can't spin up single instance, because it throws a load balancer error, can't do simple logging, needs enhanced, so on, so on)

AWS: Okay, you finally figured out the combination of steps and you have a working instance.

Step 2: Now, I need to modify this instance. Need to install redis and install some image libraries...EPEL, etc..

AWS: LOL! Nope.

Me: What do you mean, nope? Your platform specifically said that Amazon Linux 2023 is the best version to use with AWS hardware and is the most capable...

AWS: It is the best.

Me: But...you don't have any libraries to install pretty generic stuff.

AWS: Correct.

Me: How does that make sens...okay, never mind. I'll install from source...phpize, configure, make and make install....

AWS: Libraries installed.

Step 3: Whew. I'm out of breath. Now let's add an elastic file system.

AWS: Done. But it will delete on reboot. We're edgy like that.

Me: Okay...not even going to say that was unexpected, so I'll follow the link buried in the footer of the EFS guide and make it persistent with fstab....

Step 4: Deploy code

Me: Okay, let's deploy some of the latest code.

AWS Code Pipleline: answer me these questions 50, or errors I shall give thee!

Me: I beg. Here are answers. (After try 30).

AWS Code Pipeline: I begrudgingly grant thee success to the next stage!

Step 5: Moving on. Let's set up a redis cluster.

AWS: Done.

Me: That was easy. Too suspiciously easy. Let's load up the app...

App: FATAL ERROR. REDIS KEY MISMATCH.

Me: W.T.F?

[3 hours of Googling later: can't use cluster mode for redis because it gives apps a sad!]

Me: GFDI.

AWS: hahahahahaha

Me: I'll figure out how to get this into single mode one way or the other!

AWS: nanana - good luck finding out the button combination to make that happen!

[45 minutes of googling later].

Me: Found it. Okay, redis spun up. Good lord. Is this setup run by Chuckey?

Step 6: Make this change persistent so the elastic beanstalk instance reflects the changes in the future.

Me: Okay. Finally! We're done. Let's create an AMI off of this, and deploy it on beanstalk...

Beanstalk: this AMI gives me a tummy ache. Tummy ache bad!

Me: Please don't have a tummy ache Mr. Beanstalk, I just need you to load up the AMI.

Beanstalk: grumble grumble.

Me: Okay, let's deploy the latest code change.

AWS: Code deployed.

Beanstalk: grumble grumble

EC2: No code change reflected.

Me: Wait? What? Why? Why don't you work?

AWS:....

Me, to AWS: AWS. I made this shiny new AMI for you to load up this configuration I spent all this time working on. Why is it giving Beanstalk a tummy ache?

AWS: LOLLLLLLLLLLLLLLLLL. You can't make an AMI off of the beanstalk EC2 instance, silly! Did you HONESTLY think you could do something so ridiculously dumb? [Sinister clown music plays]

Me: But...But...I configured the instance like the guides and I just want the configuration to save!

AWS: LOOLLLLOLLLOLLLLLL!!!!! Silly rabbit, common sense is for losers! What you should have done after spending all that time creating a beanstalk instance, is to DO IT ALL AGAIN in an EC2 instance, then figure out exactly how to create a custom AMI based on that original elastic beanstalk AMI that you then modify, and then clone as its own AMI, to pipe back into beanstalk as the deployment AMI!

Me: Wait. What? WTF? WHAT IS WRONG YOU WITH YOU?

AWS: [Sinister clown music plays]. If you want to travel from Boston to Washington D.C., you don't want to just fly south, do you? No! You want to fly NORTH, over the pole, and then take a rocket to Mars, bounce off the planet, to have a colonoscopy in Jupiter, before passing through hell's nine circles to arrive at D.C. It's better this way. [Clown music intensifies]

Me: I beg!

AWS: Beg harder!

Step 7: Embrace the suck, and beg harder.

Me: FUCK IT. FINE! How do I create this instance?

AWS: run this command:

aws elasticbeanstalk describe-platform-version --region us-east-2

\ --platform-arn "arn:aws:elasticbeanstalk:us-east-2 ::platform/Tomcat 8.5 with Java 8 running on 64bit Amazon Linux /3.1.6 " \ --query PlatformDescription.CustomAmiList

Me: Wait, I'm not running Tomcat or Java. What do I enter here in order to get this new AMI I need to create from the original AMI so I can make the new AMI to deploy over the default AMI to get a working AMI, well, working?

AWS: it's all in that guide. That tells you nothing. Haha!

Me: Okay...I guess I'm looking for PHP something. I'll start trial and error.

AWS: need to install console libraries!

Me: FFS.

Step 8: Embrace the suck, and install console libraries.

Me: ok...let's just get this over with.

AWS: need key.

Me: How...where, do I do that?

[Google: set up IAM bullshit. Devote another hour. Do not pass go or collect $200].

Each entry thereafter:

AWS, in Edward Nerdy's voice from Jurassic Park: Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word! Nuh uh uh, you didn't say the magic word!

After stackoverflowing and serverfaulting and googling and screaming:

Magic word found. AMI discovered:

aws elasticbeanstalk describe-platform-version --region us-east-1 --platform-arn "arn:aws:elasticbeanstalk:us-east-1::platform/PHP 8.2 running on 64bit Amazon Linux 2023/4.0.4"

I got the AMI ID. Finally. FINALLY.

AWS: silence.

Me: Okay, AWS, now can we please just let an AMI be created so I can go to bed and get a working setup?

AWS: Sure! Sure... 😈

——

I will update this post with the next trial put in front of me. I think I need to pipe environment variables into an EC2 instance and make changes to the nginx configuration. To do this, AWS seems to suggest that I need to fight a tiger that Danny DeVito is sitting on top of with a rocket launcher in his hand, while at the same time translating technical blueprints written in Japanese into ancient Latin, with Sanskrit-influenced inflections written in perfect cursive. I also many need to go back to Jupiter to fetch a magic bean. I'm unsure if I'm supposed to plant it or eat it, and if the latter, whether it gives me super powers or will kill me on the spot. The documentation seems to suggest both - I just have to put the flim flam in the flizzle flazzle and just move the popspot into the skiperiedoodledaddledo, multiply by the blopitybloop and whopdidapperpaddle the appliflubber, and that should get it working.

The journey continues.


r/aws • • Jan 27 '25

article S3 last lowered its price 8 years ago

0 Upvotes

S3 last lowered its price 8 years ago.

Since then, HDD cost have lowered by at least 60%. (visualization)

That’s an annual decrease of 13%.

Imagine your S3 bill went down by that amount every year.

Here is a brief history of S3 storage cost, in us-east-2:

• 2010: $150/TB
• 2011: $125/TB
• 2012: $110/TB
• 2014: $31/TB
• 2016: $23/TB • Today: the same

Soon enough it’ll be a decade of fixed pricing.

Some Rebuttals

This isn't an Apples to Apples Comparison 🍎

That's right - it's not.

S3 doesn’t just buy 1 TB of hard disk and sell it to you. It stores a few copies of the data (Erasure Coding) and keeps extra, free storage capacity.

So you would expect to pay at least a few times the cost of an HDD, since 1 TB stored in S3 probably takes up 3+ TB of underlying disk capacity.

The Software is Priceless! 🤩

That's the sense I get from some people who argue this to me, lol.

But it's true - there is a premium to be paid on the fact that S3 is infinitely scalable, never down, incredibly highly-durable (11 9s). I acknowledge that.

Power Costs Have Gone Up ⚡️

This is partly true but not a justification imo. In the last 25 years, Virginia has registered a 2.6% annual electricity price increase. In 1998 its rate was 7.51 cents/kWh and today it's 14.34 cents/kWh.

Assuming 24/7 activity, a hard drives uses around 220 watt-hours per day. That's ~6710 per month and 80,520 per year. 80.52 kWh at the high 14.34 cents/kWh is $11.54 a year. Assume there are three 22TB drives for each 22TB you store, that's just $35 a year. Your annual bill for those 22TB would be close to $6217, so electricity is barely 0.5% of that.

It could go up 2x (unheard of) and still be a rounding error.

There's no Incentive! 🥲

I think this is the right answer.

There's no incentive for AWS to lower the prices, so from a business point of view - it would be an awful decision to do so.


r/aws • • Dec 05 '25

article Is this subreddit just hating on re:Invent 2025, or are we missing the full picture?

19 Upvotes

I have been reading the reactions on r/aws, and a lot of people feel the same frustration. They want AWS to fix outages in us-east-1, reduce complexity, lower latency, and strengthen the core services that run real production systems. They see the AI announcements and feel that the priorities are shifting in the wrong direction.

I understand that view. Reliability is the foundation. Without it, everything else is noise. At the same time, I spent the week at re:Invent 2025, and what I saw was not superficial AI hype. There were concrete advancements that strengthen the platform in practical ways.

Nova 2 is not a marketing stunt. It is a model family built for structured reasoning, multimodal workloads, and deeper integration with the AWS environment. It gives enterprises a way to move from isolated AI experiments to systems that actually work inside their own controls and data boundaries.

FSx and S3 improvements were not small updates either. They simplify how large datasets are read, processed, and shared across analytics, ML, simulation, and HPC workloads. High-performance file semantics on S3 remove entire layers of duplication and refactoring. For many organizations, this reduces friction more than any new model would.

The pattern I saw was simple. AI on its own does not solve cloud problems. But AI integrated into the existing AWS backbone gives teams a way to move faster without losing predictability or governance. That is a meaningful shift.

I also agree with the community on one point. The foundation still matters. Stability, clarity, cost visibility, performance, and regional resilience are the things that earn trust. Innovation only works when the base is strong. The feedback on this subreddit is part of that accountability loop.

Both views can be true. AWS can and should invest in cloud fundamentals. And at the same time, the new capabilities announced at re:Invent can meaningfully improve how enterprises modernize systems, process data, and deploy AI in production


r/aws • • Sep 04 '22

discussion Database used by AWS

0 Upvotes

Which database(s) does Amazon use for storing all the Services that its customer use ? And how would the databases be structured ?

Like storing IAM Configuration, S3 configs, EC2 configs, etc.

From the JSON Structure, I believe it would be NoSQL, but then since it is highly relational, it would seem unwise to use a NoSQL.

P.S - I am not asking about the databases that are available to the customers of AWS.


r/aws • • Nov 17 '24

discussion I think amazon will buy anthropic

0 Upvotes

Amazon hasn’t launched any LLM like chatgpt, gemini, midjourney.

They are heavily investing in anthropic, and pushing anthropic to use AWS custom chip. After AI hotness will settle down and everything seems fine( with business perspective) they will buy anthropic.

Anthropic is very independent company, amazon is waiting for right time.

What you guys think?


r/aws • • Aug 10 '24

discussion aws charged me USD 8,600 with an unauthorized marketplace subscription to Claude 3 Opus (Amazon Bedrock Edition) (sold by Anthropic, PBC)

0 Upvotes

Hi everyone,

I'm reaching out to see if anyone has had a similar experience or can offer some advice. Recently, I discovered that my AWS account was compromised, leading to unauthorized Marketplace subscriptions and some pretty hefty charges that I didn't authorize or even know about.

I haven’t logged into my AWS account for a long time, so you can imagine my shock when I saw these charges. I immediately took steps to cancel the unauthorized subscriptions and secure my account, but I'm still facing some challenges.

Here’s where it gets frustrating: despite contacting AWS support multiple times, I feel like I'm not getting enough help to actually resolve this issue. The support team’s responses have been slow and haven't fully addressed my concerns, especially around getting a refund for these unauthorized charges.

Here's a quick rundown of what’s happened:

  1. Unauthorized Activity: Someone accessed my account and subscribed to several services I never wanted or needed, resulting in huge charges.

  2. Unexpected Billing: I’m now stuck with a bill for services I didn’t use, and I’m finding it really difficult to get it resolved.

  3. Security Concerns: Even though I’ve tried to secure my account, I’m worried it might still be vulnerable.

  4. Lack of Support: Despite reaching out to the support team, I haven’t received the help I need to fix this.

I’m at a point where I’m considering escalating this further, maybe even contacting higher-ups at AWS, because this is just too much to handle alone. Has anyone else been through something similar? How did you manage to get it resolved? Any advice or shared experiences would be really appreciated.

Thanks in advance for any help or suggestions!

Here's how you can edit your Reddit post to include the new information:

Edit: Unfortunately, AWS has informed me that they won't be able to process my refund until the current billing cycle has been completed, which typically happens on the 3rd of the following month. They mentioned that they will resolve this case for now and follow up once the billing cycle is completed to confirm the refund.

This response is quite frustrating and unacceptable to me. It's disappointing that AWS won't take action on the unauthorized charges until the billing cycle ends, leaving me in limbo until then. I'll keep everyone updated on how this unfolds, but for now, it seems I'll have to wait for weeks before this issue is resolved.


r/aws • • Apr 18 '25

technical question Scared of Creating a chatbot

0 Upvotes

Hi! I’ve been offered by my company a promotion if I’m able to deploy a chatbot on the company’s landing website for funneling clients. I’m a senior IA Engineer but I’m completely new to AWS technology. Although I have done my research, I’m really scared about two things on aws: billing going out of boundaries and security breaches. Could I get some guidance?

Stack:

Amazon Lex V2: Conversational interface (NLU/NLP). Communicates with Lambda through Lex code hooks. Access secured via IAM service roles. AWS Lambda: Stateless compute layer for intent fulfillment, validations, and backend integrations. Each function uses scoped IAM roles and encrypted environment variables. Amazon DynamoDB: database for storing session data and user context. Amazon API Gateway (optional if external web/app integration is needed): Public entry point for client-side interaction with Lambda or Lex.


r/aws • • Feb 21 '20

article After being in the consultant biz for 3 years, here are our top 5 least favorite AWS services

Thumbnail
medium.com
0 Upvotes

r/aws • • Mar 18 '26

discussion WTF is AWS' strategy right now?

0 Upvotes

AWS has everything needed to own the coming era of personal software.

The infra. The AI services. The developer tools. Companies like Lovable and Supabase are literally building the application layer *on top of AWS* — and printing.

Yet here's Amazon, largely content to rent GPU compute and inference endpoints while others capture the relationship with the next generation of builders.

Amplify hinted at this vision years ago and was never taken seriously internally. Q Developer exists but nobody's rushing to use it over Cursor or Claude Code. It's starting to feel like they are operating like IBM at the dawn of the rise of the personal computer.

For most of the 20th century, media was built for the masses. A newspaper, a TV channel, a billboard — one message, millions of recipients. The economics demanded it. You couldn't justify producing something for an audience of one. Then social media atomised consumption entirely. Your feed isn't anyone else's feed. The content finds you, shaped around your behaviour, your interests, your moment.

Software is about to go through the same shift. Right now, applications are broadcast — Salesforce is built for every sales team, Xero for every accountant, Jira for every engineering org. One product, millions of users, averaging out everyone's needs. The era of personal software is the feed moment: where the tool is built for you, shaped around how your business actually works, not how some product manager in San Francisco imagined it might. The difference is that instead of an algorithm curating content, an AI agent is building the application itself.

We are already seeing businesses building like this, and I've been waiting for the world shattering product announcement on the par with Lambda to bridge AWS into the next technology era. And I'm waiting... and waiting...


r/aws • • Oct 20 '25

discussion Is this a cyber attack?

7 Upvotes

I have no experience in AWS lol, can someone explain in basic terms why dynamodb could go down/why it’s effecting sm other services? Or do we just have no idea currently Also how long would you guess this will last?


r/aws • • Nov 05 '25

discussion CloudFront restriction and AWS Support team decides to keep silent for almost a month.

1 Upvotes

We are a startup business and AWS is our first choice when thinking about cloud infra hosting services.

But everything turn down when CloudFront and ALB restriction is set out of nowhere. We can't do anything without CloudFront, and have to move our code to EC2. Without ECS, S3, our CI/CD is a nightmare when we have to manage it.

But the worst thing is, our support case has been ignored for almost a month, since 20 Oct till today. Possible is that because our Support Plan is still on Free?

Does anyone having this issue or have a way to liftoff this restriction? Our team is planning to choose another cloud service providers as an alternative as it's heavily affected our business.

Update: I think by sharing my incident, we may have more idea about the case.
My business account is registered with a valid business email domain (not from common one like gmail, outlook...). I already added my credit card and fill in everything about my company's profile.

However, when I create a new CloudFront distribution, both with CLI and Console, I got this error message:

Your account must be verified before you can add new CloudFront resources. To verify your account, please contact AWS Support (https://console.aws.amazon.com/support/home#/) and include this error message.


r/aws • • Jul 28 '19

discussion How I use the good parts of AWS while filtering out all the distracting hype

Thumbnail
twitter.com
0 Upvotes

r/aws • • Jan 24 '25

discussion Do all EC2 instances now effectively have a $4/mo hidden fee?

29 Upvotes

A public IP now costs $3.65/mo. This isn't included in the EC2 price; it's not even shown in the AWS pricing calculator when estimating EC2 costs. It's hidden under VPC pricing.

That's a fairly substantial increase for small instance sizes. A t4g.small with the savings plan at around $9/mo will actually cost $13/mo — almost a 50% increase.

And there's no real way around it for most situations, especially small projects where that cost makes a difference.

Let's say you decide to use CloudFront and put your EC2 instance on a private subnet, no internet gateway or public IP. You can use EC2 Instance Connect Endpoint to SSH into your box, but good luck installing packages or pulling Docker images. You can't even connect to ECR without using AWS PrivateLink, which costs a bit over $7/mo.

And don't even think about a NAT Gateway; you'd think NAT would be cheaper than a dedicated IP, but AWS charges you $32.85/mo for what a crappy home router does.

The smallest DO droplet costs as much as an IP, and that's with 10 GB of storage (and an IP).

Is there something I'm missing here? Or is this just a new hidden fee and we have to accept it? It's already bad enough that you can't create an EC2 instance anymore without an EBS volume (another fee), but at least that's reasonably cheap. I know AWS has always been fees left and right, but it's starting to get egregious. You can't even have simple hotlink protection if you choose CloudFront without paying $6/mo, something that's free everywhere else.


Edit: Wow, this is really controversial, it seems.


Edit 2: I need to clarify a bit, because I think a lot of people reading this won't realize what's it's like for a new AWS user, or for someone like myself who's setting up AWS for the first time in 7-8 years.

When I first posted this, I didn't even realize IPv6 public IP was possible. It's not made clear in the console, either when launching an EC2 instance or when creating a VPC. IPv4 is the default for both, too. I think anyone would be forgiven for not knowing there's another way and just eating the automatic $4/mo cost.

And that's really the crux of the problem. It's not an opt-in extra charge like most AWS services. It's opt-out, and you have to know that you can even opt-out at all. And, like I said, for small, single-node applications, that $4/mo fee is a fairly significant % increase.

But the fact that some of you are supporting such hidden fees is, frankly, shameful. I think I'm done with reddit for a while. Y'all suck. Those who suggested v6 and shared your experience, thank you.


r/aws • • Jan 02 '26

discussion CleanCloud v0.4.0: Now 10x faster with parallel scanning for AWS hygiene checks

0 Upvotes

Hey r/aws

I’ve just released CleanCloud v0.4.0, an open-source CLI focused on cloud hygiene for SRE teams — identifying review-only candidates like orphaned or inactive storage and log resources (AWS & Azure).

This release focuses on speed, safety, and trust rather than adding new rules.

What’s new in v0.4.0

  • 🚀 Much faster scans – cloud API calls now run in parallel

  • 🧪 Safety integration tests – explicit coverage to prevent unsafe recommendations

  • 🩺 Improved doctor output – clearer permission and environment diagnostics

  • 💬 Post-scan feedback prompt – early-stage project, feedback genuinely welcome

  • 🏢 Repo moved to cleancloud-io org for long-term stewardship

Design principles

  • Read-only, agentless

  • No automatic cleanup

  • Multiple conservative signals per recommendation

  • Confidence levels instead of hard deletes

  • No telemetry or phone-home behavior

If you’re an SRE / platform engineer dealing with cloud sprawl but don’t want “auto-delete” tools running wild, I’d love your feedback.

GitHub: https://github.com/cleancloud-io/cleancloud

PYPI: https://pypi.org/project/cleancloud/

Docs + install instructions in the repo.

Happy to answer questions or hear what rules you’d want next.


r/aws • • Sep 04 '26

discussion AWS SES production access rejected for... no reason

0 Upvotes

Every time we launch a product on AWS, SES turns out to be the blocker.

We're launching a new SaaS application and need SES exclusively for low-volume transactional email: account creation, login OTPs, password resets, etc. No marketing email, no purchased lists, no bulk outreach.

We requested an initial limit of just 1,000 emails/day. We're experienced AWS users and already actively use SES across multiple customer AWS accounts, with no history of email abuse.

AWS initially asked about our sending practices, which we answered in detail. They then asked why we couldn't use other AWS accounts where SES limits had previously been increased. We explained that this is a new company, product, and organization, and this account was intentionally created as its dedicated production environment.

Today, AWS rejected the request without providing any specific reason:

> "While we are not able to share the specific criteria used in our assessment..."

The frustrating part is that SES sandbox access is now blocking the launch of the entire application, despite the extremely limited and purely transactional use case.

Has anyone successfully appealed a rejection like this? Is there a better escalation path or someone at AWS who can review the request manually?

There surely must be a way for AWS to prevent and mitigate email abuse without blindly blocking new product launches.


r/aws • • Jul 17 '26

general aws Aws bill of 40k and i hardly use AWS and generally get 0.0 every month

0 Upvotes

Help me please, am panicking and not sure what to do. yes i have account , dont see anything as being used.. raised a ticket but it says 24 hrs not sure who to talk. based out of AU


r/aws • • Feb 27 '25

security Is it safe to upload profile picture of user in s3 bucket?

0 Upvotes

Hey guys, I'm working in a small organization as an intern and we are encountering a problem with saving user profile pictures. So previously we saved the user profile picture in the MongoDB database using base64, compressed, and reduced from the front-end. but now we want to shift it to the S3. I didn't have any idea about the S3 that much. so I googled it read some articles and got the idea also asked AI for the process. For now, I learned that first, we have to upload the image on s3 then generate the link of that image, and save it into the MongoDB (since I have to use that link for other functionality) after that while fetching we can just call the URL form the MongoDB and it will retrieve from the s3.

the real concern here is security. I know that there are two modes private and public in s3. but don't know what it works like. if I send the link of the user profile on the front end using that URL can anyone access my all-user image or not? if yes how I can make it safe? any help will be very appreciated


r/aws • • Mar 14 '24

discussion AWS IPv4 pricing: Azure is 20% cheaper, GCP ipv4 is 50% cheaper

0 Upvotes

My recent frustration (and rant) in discovering* AWS's eye watering charges for IPv4 has led me to migrate my EC2 instances to Azure, not doing so meant i either pay the full price, stick ipv6 or i bring in other services which i have no interest in. upon investigation and from several posters here, it seems AWS don't even support ipv6 in all their services, which i think is hypocritical, if true.

since i am using Azure for Auth n/z , i decided to start using it for compute too, currently experimenting with GCP.

Azure's IPv4 pricing is overall cheaper, here. GCP is even cheaper if you use spot here

while this might not matter to everyone, it really depends on your use case, we depend heavily on dynamic** compute allocation.

* Sending reminders about the upcoming charges is a crap argument, this is a matter of principle, why should i pay more when a viable competitor is charging less?

** i have no love for ipv4 , but there are many other ways to accelerate its demise without losing customers, short sighted at best.


r/aws • • Jan 18 '26

technical resource I built a CLI tool to find "zombie" AWS resources (stopped instances, unused volumes) because I didn't want to check manually anymore.

0 Upvotes

Hello everyone, as a Cloud Architect, I used to do the same repetitive tasks in the AWS Console. This is why I created this CLI, initially to solve a pretty specific necessity related to cost explorer:

  • Basically I like to check the current month cost behavior and compare it to the previous month but the same period. For example, of today is 15th, I compare the first 15 days of this month with the first 15 days of last month. This is the initiall problem I solved using this CLI

  • After this I wanted to expand its functionalities and a waste functionality. Currently this checks many of the checks by aws-trusted-advisor but without the need of getting a business support in AWS

t’s basically a free, local alternative to some "Trusted Advisor" checks.

Tech Stack: Go, AWS SDK v2

I’d love to hear what other "waste checks" you think I should add.

Repo: https://github.com/elC0mpa/aws-doctor

Thank you guys!!!


r/aws • • Apr 28 '25

technical resource AWS Podcasts with American Accents

3 Upvotes

Hi.

Part of keeping myself updated with changes at AWS is by listening to AWS podcasts. But I’ve noticed that the official one available at Spotify feature hosts with accents from New Zealand, Australia, or the UK. While I absolutely appreciate the diverse range of voices, I personally find it a bit challenging to follow at times.

I was wondering if anyone knows of any official AWS podcasts with American accents? I’m just looking for something that might be a bit easier for me to follow, and I’d love any recommendations.

Thanks in advance!


r/aws • • Oct 03 '23

discussion Amazon SageMaker -- What an absolute ripoff!

0 Upvotes

If you're new to AWS, run away now! Basically, to use their services, you'll need a PhD in Internet Security or at least 10 years experience in IT to set it up. Then, they have a never ending cascade of help pages. You'll read one and think you can follow it, then it'll send you to one more. It just doesn't stop.

Amazon knows this. So with SageMaker, they lure you in with a push one-button solution. If you push it, you have to remember to turn everything off before exiting. And if you create an "end point", you have to go into a 10 tab side menu entitled "Inferences" to turn it off???? Not intuitive, not user-friendly. $300 dollars later I've learned my lesson. Don't fucking use this service!

It's like you forgot to turn the lights off at you house and you have to pay $20/ per day. Then the utility company came and hid all the light switches to turn it off at your neighbor's house. You didn't realize you were getting charged until your credit card bill showed up at the end of the month.

Take that $600 you're going to get charged and go put it towards a new computer. That's the lesson. Scalability my ass. (my luck this forum is probably moderated by the AWS sales department)


r/aws • • Apr 20 '18

A security flaw I discovered recently in IAM policies

0 Upvotes

I recently came across a particular AWS Managed policy in IAM which could potentially let any role that has been granted that policy to gain admin/root privileges in AWS. And the policy I am talking about is not among those that start with the name IAM. I have reported this to AWS security team, and they said they are working with teams on updating the policy such that it would no longer be possible. But in the mean while until they come up with the fix, there is possibility of someone taking advantage of this. I do not have a way to alert AWS users of this in a secure way, so I am just leaving this much information here.


r/aws • • Mar 22 '26

technical resource Local AWS - a lightweight AWS service emulator

Thumbnail
github.com
0 Upvotes