technical question Is AWS US-East-1 Identity Center sign-in down?
Health dashboard says nothing is wrong, but is it down and X has some complaints. Returns 503.
Health dashboard says nothing is wrong, but is it down and X has some complaints. Returns 503.
r/aws • u/keto_brain • 2h ago
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?
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?
r/aws • u/tshirtdr1 • 10h ago
New account: CloudFront "account must be verified" — what unlocked it
My new AWS account couldn't create a CloudFront distribution ("Your account must be verified before you can add new CloudFront resources"). The support case sat for days with no guidance. What worked: I deployed the site without CloudFront first (API Gateway + Lambda on a custom domain), so it was live at its real address. CloudFront was approved about a day later. AWS never said a live site was needed, so if you're stuck, put the site up another way first and give its address in the case.
I got into AWS Activate and received $10K in credits. We’re building an AI product, so Bedrock was the obvious place to spend them.
But model access is blocked on my account. I’ve opened 3 support tickets asking them to turn it on. Every time, support refused and sent me to sales. I contacted sales and followed up, and never heard back.
So the $10K sits there unused while I pay out of pocket for other providers.
I’m not asking for more credits. I just want to use the ones I was given. Has anyone in Activate gotten Bedrock access unblocked?
I dont know what bad luck struct during my hectic day , just last week they validated my aws resources. Yesterday i got email from their fraud department saying i must submit id and estatement , so i did. Few hours later , my aws acc got suspended , said that i never submitted.
Has anyone dealt with this exact sequence ?
Nov 14 : I uploaded the requested verification documents through AWS secure link. AWS emailed me a receipt listing both filenames and said the submission was pending review.
Nov 15 : AWS emailed me saying it hadnt received the requested documents and had suspended my account. The notice says the account will be closed and the data permanently deleted if AWS doesnt receive the documents by Nov 20.
Ive tried every sign in route I could find and cant access the console or signed in Support Center. Ive already submitted a request through AWS public support form.
If this happened to you , did you get your account and existing resources back ? What actually got the verification team to pick it up ? Did they find your original submission , or did you have to upload the same files again through a fresh link ?
Id appreciate hearing from anyone who got the closure deadline put on hold while verification was still pending.
r/aws • u/csantanapr • 1d ago
Run agentic AI, multi-tenant SaaS, and regulated workloads with the isolation of a dedicated EC2 instance and the simplicity of a Kubernetes pod. Nitro Sandboxes give each pod a hardware-enforced security boundary, built on the same Nitro System that isolated EC2 instances from each other
r/aws • u/MinuteGate211 • 1d ago
I have two projects using route 53. Both of these have project code in Upsun. They are both Drupal 11 sites. The first, I'm not concerned about, has A records supplied by Upsun and Name Servers provided by AWS. The second project has more history. It originally ran on Bluehost. I transferred it to Lightsail, which controlled the DNS. Bluehost still reports it as an "External Domain". I assume it is okay to delete that domain from Bluehost. I have since stopped the Lightsail instance and moved the code to Upsun. My concern is with Route 53. Unlike my first project, when I check the DNS records Route 53 reports them as "Simple" but the information for record A reports the correct values supplied by Upsun.
Do I need to specifically enter the A record values in Route 53 before deleting the stopped Lightsail instance? I'm concerned that Lightsail's domain record values are still being used.
r/aws • u/MrCashMahon • 2d ago
A lot of AWS cost updates this week in backup, billing, storage, and database efficiency.
AWS Backup makes EKS restores less manual: AWS Backup can now apply resource modifiers during Amazon EKS restores, so restored workloads need less cleanup after the restore. That saves time and reduces the chance of manual mistakes during recovery. Source
AWS Billing now pulls more cost views into one place: AWS Billing and Cost Management can now use Billing Conductor and Billing Transfer views as source views for custom billing views. That makes it easier to work from one billing view across Cost Explorer, Budgets, and the billing console. Source
AWS makes database pricing and performance a little easier to tune: Aurora and RDS now support Graviton5-based R9g instances, with up to 30% better performance and up to 22% better price-performance than Graviton4. Source
AWS lowers the bar for cheaper elastic file storage: FSx for Lustre Intelligent-Tiering now has minimum provisioned throughput capacity and metadata IOPS reduced by 75%. Source
AWS gives Bedrock AgentCore a smarter default runtime: New AgentCore runtimes now default to a next-generation model that scales compute and memory with demand and scales idle agents to zero. Source
AWS Backup adds a cheaper long-term archive path: AWS Backup can now move Amazon EBS snapshots into EBS Snapshots Archive. Source
AWS CloudWatch alarms can now drive scaling from PromQL: CloudWatch PromQL alarms can now trigger EC2 and Application Auto Scaling policies. Source
AWS CloudWatch Logs now supports account-level retention policies: CloudWatch Logs can now apply retention rules at the account level across all or selected log groups. Source
AWS RDS for SQL Server gets new instance options: RDS for SQL Server now supports M8id and R8id instances with custom Intel Xeon 6 processors and local NVMe SSD storage. Source
AWS Athena adds built-in usage visibility: Athena system tables now capture query usage data for observability, auditing, and usage analysis. Source
AWS makes document database throughput go further: DocumentDB Serverless platform version 4 now delivers up to 35% higher throughput. Source
Source: FinOps Weekly Newsletter
AWS doesn't publish a container image for the new AWS Emulator. The Docker guide gives you a Dockerfile (x86_64 only, you swap the RPM by hand for arm64), and building from source needs ~100GB of disk. I wanted it in CI without any of that, so I built an image and a GitHub Action. While testing it from six SDKs I hit a few things worth knowing even if you never use my image:
JS SDK v3 sends SQS calls to real AWS. The emulator returns queue URLs on sqs.<region>.amazonaws.com, and v3 follows the queue URL host. Set useQueueUrlAsEndpoint: false. Python, Go, Java, .NET and Rust were fine.
Use 127.0.0.1**, not** localhost**.** With localhost, the JS SDK switches S3 to virtual-host style and fails with ENOTFOUND <bucket>.localhost.
Any Region name works, even xx-fake-1**.** A typo in the Region won't fail your tests the way it would on AWS.
The certificate only covers localhost**,** 127.0.0.1 and ::1**.** Another container can't call it by its Compose service name. Run the client in the emulator's network namespace (--network container:<name>) instead.
No persistence and no IAM policy evaluation. Restart = reset, and don't use it for permission tests.
The image, if it helps: amd64 + arm64 (works on Apple Silicon as-is), Amazon Linux, Debian slim and distroless variants on GHCR, Docker Hub and Quay, rebuilt within ~1-2h of each upstream release (pin a build tag or digest). The build verifies AWS's RPM/DEB signatures, and the images are cosign-signed with SBOM and SLSA provenance. Unofficial, not affiliated with AWS.
https://github.com/xSAVIKx/aws-emulator-docker
In GitHub Actions the action starts it and exports AWS_ENDPOINT_URL, the CA bundle and credentials, so SDK tests run unchanged (telemetry off by default):
- uses: xSAVIKx/run-aws-emulator@v1
- run: aws sts get-caller-identityHas anyone run it on self-hosted runners or Podman? I've only tested GitHub-hosted runners and rootless Docker.
r/aws • u/Viberjob • 1d ago
Hi everyone!
I'm a college student working on an AWS project focused on infrastructure monitoring and configuration drift detection, and I'd really appreciate some feedback.
My instructor encouraged me to reach out to people with experience in the field, hear their perspectives, and get some guidance on the direction I should take with this project. So I thought this would be a good place to ask.
A bit of background:
To be honest, I originally wanted to build something relatively simple and beginner-friendly. However, our instructor doesn't want us to just check off all the requirements in the assignment. He also wants us to build something that has an actual real-world use case, rather than simply recreating something that already exists.
The problem is that I'm still relatively new to AWS, and I don't have enough experience with real-world AWS environments to easily come up with a genuinely useful project idea on my own and an that I will know how to create.
The project idea – DriftDoctor:
The project addresses a situation where AWS resources are initially deployed using Infrastructure as Code (CloudFormation), but someone later makes manual changes through the AWS Console.
For example, someone accidentally opens SSH access to the entire internet or changes an S3 bucket configuration.
DriftDoctor is designed to detect these changes:
EventBridge Scheduler triggers a Lambda function once a day.
Lambda uses CloudFormation Drift Detection to compare the deployed resources against their original templates.
CloudTrail is queried to identify who made the change and when.
If drift is detected, Amazon Bedrock analyzes it, assigns a severity level, explains the potential impact, and suggests what to do.
The AI response is validated against predefined safety rules in the code.
An email report is sent through SNS, and the results are stored in DynamoDB.
The system is read-only. It doesn't automatically modify or fix anything.
For now, it monitors a small CloudFormation-managed test stack rather than an entire AWS account.
The problem I'm having:
I presented the idea to my instructor, and he raised an interesting criticism:
Isn't the whole point of DevOps and Infrastructure as Code to prevent these situations in the first place?
For example, why allow users to make manual changes through the AWS Console at all? Wouldn't restricting console write access and enforcing changes through a controlled deployment pipeline be a much simpler and better solution?
This made me question whether building a system that detects these changes after they happen is actually useful, or whether I'm just creating an unnecessary layer.
I'd love to hear your thoughts:
Is there a legitimate real-world use case for a tool like this? For example, emergency changes, legacy infrastructure, or situations where manual changes cannot be completely avoided?
Would you approach this differently, perhaps focusing on preventing configuration drift rather than detecting it?
Is adding AI to explain changes, assess their severity, and provide recommendations actually useful in this context, or is it overengineering?
Given that I'm still learning AWS, would you recommend a different direction for a project that is relatively beginner-friendly but still solves an actual problem?
I'm not trying to build an enterprise-grade product. I'm trying to learn, build something meaningful, and understand how these problems are actually handled in real AWS environments.
I'd really appreciate any honest feedback, advice, or suggestions.
Thanks!
r/aws • u/sebasavl25 • 1d ago
I am trying to try out bedrock since I have an important using Bedrock. But regardless of which model I select I get this for one week.
My account is new, with 200 credits (100 free & 100 for completed tasks) and billing enabled .
I have been facing this for more than 7 days, alreadyy requested to increase service quota since all have 0 quotas, no result yet though, my case is not even assigned.
What else can I do?
Hi everyone,
Our startup received $1,000 in AWS Activate Founders credits a few months ago.
During a call with an AWS representative, we were told we could request an increase to $5,000 after consuming more than 50% of our initial credits.
We've now used approximately 75% and submitted a request for additional credits, but it was rejected because we had previously received AWS Activate credits.
I'm wondering:
Is there a separate process to expand existing credits from $1,000 to $5,000?
Do we need to go through an AWS Activate Portfolio Provider?
Has anyone successfully received additional credits after their initial Founders award?
Would appreciate any advice or experiences. Thanks!
r/aws • u/Green_Crypt • 1d ago
Imagine renting an expensive car. You hand over your passport, link your credit card, pass every verification, and set off on a long trip. Halfway there, the car locks itself on the highway: "Account suspended." The doors won't open, your things are inside, and nobody answers the phone. That is my AWS experience this month.
Timeline:
Nov 3: account suspended over an invoice my card payments seemed to cover. I uploaded ID and payment documents the same day, plus sent a $700 bank transfer as Advance Pay.
Nov 6: invoice charged to my card and settled; the account was reactivated. Tokyo region stayed blocked.
Nov 11: suspended again for a "failed payment". The Payments page shows $0.00 outstanding, the invoice is marked Paid, and the $700 Advance Pay is still unused.
Nov 12: support forwarded the case to the verification team, which "communicates only via email" and asked me not to open a chat or call. Since then: silence, case still "Unassigned".
My EC2 instances and their data have been unreachable for days and my work has stopped.
Has anyone been through a repeated suspension like this? How long did the verification team take, and is there any way to escalate on Basic Support? @AWSSupport on X already has the case number.

