r/aws • • 5h ago

discussion Account gripes

7 Upvotes

A significant portion of this sub is now people who have account troubles and want to complain so that support will fix it. Is there a version of this sub that doesn't have those posts? Or has an attempt been made to push them over to another sub?


r/aws • • 12h ago

discussion What UK cloud/DevOps roles paid in 2026, and how AWS stacked up vs Azure

15 Upvotes

Quick disclosure: I work at Archer from hackajob, so this is our own platform data based on 4,423 UK DevOps and Cloud roles posted in 2026 (client base skews finance and enterprise).

Median salary across everything was around £75k.

  • AWS was in ~32% of postings, the most common cloud, but Azure was closer than you’d expect at ~25%. GCP ~17%.
  • Cloud Engineer sat around £75k, Platform Engineer ~£82.5k and the most in-demand title, about half of all openings.
  • AI/automation experience (LLMs, ML ops, automation) was the best-paying skill signal, +£20k over the median, in about 1 in 5 postings.

Azure being that close is a UK thing. In most markets AWS leads by a lot more. My guess is the finance and enterprise skew, plenty of Microsoft-heavy shops. If you’re AWS-only in the UK, that share is worth factoring in.

Does that match what you’re seeing in UK, or is AWS still clearly ahead where you are?


r/aws • • 1d ago

general aws AWS announces agentic account creation for agentic coding harnesses

Thumbnail aws.amazon.com
65 Upvotes

r/aws • • 10h ago

discussion What does Amazon look for with AWS cloud support internship ?

0 Upvotes

What does interview process for that role normally ask for and what are the type of applicants they look for?


r/aws • • 10h ago

article Went to bed with a $50 budget alert. Woke up to a $4,180 AWS bill from a key I forgot existed

0 Upvotes

This happened last week and I'm still a bit shaken, so writing it down.

I went to sleep around midnight. The budget alert email for my $50 budget arrived at 6:40 in the morning, when the bill was already over $3,000. By the time I logged in and found the cause it was $4,180. GPU instances in 4 regions I've never used, all launched within about 20 minutes of each other around 1am.

The key was from an IAM user I made in 2024 for a tiny CLI tool I published to npm. I forgot that user existed. The package never had a .npmignore and no "files" field in package.json, so npm publish included everything in the folder. Including the .env with the access key. It's been sitting in a public tarball on the npm registry for over a year. I only ever checked GitHub for leaked keys, and that repo on GitHub is clean.

What I keep coming back to is the alert. I thought $50 was my safety net. But billing data runs hours behind, so the alert is really telling you what happened earlier in the night. Someone who launches a dozen GPU instances at 1am has a few hours of free compute before anything even emails you.

Support was decent so far. They asked me to secure the account, delete the key and confirm nothing else is running, and they're reviewing the charges.

What I changed:

- Deleted every IAM user with long lived keys and moved my own CLI access to IAM Identity Center, so there are no access keys on my laptop anymore

- Set up a budget action that applies a deny policy on EC2 when spend crosses $100, so it actually stops things instead of only sending an email

- The few app secrets I still need live in Infisical now and get pulled in at runtime, and every package I publish has a "files" field so only the build goes out

- Ran npm pack --dry-run on all my old packages to see what each one ships

Is there anything closer to a real hard stop on AWS than budget actions? And has anyone actually checked what their old npm packages contain? I'd never once looked


r/aws • • 1d ago

general aws AWS suport is the wrost i have ever seen anywhere

45 Upvotes

I am writing this after 25 days of a case being open. And 6 days since their last reply,

Almost a month ago, they closed some services on my account due to a login from somewhere else.

From then on, they keep asking me to review this and that. After I do one thing, they ask for another. same has been going on for a month now.

- Chat never connects; if it do it take more then 2 hours.
- Web: they just ignore it their last reply to the case was 6 days ago
- Phone: always throws an error.

I feel like they forcefully want their customer to move to premium support or Leave.


