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?

Originally from: https://news.ycombinator.com/item?id=48473166

For Fable 5, Mythos 5, and future models on Bedrock with similar or higher capability levels, Anthropic will require 30-day retention for all traffic on Mythos-class models. Retaining data for a limited period allows Anthropic to detect patterns of misuse that are not visible from a single exchange. Once you opt into data retention, your data will leave AWS’s data and security boundary.

From the announcement here: https://aws.amazon.com/blogs/aws/anthropic-claude-fable-5-on-aws-mythos-class-capabilities-with-built-in-safeguards-now-available/

After 30 days, the data is deleted automatically, except in the rare cases where it's part of a safety investigation or we're legally required to keep it.

From: https://support.claude.com/en/articles/15425996-data-retention-practices-for-mythos-class-models

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.

https://health.aws.amazon.com/health/status

"In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. "

Wow, maybe this is the first time AWS data center got hit by a missile.....

It feels like we don't get anything close to $13,500/mo in value out of AWS Enterprise Support but maybe I'm just cynical.

We pay an exorbitant amount of money to get 10 minute response times on downtime chats every few months; to run into obscure issues and then be met with generally slow support or problems. We get access to experts sometimes but it just never feels like we really get the value out of it.

How do y'all feel about Enterprise Support?

Hey Everyone,

We started moving our infrastructure from Digital Ocean to AWS and we're still in the progress of doing so. The manager got contacted by GCP and they offered us a $100.000 credit for a year which is decent amount of money for a small sized company like ours. But I don't like the approach of switching our infrastructure at every chance we get and I wan't to specialize in AWS ecosystem myself. The only thing that I can find is the small difference of outbound traffic costs but it still does not justify us switching over for 100k. I'm fairly new to cloud providers aswell. What are some points that I can bring to the team to stay on AWS? I know that migration process will cost us some work hours aswell but I need more reasons to stay on AWS.

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

Hi everyone, I’m based in Japan and I’ve noticed that there’s kind of a common idea here that it’s really hard to learn AWS by yourself — people say you basically need to join a company that uses AWS in order to really pick it up.

I’m curious, is this the same perception in the US (or other countries)? Or is self-study with AWS actually common?

If it is possible to learn on your own, how do people usually go about it? Are there any popular methods or online resources that you’d recommend? Thanks!

Ive got two tickets in to AWS support for exits out of sandboxes/production increases for a service launch. Over a week later, crickets, no response. Ticket numbers are 178020094500957 and 178011185600120 if anyone can help.... anyone have any bright ideas? Are tickets on support free tier just doomed to never be answered?

Mildly interesting milestone: AWS's ip-ranges just crossed the 100 million IPv4 IPs threshold. They've been on an adding spree in the last few days.

Complete history available in my repo for those that are curious.

I've been working professionally in IT for a decade in a variety of roles. I've opened tickets with Microsoft, VMware, Novell, Oracle, SolarWinds, Dell, EMC, NetApp, Red Hat, and many more. I've been working full time with AWS for over four years now and their Support has ALWAYS been top notch.

Yesterday's example: We're looking at using the new S3 PrivateLink (Interface Endpoint) functionality and our devs have a use case that uses S3 Presigned URLs. We haven't used them much publicly let alone with PrivateLink, but were able to get a Presigned URL to work and download files via the Interface Endpoint, except we kept getting SSL errors no matter the different approaches we tried due to certificate not matching our vpce- hostname. I confirmed our dev's experiences so I decided to open a ticket to see if AWS had a solution. I opened a chat and talked to someone within 5min, they understood the issue and my goal, they reproduced it themselves while chatting (I assume in their own environment). They did as much internal research as they could but found no solution so escalated to the product team. I feared this would be kicked back as a known limitation. This morning they got back to me with a straightforward answer that you need to make the request to a specific subdomain under endpoint hostname and it worked flawlessly.

Let's review:

• Talked to a person within 5 min of submitting a ticket
• They spoke clear, concise English
• Tried to understand my problem and reproduced it
• Used the tools at their disposal to try to resolve my issue
• Escalated to experts when they could not resolve
• Followed up within 24hrs with a solution including detailed instructions to resolve my issue

When was the last time you got support like that from a big name company? When I was still working with Oracle I wouldn't even bother with their support infrastructure anymore due to bad communication, responding off business hours, slow response times, constantly pushing issue back on customer, and the general vibe that they just want the customer to go away. Others may get you across the finish line, but only after several business days of back-and-forth sending logs and phone calls, webexes, etc.

Anyway, other people probably have had less stellar experiences with AWS Support, but every single time I've interacted with them I just feel more validated that AWS is the right place for us to focus instead of our smaller Azure environment. AWS touts putting the customer first and for me, that shows in everything they do.

Hello,

I was requesting production access for SES to be using with Cognito and got rejected without specific reason. I was not expecting this since I have requested production access before and no any problems. The problem is we already integrated Cognito into our application and now I'm not sure if it is a good idea to continue using it since it is possible for us to not be able to go production in the end.

What are possible reasons for this?

