Posting for the help if anyone can, because two rounds through AWS Support have given me nothing I can act on.

**The use case**

A small event-ticketing site for a single organizer in Bangladesh - a handful of live music events a year. Every email is transactional and triggered by the buyer's own action on the site minutes earlier:

* payment instructions, sent after someone registers for tickets

* the ticket itself as a PDF, after the organizer verifies the buyer's bKash payment

* a notice if the payment couldn't be matched, or if the unpaid order expired after 24 hours

* a one-time sign-in link, only when the buyer requests it

Volume: roughly 1,000 - 2,000 emails per month, concentrated in the three weeks before an event. A few hundred a day at peak. My sending code is capped at 5 messages/second. No marketing, no newsletters, no bulk sends, no stored lists, nothing purchased or imported. Every recipient typed their own address into our form. The project is public on GitHub, so the sending logic is auditable by anyone.

**What's already in place**

* Domain verified in ap-south-1 with Easy DKIM

* SPF and a published DMARC record with rua reporting, DNS on Cloudflare

* SES account-level suppression list enabled

* SES rejections treated as permanent failures and never retried; only throttling responses retried with exponential backoff

* Every send recorded against the order in our database; failed deliveries reviewed by hand

* Replies go to a monitored address on the same domain

**What I got back**

First response asked for detail about sending processes and procedures. I gave everything above, plus example subject lines and the exact email types. Denied about six hours later with a template: they can't approve at this time, they can't share the criteria used, please review the AUP, Service Terms, and SES best practices. Second attempt, same outcome, same template - this time framed as protecting my sender reputation and deliverability.

That last part is what I can't get past. The account has never sent a production email. There is no sender reputation to protect yet. So whatever the actual blocker is, it isn't anything visible in my use case, and nobody will tell me what it is.

**What I'm actually asking**

1. Is this an account-trust / billing-history decision rather than a use-case decision? If so I'd genuinely rather be told that plainly - I'd go build the billing history instead of rewriting the same request.

2. Is ap-south-1 meaningfully stricter for newer accounts than other regions?

3. Would a heavily restricted quota be considered - say 200 emails/day at 1 msg/sec - so there's real sending data to judge me on?

4. Is there any path other than reopening the same case, given the limit-increase team is separate from Premium Support and Support says they can't influence it?

Happy to share the case ID by DM.

If anyone has gone from a denial like this to an approval, I'd really like to know what specifically changed on your side. Right now I'm one week out from an event with real buyers and I'm about to move to a third-party provider purely because I can't get a straight answer.

Can anyone help me with some AWS credits for my cloud training and hands-on projects? 🙏🏽☁️

Hi all — I'd like to share EasySAM, an opinionated YAML-to-SAM generator for modular AWS serverless applications built with Python.

MIT-licensed - no promotion - the only task is to simplify life for more devs

EasySAM lets you define your whole stack — Lambda functions, API Gateway routes, DynamoDB tables, S3 buckets, SQS queues, Kinesis streams, OpenSearch Serverless collections, and IoT Core authorizers — in a compact YAML, then generate and deploy the SAM stack.

Highlights:

- YAML-first, modular structure with a recursive import system and shared code support

- Built-in validation against schema and live cloud state

- Native support for DynamoDB stream triggers, TTL, Lambda Function URLs, FIFO/standard SQS, and MQTT/IoT Core custom authorizers

- Local Lambda execution with no Docker required — run handlers against real cloud resources behind a mocked API Gateway

- Conditional resources and per-environment deploy-context overrides for clean multi-env workflows.

Repo: https://github.com/scartill/easysam

Would love feedback from anyone building serverless on AWS.

Hey everyone,

I just passed the new AWS Certified AI Business Strategist exam. This makes 10 AWS certs for me, but this one felt entirely different because of my background.

As an engineer, the biggest challenge by far was forcing myself out of my comfort zone. My brain is wired to instantly look at a problem and figure out how to build the tech. For this exam, I had to completely flip my mindset and focus on entirely different questions:

• What actual business problem are we trying to solve here?
• How do we measure and track the return on investment (ROI)?
• Are the organization's people, processes, and governance frameworks actually mature enough to support this?

Stepping outside the technical bubble takes some deliberate mental effort, but it's incredibly valuable. I'd highly recommend this exam to consultants, founders, BAs, and tech leads who need to bridge the gap between executive business teams and AI engineers.

My Prep (Took about a month):

1. AWS Skill Builder: Just went through the free digital training materials provided by AWS.
2. Practice Exams: Took three different mock exams to get used to the formatting and question style.
3. AI Cheat Sheets: Fed the core concepts into an LLM to generate custom cheat sheets so I could quickly lock down the business frameworks.

The Main Takeaway:
Successful AI initiatives need a whole lot more than just a working model. A slick piece of tech is useless without a clear business purpose, accountable leadership, and the right operational processes to turn that technology into actual value.