r/aws • • 16h ago

billing No longer have access to my account's email

0 Upvotes

I have an AWS account associated with an email address that I no longer have access to. I'm still being charged, so I'd like to cancel any active services.

However, seems that I must to sign in before I can contact customer support. Their AI support was not helpful.

What should I do now? TIA.


r/aws • • 1d ago

security AWS Sign-In now supports OAuth 2.0 Token Exchange

Thumbnail aws.amazon.com
46 Upvotes

r/aws • • 1d ago

article Making AWS TEAM private: what worked, what stayed public, and why a fresh install is broken since CloudTrail Lake closed

1 Upvotes

I deployed TEAM (Temporary Elevated Access Management) a while back at a regulated enterprise, and it only got approved under a yearly security exception because the UI is on Amplify Hosting and the API is a public AppSync endpoint. I went back to see what it takes to remove that exception. Short version below, full writeup and the fork at the end.

What changed

  • Amplify Hosting has no internal mode, so the SPA runs in nginx-unprivileged on Fargate behind an internal ALB with a private hosted zone.
  • AppSync is created with Visibility: PRIVATE (one property override in the Amplify project). Queries, mutations and the realtime websocket all go through the appsync-api interface endpoint. Visibility is immutable, so on an existing install this is a replacement API, not a setting.
  • Six Lambdas call AppSync, so they move into private subnets. The rest stay outside the VPC.
  • Build moved from Amplify Hosting to CodeBuild running a headless amplify push.

Upstream bugs fixed in the fork

