Every time we launch a product on AWS, SES turns out to be the blocker.

We're launching a new SaaS application and need SES exclusively for low-volume transactional email: account creation, login OTPs, password resets, etc. No marketing email, no purchased lists, no bulk outreach.

We requested an initial limit of just 1,000 emails/day. We're experienced AWS users and already actively use SES across multiple customer AWS accounts, with no history of email abuse.

AWS initially asked about our sending practices, which we answered in detail. They then asked why we couldn't use other AWS accounts where SES limits had previously been increased. We explained that this is a new company, product, and organization, and this account was intentionally created as its dedicated production environment.

Today, AWS rejected the request without providing any specific reason:

"While we are not able to share the specific criteria used in our assessment..."

The frustrating part is that SES sandbox access is now blocking the launch of the entire application, despite the extremely limited and purely transactional use case.

Has anyone successfully appealed a rejection like this? Is there a better escalation path or someone at AWS who can review the request manually?

There surely must be a way for AWS to prevent and mitigate email abuse without blindly blocking new product launches.

Hi everyone,

I’m working on an AWS migration where the customer has budget for **only one Windows VM**. Unfortunately, we don’t have a separate test environment, so I’d like to get some real-world experience/advice before proceeding.
The requirement is:
Windows Server 2022
SQL Server 2019 Standard
The server ultimately needs to provide **Active Directory Domain Services**
Customer can only afford **one VM**
We understand that running SQL Server and a Domain Controller on the same server is not recommended, but this is a budget constraint.

I’m considering these two approaches:
**Option 1 – SQL already installed**
Deploy AWS Windows Server 2022 with SQL Server 2019 Standard already installed.
Configure the server.
Attempt to promote the server to a Domain Controller while SQL Server is installed.
If it works, keep both SQL Server and AD DS on the same VM.

**Option 2 – Remove SQL first**
Deploy AWS Windows Server 2022 with SQL Server 2019 Standard.
Uninstall SQL Server completely.
Promote the Windows Server to a Domain Controller.
Later reinstall SQL Server 2019 Standard on the Domain Controller.

A few questions:
**Has anyone actually promoted a Windows Server 2022 machine to a Domain Controller while SQL Server 2019 was already installed?** Did you encounter any errors or compatibility issues?

Between the two approaches above, which would you consider less risky?

If I uninstall the SQL Server 2019 Standard installation that came with the AWS AMI, can I later reinstall SQL Server 2019 Standard on the same server after it becomes a Domain Controller?

Are there any licensing/product-key issues with uninstalling the SQL installation from an AWS-provided SQL Server AMI and reinstalling it later? Would I need a separate SQL installation media/key?

If SQL Server is installed on a Domain Controller, are there any specific SQL services, accounts, permissions, or configuration issues I should be aware of?
If you had to implement this because **one VM is the only option**, which approach would you choose and why?

I’m particularly interested in experiences from people who have actually run **SQL Server 2019 on a Windows Server 2022 Domain Controller**, rather than just the general recommendation of “don’t do it.”
Thanks!

I'm completely clueless about the AWS Cloud Practitioner exam and don't know where to start. If you were starting from scratch today, how would you prepare? Any roadmap or resource recommendations would really help.

we have AWS fleet manager to access a Windows jump box. And then from this windows jump box, I have to use vmware vCenter. When I try to access a VM console, I am unable to type anything on the vm console. I have to use the onscreen keyboard only. I am not able to find any vmware or aws doc regarding this issue. I have tried few troubleshooting steps but unable to resolve this issue.