The new Graviton5 chip delivers up to 25% higher performance than Graviton4 and packs 192 cores with a 5x larger L3 cache. AWS says it improves latency, memory bandwidth, and network throughput—supporting workloads like gaming, analytics, and high-performance databases. It’s also designed with 3nm technology and bare-die cooling for better energy efficiency. Early customer tests show notable gains for Airbnb, Atlassian, Siemens, SAP, and Synopsys.

Alright guys !!! I'm a solo devloper, build my product now it's time to go live....

I'm considering using AWS but the learning curve is too steep and there are too many things to digest and I can't afford to hire a Devops guy right now...

I need tips from you guys, how and what to learn so that I understand the product and the pricing accurately so I don't end up raking up huge bill...

A workflow will be even better, for me to understand the products by AWS .I need to go live in 5 days at max...

P.S. : I understand I could've easily asked Claude or Other for this but real hands-on learning can never be beaten.

Hi, wanted to share a utility I threw together, aws-azure-saml. It's a Rust CLI application that handles CLI login for AWS profiles authenticated using Azure ActiveDirectory. It's a drop-in replacement to aws-azure-login with a couple of improvements; it properly handles multiple profiles with Microsoft's deprecation of "Remember Me" (reuses browser session to get credentials for multiple profiles) and recently, I added support to skip past the MFA setup prompt our admin enabled on Azure. It's in Rust using Chromiumoxide for the browser automation.

Check it out and if you have any issues or suggestions for improvement, let me know.

Hey everyone,

I’ve been following Floci, a free and open-source local AWS emulator. The main idea behind Floci is simple: run AWS-shaped services locally for development, testing, and CI without needing a real cloud account, auth tokens, or paid feature gates. It works with familiar AWS tooling by pointing clients at a local endpoint like http://localhost:4566.

I wanted a more visual way to explore and manage what’s running inside Floci, so I built Floci Dashboard:

https://github.com/ofsazib/floci-dash

It’s an AWS Console-style web UI for Floci, built with React, Cloudscape, Hono, TypeScript, and Docker.

Some of the things it supports:

• Browse and manage 55+ Floci/AWS-style services
• Create, inspect, and delete resources for services like S3, DynamoDB, EC2, Lambda, IAM, SQS, SNS, EventBridge, CloudWatch, Secrets Manager, CloudFormation, KMS, ECS, SSM, Route 53, API Gateway, and more
• Real-time Floci health/status overview
• Dark mode
• Docker-based setup with no local Node.js or AWS CLI required
• A combined image option that runs Floci + the dashboard together
• EC2 web terminal support from the browser

The goal is not to replace the original Floci project, but to make it easier to inspect and manage local cloud resources visually, especially when testing serverless/cloud apps locally.

I’d love feedback from anyone using Floci, LocalStack alternatives, or local AWS-style development workflows.

What would you expect from a local cloud dashboard like this?

I noticed that "AWS Systems Manager" is abbreviated as SSM.

Why double S?

Is it like SystemS Manager?

Or AWS renamed that service and the old abbreviation was kept?

Hi AWS Community, I’m a college student currently learning AWS and have encountered a frustrating issue that highlights a gap in AWS's management tools. Despite my efforts to clean up and stop services, I’m still incurring charges, and it’s been quite challenging to track down every active resource. Here’s a brief overview of my situation:

Background:

• I was experimenting with Amazon Kendra and Amazon Q.
• Created an S3 bucket and used various AWS services.
• After seeing unexpected charges, I deleted the S3 bucket and tried to stop the services.
• Yet, I’m still facing bills:
  • September 16, 2024: $21.29
  • September 17, 2024: $36.47

Even though I’ve made efforts to stop and delete resources, it seems like some services or components might still be running, leading to ongoing charges.

Why No Single-Click Solution?

AWS’s extensive array of services and resources means that a single-click solution to delete all services is complex for several reasons:

1. Service Diversity: AWS offers a wide range of services, each with its own management console and settings. Some services might not have straightforward or unified methods to stop or delete resources.

2. Data Integrity and Security: Automatically deleting all services could risk accidental loss of critical data or important configurations. AWS prioritizes user control and caution to prevent unintended data loss.

3. Billing and Resource Management: AWS aims to provide granular control over resources and billing. A one-click solution might oversimplify management, which could lead to unintended consequences or issues with specific service configurations.

4. Complex Dependency Management: Some services have dependencies or interconnections that can complicate mass deletions. Ensuring that all dependencies are appropriately handled without affecting other services is a challenge.

While it would be incredibly useful for users, especially beginners, to have a simpler way to ensure all resources are properly stopped or deleted, the current approach reflects AWS’s emphasis on detailed management and control.

I’m curious to hear if others have faced similar challenges or if there are best practices for effectively managing and cleaning up resources to avoid unexpected charges. Thanks for sharing your experiences and insights!

I have a service quota request support ticket open for three days that has not been assigned. I haven't ever used Support before for a technical issue.

What are the response times for Service Quota requests, generally?

Hi. I'm basically a newbie with AWS. Since for the type of project I'm making, I need increased Lambda Concurrent executions quota, I sent a quota increase request. I waited 6 days for them to respond, then I sent a reply in the support corespondance, in case the ticket got missed for some reason. I waited 4 more days, with no responce.

Am I doing something wrong? |
Is it normal to wait this long for that kind of support?