These affect stock TEAM, private or not:

  • Fresh installs fail since CloudTrail Lake closed. AWS stopped accepting new CloudTrail Lake customers on May 31, 2026, so creating the event data store now fails with "CloudTrail Lake is no longer accepting new customers." Upstream creates that event data store even when CloudTrailAuditLogs is set to none, so there was no configuration of TEAM that would install in a new account (upstream issues #511 and #586). In the fork, none now really means none.
  • The Logs Insights replacement (open PR #599) didn't work. It swaps CloudTrail Lake for a Logs Insights query against the Control Tower org trail log group, which gets session audit logs back without buying anything new. Three fixes: logs:GetQueryResults doesn't support resource level permissions, so it needs Resource "*" while StartQuery stays scoped to the log group; the start and results Lambdas have different execution roles and the cross account role has to trust both; and the real Control Tower log group name has a random suffix the PR's docs leave out.
  • Revoked requests showed an end time of Dec 31, 1969. The revoke state machine writes endTime directly to DynamoDB, skipping AppSync, so no subscription fires and the history page renders new Date(null). The same null crashed the session log lookup. Both now fall back safely.

Egress findings

  • Almost everything works over VPC endpoints: sso, identitystore, states, sts, logs, ecr, gateway endpoints for DynamoDB and S3, and Organizations through a cross region endpoint (its endpoint only exists in us-east-1).
  • Cognito is the exception. With a cognito-idp endpoint in the VPC, ListUsers fails with PrivateLink access is disabled for the user pool that has ManagedLogin configured and every request sits in pending. User pools with a domain can't use PrivateLink, and private DNS captures the hostname for the whole VPC, so a shared or "tidy up" endpoint breaks TEAM even with NAT in place.
  • Cognito managed login itself stays public. That's how Cognito works, so it's documented in an ADR rather than hidden.

Testing tip: SSH over SSM with DynamicForward and Chrome on socks5:// so DNS resolves inside the VPC, plus an inline PAC script if the tunnel host has no internet route.

Full writeup: https://www.briancarpio.com/blog/private-aws-team Fork: https://github.com/bcarpio/iam-identity-center-team

Anyone else running TEAM in a new account since the CloudTrail Lake closure? Curious what you did for session audit logs.


r/aws • • 1d ago

technical question Weird rds api issue in sa-east-1

4 Upvotes

I'm unable to list rds databases on console or even issue cli commands at sa-east-1 in one of the accounts.

There's a weird api error message which says "An internal error has occurred. Please try your query again at a later time.".

Anyone receiving the same error ?


r/aws • • 1d ago

discussion Account suspended for 3 days — unable to receive verification emails because the email domain depends on the suspended account

Thumbnail gallery
4 Upvotes

My AWS account has been suspended for three days, and I’m stuck in a verification loop. I would really appreciate some practical advice.

Here’s what happened:

  1. My bank flagged AWS’s overnight charges as suspected fraud and blocked the payment method. Meanwhile, AWS’s suspension warnings all went to my spam folder, so I missed them. My account was subsequently suspended.
  2. The domain used by my administrator email address relies on DNS hosted in that same AWS account. Since the suspension, that email address has been unable to receive any messages, including verification emails.
  3. AWS Support keeps asking me to complete verification through the administrator email address. I have repeatedly explained that this mailbox cannot receive emails because of the account suspension.
  4. Despite that explanation, support continues to direct me to the same process for submitting verification documents. I am willing to cooperate and provide the necessary information, but the process depends on an email address I currently cannot access.
  5. I also cannot upgrade to Enterprise Support because the account is suspended.

I even approached another company and paid for their Enterprise Support plan, hoping they could help escalate the issue. However, the response from AWS was still essentially to log in to my administrator email account—which, as I have repeatedly explained, cannot receive any emails.

How can I verify ownership and get this reviewed when the required mailbox depends on the suspended account itself? Is there an alternative verification process or a way to reach the team that can address this specific problem?

My customers are now complaining about the disruption, and this is seriously affecting our business. If anyone has dealt with a similar situation, I would be grateful for practical advice on what actually helped move the case forward.

Thank you.


r/aws • • 2d ago

discussion aws hotfixed the fonts, but to me it still looks like it was vibecoded

43 Upvotes

for comparison this was how it looked before-ish, on bedrock

try and look at my role, contrast is like ahh, i dont mean to disrespect, but do you really think above is better?
is it just me who think its worse?

and its 4MB of css


r/aws • • 2d ago

re:Invent What happens in Networking Receptions in Re:Invent? And a Food question

4 Upvotes

My employer is sending me to re:invent this year. I have some questions: What happens in the networking receptions by AWS and other companies? I have a health condition which needs me to eat proper meals at regular intervals. I have a packed schedule leading into the night on many days. What kind of food does these receptions provide? Many of them say drinks and snacks. I am not much on drinking as well. How can I keep myself well-fed while running from venue to venue? This is my first time to las vegas and all that I have read makes me nervous (distances etc)


r/aws • • 2d ago

technical question AWS account blocked from launching EC2 instances - Support case unassigned for 4 days

0 Upvotes

Hi everyone, [u/AWSSupport](u/AWSSupport),

I’m experiencing an issue with my AWS account that is preventing me from launching any EC2 instances.

Every time I try to launch an EC2 instance, I receive the following error:

Error: creating EC2 Instance:
operation error EC2: RunInstances
HTTP Status: 400
api error Blocked:
This account is currently blocked and not recognized as a valid account.

Some important details:

- My AWS account is several years old, not newly created.
- I can successfully create RDS instances without any issues.
- There are no outstanding payments or known billing issues.
- I’ve already updated my payment method.
- I also have access to a separate corporate AWS account, where EC2 instances can be launched normally.
- I opened a support case on November 12, 2026, under Account and Billing → Account Verification.
Today is November 16, and the case is still marked as “Unassigned”, with no response from AWS.

The fact that EC2 works normally in my corporate AWS account, while my other account is blocked, suggests that this is an account-specific restriction rather than a general EC2 service issue.

I’m currently on the Basic Support plan. Unfortunately, the Account Verification category only allows web-based support cases. Both chat and phone support options are disabled, so I have no way to contact AWS Support directly.

This situation is blocking my infrastructure deployment, and I have no information about why my account is restricted or how long it might take to resolve.

[u/AWSSupport](u/AWSSupport), is there any way to escalate my existing support case or get it assigned to someone?

Has anyone experienced a similar situation? How long did it take AWS to resolve the restriction?

Any advice would be greatly appreciated.

Thanks!


r/aws • • 2d ago

discussion Absurd on account verification

0 Upvotes

EDITED: Less then in 24 hours after creating this post, situation was sorted out and now I am able to access my account. I would like to express my thanks to that person, who elevated this post for the support team. For some reason this subreddit works faster then Support Center on AWS site... I will hope that this problem will never happen to me or other people again, so things will change to better. And i wish my next post regarding AWS will be more positive than this.

I am a student, created my AWS account some time ago (about a year) because i needed it to do university tasks (we had a subject about cloud technologies). After it I had deactivated all the services on it (to not waste my money).

Now I started a hobby project, and for it I needed a data storage and a VM. So i decided to use AWS. Timeline of the events(time is my local):

- Friday 13.11, around 8:00 - logged in into my AWS account, updated payment data and started using it
- Saturday 14.11, 19:40 - got an email that my account is "on hold" and i have to provide my documents
- Saturday 14.11, around 19:50 - uploaded all the requested documents to the link
- Saturday 14.11, 19:53 - got a confirmation that AWS received my documents
- Sunday 15.11, 12:10 - was unable to start my VM, as mail i got only said that i am unable to request a new services, I opened a support ticket asking about how long this "verification" can take and if there is a way for me to continue using my services during it
- Sunday 15.11, 19:41 - got an email that my account is suspended because i had not provided documents
- Sunday 15.11, 19:55 - created another support ticket, now asking about this situation and its cause

--- EDITED ---

- Monday 16.11, around 19:30 - this post was written
- Tuesday 17.11, 16:26 - got a message from AWS that they cancel my account review request, saying that I am no longer required to provide documents and can continue using my account

--- END OF EDITED ---

For now both of those tickets are "Unassigned". I initially didnt want to go with this in public. I understand that I am a *very* small client, with "basic support level". But for me this situation looks crazy. You asking me for documents, putting me on timer. Then you just doing nothing and saying me "We understand that circumstances may have prevented you from responding to our initial request, and we want to give you another opportunity to verify your account and restore access."

It feels like a bold trolling. I mean, if I would do something like this on any of jobs i had to any of clients - my boss would fire me immediately. And this is definitely not a "level of service" i was expecting from a such big and famous company. I literally understand it as "We dont care about you, we dont care about your data and we event dont care about anything we say to you"

And while i lost not so much (because its just my hobby) - what i had seen is more then enough for me to never use this service in real production. Btw IT initially was my hobby and everything i learn here came from it. So, one more mistake that i will never repeat.

And I am writing this post not to ask again to help me, i already did it in support ticket and under the AWS support response to the post here describing the same problem. I read some not so good things regarding AWS here. And one of those i had seen now in person. But i know that things happens, and people usually writing about bad things and staying silent about good. And maybe I just got very unlucky (maybe creating a VM on Friday 13th was not the best idea).

So, out of curiosity, I would like to ask your, both users and AWS representatives. What is your opinion on this situation and AWS quality of service at all?

And i would like to ask you for advise. I know how to do it in my country, but as AWS operates not under its jurisdiction, i want to clarify it. If it comes a way that this case wont be resolved(this ghosting will continue), how can enforce AWS to delete all my personal data (including my documents, address, payment data etc) and revoke a permit for its processing? For some reason, if company doesnt cares about me - i dont want it to have a lot of my sensitive data "just laying around".


r/aws • • 2d ago

billing AWS Account Creation Support Case Unassigned for 3 Days (Case #179464065100535)

1 Upvotes

Hello, I am hoping someone from the support team can help take a look at my account creation case.

My free-tier signup has been completely blocked at the phone verification stage with a processing error, despite waiting over 24 hours and attempting verification with a secondary phone number.

My support case #179464065100535 has been unassigned and sitting in the queue for 3 days. Could an agent please review or escalate this verification block? Thank you!


r/aws • • 2d ago

discussion issues with lightsail this morning?

0 Upvotes

I have 3 of about 50 instances that seem to have a network or disk issue. Since AWS took away trouble reporting on lightsail I can't even report the issue. again, just 3 of about 50 instances and they are 'up'. I got ssh'd into one and any 'cpu' stuff works but as soon as I try to hit the disk it goes unresponsive.


r/aws • • 2d ago

security Key leaked, account limited - access still not restored

0 Upvotes

Evening!

Had a key leaked through a very stupid mistake from my side, AWS caught it at about $5.5k of usage, restricted our account and emailed me. This all happened last night about 2200 UTC

I immediately revoked the keys that were at fault and began investigating. Even though I confirmed last night that I'd taken steps to secure the account and updated the ticket with exactly what resources the attacker had used (Fable 5.2 credits only) within a couple of hours the restrictions are still in place and no updates on the account, this is blocking a few things like:

  1. Our lambdas are not working
  2. New cognito signups are not working - thankfully existing users can still sign in
  3. Bedrock invocations for our existing KBs are not working

We're on Business support, have been for a good couple of years but according to our reseller we don't have an assigned AWS Account Manager

Any ideas? Thanks:)


r/aws • • 2d ago

discussion Trying to use Notify 6 weeks, 2 cases, 3 identical canned rejections for a 10-year-old paying account

0 Upvotes

I'm pretty appalled by AWS right now. I tried to create a Notify configuration and it was rejected right away with "ACCESS_DENIED_CONTACT_SUPPORT". So I contacted support.

My first case got a canned reply: "Due to some limiting factors on your account… We enforce these limitations on all new accounts." I've been a paying customer since 2016 (Route53, S3, EC2, RDS, Beanstalk, CloudFormation), with every invoice paid. I told them that and asked them to look again. The next day I got the exact same text.

So I opened a second case. They asked me everything: what the app does, region, opt-in process, target countries, daily volume and message templates. I answered all of it the same day. My use is as small as it gets: OTP codes only, AWS's own pre-approved Notify template, under 20 messages a day, a $1–2 monthly spend limit, mostly sent to my own number while testing.

After that I got "typically within 3 business days," then "still processing, taking longer than expected." Nothing else. I even paid for Business Support+ to get someone to look at it. Three days later, after 41 days in total, I got the same canned rejection for the third time, word for word, including "all new accounts."

Ten years of paid billing and steady use of other services isn't enough "billing history"? That's a template, not a reason. As it stands, don't plan on using Notify: you might never get access.


r/aws • • 2d ago

discussion What should I do? I can't register with my email

Thumbnail gallery
3 Upvotes

My account is an university email address that I use to log in to everything related to my coursework. However, when I tried to sign up for AWS for the first time, the system indicated that the email had already been used and that MFA (Multi-Factor Authentication) was already set up, even though I have never used AWS with this email before. I tried to create a case to get a solution, but the reply doesn't help much. They said that my email address doesn't match with any AWS account, yet everytime I tried to sign up into AWS with this email address, it asked me for a password. Even worse, when I tried to follow the "forgot password" instructions, I was instead asked to enter an MFA code, which I don't even have. What should I do? I'm sure that I'm the only one who has access to this email. And even if it got hacked, what can I do to recover this account?


r/aws • • 2d ago

discussion RE:Invent Ticket

0 Upvotes

Looking for a Reinvent ticket if anyone has one not using or cant go. Thanks!

If up still looking, to be clear I dont have a lot to give :) - more of a last resort

Please DM me.


r/aws • • 2d ago

ai/ml [Action Required] Cannot Access Bedrock, Support Not Responding.

0 Upvotes

Hi All,

I am currently studying for the Generative AI Professional certification and performing hands-on work using my AWS account. When I tried to use Bedrock models, I got the following error:

ValidationException: Error 002: Access to Bedrock models is not allowed for this account

I've reached out to support days ago - both via web reply and chat request - but I didn't get a response on web and I was in live chat queue for over 3 hours today without connecting with an agent

Can AWS please help?

CASE: 179450947500624


r/aws • • 3d ago

technical question Is AWS US-East-1 Identity Center sign-in down?

50 Upvotes

Health dashboard says nothing is wrong, but is it down and X has some complaints. Returns 503.


r/aws • • 3d ago

article Lessons from building centralized ingress and egress inspection with GWLB and Palo Alto VM-Series (and what I'd change in 2026)

7 Upvotes

I wrote up a design I built a few years ago for a large regulated enterprise and figured this sub would have opinions. Short version below, full writeup with diagrams and Terraform at the end.

Starting point: every spoke VPC had no IGW and no NAT. All traffic in both directions went over TGW, down Direct Connect, and out the data center's internet edge. We moved the internet edge into a dedicated DMZ account with Palo Alto VM-Series behind a Gateway Load Balancer, inspecting everything inbound and outbound, and let app teams create their own public endpoints through a pipeline.

The things that actually mattered:

  • Appliance mode on every TGW attachment in front of the firewalls. GWLB keeps a flow on one firewall only if both directions reach the same GWLB endpoint. Without appliance mode, TGW can send the reply into a different AZ and the session dies.
  • Client IP preservation off on the DMZ NLB. Inbound chain is public NLB in the DMZ (IP targets) > TGW > internal NLB in the spoke on static IPs > internal ALB. AWS doesn't support client IP preservation when targets are reached through a TGW, and the packet walk shows why: the spoke would reply to the real client IP, the spoke TGW route table sends 0.0.0.0/0 to the egress inspection path, and that firewall has never seen the connection. With preservation off, replies go back to the NLB's private address and return through the same ingress firewall.
  • Edge routes on the IGW target each public subnet's exact CIDR, one per AZ, so inbound traffic is inspected by the same-AZ GWLB endpoint.
  • Static private IPs on the spoke NLB via subnet_mapping, since the DMZ NLB targets it by address.
  • GWLB target_failover rebalance helps less than you'd think. Flows get rehashed to a healthy firewall, but that firewall has no session, so long lived TCP connections still reset.
  • Don't use ELB health checks on the firewall ASG during bring up. The GWLB health check fails until Panorama pushes the interface management profile, and the ASG will terminate firewalls that are still bootstrapping.

Cost of the design: the app never sees the real client IP. The ALB can't take Proxy Protocol, so client IP based controls have to live on the firewall, not in a WAF on the ALB.

What I'd change today:

  • For inbound HTTP, cross account CloudFront VPC origins (late 2025) can replace the whole NLB chain and pass the real client IP, if the security team accepts WAF at the edge instead of an NGFW.
  • AWS Network Firewall now attaches natively to TGW and removes the inspection VPC. But I wouldn't swap out the Palos for a client whose network team centrally manages every firewall in Panorama across the data center, branches, and cloud. Moving the cloud side to Network Firewall splits that into two policy models, two sets of logs, and two consoles. For those shops the GWLB inspection VPC is the cost of a single view.

Full writeup: https://www.briancarpio.com/blog/centralized-inspection-gwlb-palo-alto

Curious how others are handling inbound inspection now that CloudFront VPC origins work cross account. Are your security teams still requiring an NGFW in front of everything internet facing?


r/aws • • 3d ago

general aws Action may be required messages

2 Upvotes

Just received AWS Security Hub CSPM messages in Japanese AP-Northeast-3 and Korean AP-Northeast-1 as far as I’m aware we don’t have anything in those regions. As we are in London?

Is it anything to worry about?