The irony: the Preview panel in the display settings still shows the old dark UI, with the navy top bar and the clear contrast between sections. That is exactly the UI I would prefer since I am very used to it, and it is the one I no longer get after I click Save.
In the current dark mode, without those colors, everything blends together. It is hard to navigate, and after a while it gives me a headache, so I cannot concentrate on work.
This is on macOS
Two questions:
Is this a bug, or is the preview just outdated?
Is there any way to get the dark UI from the preview back, for example a setting or another browser?
r/aws • u/OkLetsDoIt124 • 2d ago
Seeing random invalid encrypted view errors using codex through bedrock, all set in us-east-1. Works fine one time, goes back to the error the next. Nothing posted on their status board about it. Anyone else?
r/aws • u/Wild_Description3941 • 2d ago
Need someone to look into our Quota Request, It has been some time now. Even requesting for a live chat does not work, I have been sitting here for more than a day now, and still no live support.
r/aws • u/illuminatedtiger • 2d ago
Was finding it really useful, especially with the filter functionality. Where can I find it now?
r/aws • u/Seanw265 • 3d ago
r/aws • u/MCRG_2005 • 2d ago
I recently created a fresh AWS account, completed the payment verification, and tried to use Amazon Bedrock for the first time.
Unfortunately, I haven’t been able to make a single successful request.
Every API request returns a ThrottlingException, and when I checked my account’s allocated quota, it showed 0.
It’s been almost two weeks now, and nothing has changed.
I’ve already opened two AWS Support tickets explaining the situation. However, both times, the issue was treated as a standard quota increase request. That’s not really the problem I’m trying to report.
My concern is that the account appears to have zero allocated quota from the beginning, making Bedrock completely unusable. I’ve verified the payment method, but I still seem to have no way to get past this initial restriction.
I understand that AWS may have onboarding restrictions or eligibility checks for new accounts, but there should at least be a clear explanation or a path to resolve the issue.
Has anyone else experienced this with a newly created AWS account?
Is this a known restriction for new AWS accounts?
Does Bedrock require some additional account verification before quotas are allocated?
Is there a specific AWS Support category or escalation path that actually addresses this issue?
I’d really appreciate hearing from anyone who has managed to resolve this. At this point, I’m just trying to get Bedrock working for the first time.
r/aws • u/allixsenos • 3d ago
I maintain cfnrain, a community fork of AWS's archived rain CLI for CloudFormation. Real-AWS integration tests are slow and painful to run in parallel, so I tried AWS Emulator (1.0.322) the night it came out.
Works well:
CloudFormation create/update/delete, change sets, rollbacks with real event reasons, termination protection
Express mode and Early Validation
SQS, SNS to SQS, EventBridge to SQS, Lambda (inline Python), Step Functions, DynamoDB with GSI, CloudWatch Logs, KMS, Secrets Manager
Watch out for:
CREATE_COMPLETE for resources that don't exist in the service API: CloudWatch alarms, ElastiCache, CloudFront, ALB/NLB, ECS. CloudFront and ELB return synthetic DNS names.
Updates return NotImplemented for API Gateway, ECR, WAFv2 and VPC gateway attachments
IAM support is spotty at best: with its own credentials it allows everything, whatever your policies say (documented)
Lambda's runtime only builds SDK clients for a handful of services; SNS and S3 aren't among them
ACM DNS validation not implemented, no StackSet instances
Telemetry is on by default (--telemetry off)
Filed 7 issues upstream with plain CloudFormation + AWS CLI repros.
Write-up with more detail and how I've implemented it: https://chaosguru.substack.com/p/aws-finally-made-an-official-local?r=3f5ebc
r/aws • u/GaryZhen • 2d ago
Recently, we noticed our account has been blocked because of a credit card issue, which caused previous payments not to go through. That is why we made a payment right away. But even after that, the account has not been activated at all.
We tried to send a new request and use live chat, but unfortunately, after one week, nobody has responded and the case has not been assigned at all.
I cannot imagine this: our data and our services are all on AWS right now, and AWS has had no response whatsoever. I cannot believe a huge company like this treats their customers this way, and the system is so old and hard to use.
r/aws • u/ckilborn • 3d ago
r/aws • u/Particular_Goal_6293 • 3d ago
Hey Reddit!
I built a website to make it easier to navigate the expo, learn about the exhibitors, and plan ahead. Live updates start Sunday the 29th, including Waze-like features of what’s happening on the ground.
FYI: It runs fully on AWS; no data is collected (unless you sign up), and it's fully run on AWS Credits :)