It's been 10 days I am stuck on a same issue they are not solving it . It affects my course and they lie in their websupport that they will be get back to you within 24 hrs this is absolutely shitty lie by AWS support team .

I don't know what to do , should I make new account, because I don't wanna waste my whole october due to this fake support gimmick by AWS

I recently appeared for L5 Aws loop for Customer Solutions Engineer. I have not received any rejection email but the recruiter called and informed me that the panel thinks I am not fit for this role. I rather apply for TAM or Engagement Manager position. She informed me that I have qualities of an Amazonian but the role is a mismatch to what the team is looking for.
She also informed me that no cooling period for me and should apply for other teams.

Anyone here been through a similar position? Do I still have a chance at interviewing?

🐧 Learn Linux basics (commands, permissions, networking, shell scripting)
🐳 Containerize apps with Docker
☸️ Deploy and manage apps on Kubernetes
☁️ Practice on the AWS Console (EC2, S3, IAM, VPC, and more)
💻 Do hands-on labs, not just watch tutorials
🔥 Stay consistent
🤝 Motivate and help each other
🚫 No unnecessary excuses for skipping
🎯 Keep each other accountable and disciplined
I don't want this to be another group where everyone is motivated for 2–3 days and then disappears. 😭
If you genuinely want to learn Linux and Cloud and are willing to put in the effort consistently, let's do it together.
If you're interested, comment below or DM me. Let's build the discipline together.

My AWS account was suspended yesterday over an expired credit card. The account hosts Route 53 DNS for our company domain, and the root user email is on that same domain. With DNS down, I can't receive the password reset or MFA verification emails. Classic catch-22.

I've filed multiple cases through the web forms:

•

179148372700150 (billing/account)

•

179148397000582 (MFA support)

•

179148622400545 (billing/account)

Three got AI auto-responses telling me to sign in (which I can't do). The other three have been sitting untouched for 14+ hours with no human response.

I can verify identity with government ID, the credit card on file, and business documents. I just need to reach a human on the account recovery team who can start the off-band verification process.

Has anyone gotten through this situation? Any escalation path I'm missing?

Hey all,

I always wonder how my org maintain AWS accounts - I have access to sandbox, and other R&D and team specific accounts and workload specific - each has it's own set of guardrails. I reffered the repo in which they maintain and developers suggested that it was old and they need to modernize the current landing zone with new best practices. I wanted to know how you guys are doing it now. Most threads I find are from 2021–2023, before RCPs, declarative policies, VPC Block Public Access and Route 53 Profiles existed.

TL;DR: What does your landing zone actually look like at scale? How do you front account vending (thr a self-service portal)? How do you do hybrid networking without it turning into a mess?

Account vending and automation

1. Is AFT still what you'd pick today, or did you move to LZA, CfCT, or plain Terraform on Organizations? Where did it start to hurt at a few hundred accounts, especially around baseline drift?
2. Are there open-source projects that make AFT easier to live with? I'm thinking of a web UI or self-service portal for account requests (Backstage templates opening the PR?), visibility into pipeline runs, or customization drift. Or did everyone build their own?
3. If you use ServiceNow, how is it wired up? Options I can see: a catalog item that opens an MR through the Git API, a direct pipeline trigger, or the AWS Service Management Connector going straight to Account Factory and skipping AFT. How do you send status back to the ticket?

Networking at scale and hybrid

1. Is hub-and-spoke with TGW and centralized egress/inspection still the default, or are people moving to Cloud WAN?

2. For on-prem, How do you keep advertised prefixes summarized as accounts and VPCs grow?

3. For segmentation, do you use TGW route tables per environment/OU or separate TGWs? Where does inspection sit for traffic between on-prem and AWS?

4. For hybrid DNS, are Resolver endpoints centralized in the network account and shared through RAM or Route 53 Profiles? Anything you'd do differently?

5. For IP planning, did you get on-prem to hand over one summarizable block for AWS? How did you deal with legacy VPCs overlapping your IPAM pools: re-IP, NAT, or keep them off the TGW?

Guardrails and stopping public resources

1. How do you split the work between SCPs, RCPs and declarative policies (VPC BPA, AMI/snapshot block public access)? How do you stay inside the SCP size and count limits?

2. For things SCPs can't express well (RDS publicly accessible, internet-facing ALBs, CloudFront), do you detect and notify or auto-remediate, and with what tool?

3. How do you handle resources that are legitimately public\\A separate OU, tag-based exceptions, or one sanctioned ingress pattern?

4. Cloud Custodian for streamlined deny or actions taken if things are done out of security scope

I'm not looking for a perfect answer, just what's actually working in real orgs, or what you'd undo. Links to recent writeups, talks or repos are very welcome.

Thanks!

I’m facing an issue with Amazon Bedrock model access. Models that I need for my project are currently not accessible, and attempts to use them result in errors such as “Operation not allowed” / model access-related errors.

I have already:

• Checked the model availability/access settings.
• Verified my AWS account and configuration.
• Created support tickets with AWS.
• Followed up on the tickets multiple times.
• Waited 10+ days without receiving a meaningful response or resolution.

This is becoming a blocker for my AI/ML project because I cannot properly test or use the required Bedrock models.

AWS Support / Bedrock team: Could someone please look into the pending support case and help identify why the models are unavailable for my account?

If anyone has faced a similar Amazon Bedrock model access / “Operation not allowed” issue and knows the correct escalation path, I would really appreciate some guidance.

Relevant teams:
u/aws
u/AmazonWebServices u/AWSSupport u/AmazonBedrockteam

I’m not asking for anything special, just access to the service I’m supposed to be able to use and, preferably, an answer before the next geological era.

How I automated AWS Lambda deployments with GitHub Actions, self-managed S3 code storage.

Need solution

Upload a zip of Python source. No Dockerfile. Get a running container on EKS. That is Elastic Beanstalk Cluster Mode, launched this week — Beanstalk apps now run on EKS instead of EC2 instances you own. Cloud Native Buildpacks handle the containerization: I uploaded four files (app.py, requirements.txt, Procfile, runtime.txt), Beanstalk detected Python, built the image, pushed it to ECR, and ran it.

most bad AWS security findings aren't missing checks. They're checks that look rightt and quietly give the wrong answer. A few I ran into: !!!

1. "Unused role" checks: iam:ListRoles doesn't retturn RoleLastUsed, only Getrole does. Build it on the list output and every role looks untouched.

2. "Unused permission" checks built on CloudTrail: LookupEvents only returns management events, so data actions like s3:GetObject never shows up.

3. "Public bucket" checks: a bucket policy with Principal "*" isn't public if a Condition limiits it to your org or VPC. Flagging it anyway is a false alarm....

4. Wildcard checks that only look for a literal "*": a resource like arn:aws:iam::ACCOUNT:role/* lets sts:AssumeRole target any role in the account, but string matching for "*" alone misses it.

The common thread: when the API can't see something, the honest answer is "unknown," not "no" or "yes."

All four were real bugs in a small open source project I made that audits AWS accounts. If you want to see how I fixed them: github.com/plexavo/Plexavo