I am completely trapped in an AWS account security loop and need a human engineer to escalate my case.

Root Cause: I closed my initial default project on a new account before a replacement could be provisioned. My root credentials authenticate perfectly, but because there are 0 active projects, the top-level router crashes. Every console subdomain (including Billing and standard Support) immediately returns: "Something went wrong. This project is currently inaccessible. For more information, visit AWS Settings."

The Loop:
1. I cannot log in to open a traditional support case because the console is completely broken.
2. I tried using the unauthenticated/offline forms, but the automated security bot immediately rejects them, stating I must log in to discuss account-specific information.
3. Tickets submitted via the legacy ://aws.com timeline have sat unassigned and ignored since October 8.

I have already paid any outstanding balances. I need an Account / Sign-In Engineer to manually clear the profile initialization block or inject a blank default project context so my console can load. My public form transaction reference numbers are: 179198721400075 and 179140354800545. u/AWSSupport — Can you please escalate these references to a human engineering team?

Is there any way to make it prepaid?

How do u make AWS bills predictable?

Hi All,

I've identified a bug in AWS WorkSpaces caused by an incompatibility between the WorkSpaces Personal Smart Card driver and the Windows October 2026 cumulative update.

It manifests as the update downloading and showing as "Pending Restart", however during the commit phase it fails and rolls back with error 0x80070002.

Once this happens, check:

C:\Windows\WinSxS\pending.xml

You should see references to:

C:\Windows\System32\WinSCard.dll

The WSP agent implementation does some unusual hard-linking of this file to its own version, which Windows servicing doesn't like. During the update process, poqexec.exe fails when attempting to modify the file, causing the update to roll back.

This has been confirmed with Amazon Support, who are working on a permanent fix, although there is currently no ETA for resolution, expected in next agent version.

Workaround:

1. Ensure the WorkSpaces agent version is 2.2.0.2482 or later (August 2026 release minimum).
2. If running an earlier version, reboot the workspace to pick up the newer agent version.
3. Create the following registry value:

Key: HKEY_USERS\S-1-5-18\Software\GSettings\com\nicesoftware\dcv\smartcard

Value Name: Process-Denylist

Type: REG_SZ

Value Data: ['poqexec.exe']

1. Reboot the machine to apply the exception.
2. Patch and reboot as normal.

This prevents poqexec.exe from interacting with the smart card component during servicing and allows the cumulative update to install successfully.

Hope that helps whilst we wait for a fix!

tldr: Trawl is an ALB/S3/CF access log analyzer that runs entirely in your browser.

Hey folks,

recently I found myself having to generate a report from some AWS access logs for one of my clients. As this turned out to be a recurring task, I planned to build this into a reusable self-service application but didn't like the idea of having to build yet another backend+frontend stack and take care of hosting it.

I remembered hearing something about a WASM version of DuckDB but I was a bit worried about the performance when millions of lines of log data. Luckily it turned out to be good enough for my use case so I gave it a go.

Building this was a very enjoyable experience and it's crazy what kind of functionality you can achieve nowadays in the browser with no backend at all.

Big kudos to DuckDB which is the main driver of this project.

You can give it a try by loading some sample data or your own access logs. Again, nothing leaves your browser, all processing is happening locally.

Loading 1GB of data takes ~60 seconds on my end. No need to keep the browser tab open though during the initial load and the tab name shows you the progress.

Tried improving performance by enabling the experimental multithreading support but it didn't result in any meaningful gain. Will keep an eye on that though.

Wish you guys a pleasant day and a stable AWS bill 😉

I'm working on a self-hosted CRM that companies would deploy in their own AWS or Azure account, or on-prem, instead of using a SaaS product. Before I go much further, I want to understand the side I worry about most: what it's actually like for the people who keep this kind of software running.

My assumption so far is that the software itself is the easy part, and the ongoing work is what makes or breaks it: upgrades, patches, backups, someone getting paged at 2am. I'm designing around that. It ships as containers on a managed Postgres, upgrades apply themselves with no manual steps, and there are as few extra services to run as possible. But I don't know whether that matches what really matters to you, or whether I'm solving the wrong problem.

So I'd really like to hear from people who've run business apps like this. When your company chose to self-host something instead of paying for SaaS, what drove it: cost, compliance, data residency, or just wanting control? Once it was running, how much effort did it take in practice, and did that surprise anyone? I'm also curious about the other side: the apps that were a pleasure to run, what made them that way, and the ones that made you swear you'd never self-host again.

And if you've ever evaluated something like this and said "no, we'll just pay for SaaS," I'd love to know what tipped it. Those stories are probably the most useful to me.

Not selling anything here, and there's nothing to sign up for. I'm trying to build this the right way before it's too late to change course. Thanks for any stories, good or bad.

EDIT: I overstated, and shouldn't have said ERP

Hi, I opened a new AWS account (India, AWS India billing) for my startup about a week ago. Everything else works: S3, SES and IAM, and our AWS Activate credits were even approved and applied.

But CloudFront won’t let me create a distribution. I get:

“Your account must be verified before you can add new CloudFront resources. To verify your account, please contact AWS Support and include this error message.”

CloudShell also says “Your account verification is in progress. This may take up to two days for new accounts.”

What I’ve done so far:

• Verified my phone number
• Completed contact, payment and tax details
• Opened a support case with the error message, and followed up

It’s been about a week now. Has anyone else run into this with a new account, especially in India? How long did it take, and was there anything that sped it up? Should I open a separate case just for CloudFront?

Case ID: 179265014000179
Also I cant raise another case. When clicked on the Create Case it redirect to the same support home screen.

Thanks!

Hello everyone. I want to publish my Medium blog to Medium publication that related with AWS but I confused. Here anyone can recommended me to publish?

Hello everyone not sure if this is the right server for reviving a rtsp aws but can anyone tell me if this rtsp link is still active or not?

Found this from the wayback machine and it appears to be a episode of a kids show named Heulwen a Lleu (a welsh television programme)

Here is the link btw:

rtsp//:ec2-46-137-111-46.eu-west--1.compute.amazonaws.com:1935/httpl/_definst_/mp4:amazons3/bsmvid2/UK/standard/600/heulwen_a-lleu_abracadabra_cymraeg_re145r_001e2e2af4.mp4

I dont want to deal with signing up on amazon aws so thats why im asking for anyone to help!

I recently built a AWS serverless side project and felt that coding agents struggled to gather the broader wholistic context regarding code and devops. I studied about some alternative to SAM like SST but they all believe in the same concept - code and infra should be separate - Infra as Code (IaC).

Then I stumbled across encore.dev which rethought all of this fundamentally using Infra from Code (IfC) and realised this is exactly what I was looking for.

But one major issue, it supports exclusively container services like EKS meanwhile I use solely serverless for my weekend projects. Hence, decided to build a Infra from Code (IfC) for pure AWS serverless services.

Decided to dogfood it by making my own side project use it. This approach allowed make eventually verify whether IfC compiler works.

So have a look it and tell me what you think about it. Don't keep your expectations too high, this is just a cute side project. :-)

framework: https://github.com/harsh-vardhhan/syncploy
serverless app: https://github.com/harsh-vardhhan/EHR-backend
documentation: https://www.syncploy.com/