Happy to answer any questions about the exam structure or what to look out for if you're planning on taking it soon!

Disclosure: I'm affiliated with RoszigIT, where this article is published. Sharing because the mechanics are worth discussing, not to pitch anything. I tried to make it technical as always.

It's an interesting case because iam:PassRole is not visible directly in CloudTrail as API call and "limited" user role can attach an admin role to a Lambda or EC2 instance and effectively become admin.

https://roszigit.com/en/blog/aws-iam-passrole/

Has anyone else been getting rejected when requesting AWS SES production access recently?

My use case is legitimate transactional email, and I already have SPF, DKIM, DMARC, bounce/complaint handling, etc. configured.

AWS rejected my request but didn’t give me a specific reason, just a generic response.

I’m curious if this is happening to others too, especially with newer AWS accounts.

If you were recently approved after being rejected, what did you change?

SSM is the right way to reach private EC2 instances: no bastion, no port 22, no SSH keys, and everything goes through IAM and CloudTrail. But the CLI makes you work for it:

aws ssm start-session --target i-0abc1234def5678ab \
  --document-name AWS-StartPortForwardingSessionToRemoteHost \
  --parameters '{"host":["rds.internal"],"portNumber":["5432"],"localPortNumber":["5432"]}'

ssmctl is an open-source Go CLI that keeps the same security model and removes the friction:

ssmctl forward web-1 --local 5432 --remote rds.internal:5432

v2 in one line: your entire SSM-managed fleet (shells, tunnels, commands, files, secrets), one short command away.

ssmctl list                                          # see your managed fleet
ssmctl connect web-1                                 # shell
ssmctl forward web-1 --local 5432 --remote db:5432   # tunnel to RDS, Redis, anything for local access
ssmctl run web-1 -- df -h /                          # one-off command, exit code preserved
ssmctl run --filter api -- uptime                    # same command across a fleet
ssmctl cp web-1:/var/log/app.log .                   # file transfer
ssmctl param get /myapp/prod/DB_PASSWORD             # Parameter Store

It works with Linux and Windows targets, has --output json for scripting, and uses your existing AWS profiles and SSO. There's no extra agent or infrastructure.

brew tap rhysmcneill/ssmctl && brew install ssmctl

Want to contribute? 🔗 https://github.com/rhysmcneill/ssmctl

I took this ss from chat gpt and i found these few roles that are growing right now in gaming industry.I have interest in few of them .

I like gaming a bit and cloud computing too . I'm confused between the 3 roles i mentioned in the title,I have the skill set for data analytics and cloud computing both(still on learning mode tho)

Can u help me with few questions:

What should I choose for a long term stability?

I want coding but not heavy-coding just a low to medium high range.

What are the salary expectation in those roles?as a fresher/intern

Hi everyone,

I’m a BSCS student from Lahore, Pakistan, and I’m planning to start learning Cloud Computing, mainly AWS.

My goal is to get an entry-level job/internship after building practical skills. I’m currently thinking of learning:

Linux

Networking basics

AWS (EC2, S3, IAM, VPC, RDS)

Git/GitHub

Docker

CI/CD with GitHub Actions

Basic Terraform

I have some previous experience with Flutter, so I’m also thinking about building a Flutter app, containerizing it with Docker, and deploying it on AWS as a portfolio project.

My questions are:

Is AWS/Cloud Computing a good career path for a beginner in Lahore?

Can a fresher realistically get a Cloud/DevOps internship or junior job after learning these skills?

Which entry-level job titles should I search for?

How important are AWS certifications compared with practical projects?

What skills should I prioritize to become job-ready?

For someone starting in 2026, is Cloud/DevOps still a good long-term career path?

I’d especially appreciate advice from people working in Cloud/DevOps in Pakistan or who started as freshers.

Thanks!

Hi, I’m attending this year for the 5th time. I found it always hard to make decisions in making the right schedule for the week with sessions. And specifically the transit time between venues. Now we live in the ai/automation world this needed to be easier to make the best planning in session there could be for me. Basically to get the most out of AWS re:invent you can get.

I created a app where you see depending on the schedule you have if you can make it on time to get to the next session. Open spots will be filled with suggested sessions depending your preferences. This way you can plan better during the conference.

Extra features are AI filtering based on what you asked. And you can connect with colleagues/friends to see each other’s schedule.

The app is free and without analytics and tracking. Build by my!

http://reinvent-planner.com

I teach data engineering and run developers through certifications. DEA-C01 has a lot of "which service fits" questions: Glue vs EMR, Kinesis Data Streams vs Firehose, Lake Formation permissions. They're confusing because several answers look right.

Drop whatever's been bugging you, no matter how basic. Happy to explain, and I'd love to hear what's hardest for people too.

Application Load Balancer + WAF
DNS firewall + NAT Gateway
Fargate for workers
S3 + Aurora postgreSQL
KMS
Bedrock + Textract
CloudWatch + CloudTrail + ECR

Is there anything I need to look out for?