SES Production Access Denied — Single Recipient Transactional System — Registered LLC

Hello.

If the system only sends emails to your Gmail account, I think a sandbox environment should be fine.
Amazon SES in a sandbox environment has a limit of 200 emails that can be sent in 24 hours, but as long as the emails are verified, it will be possible to send them to the outer email address.
https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html

For sending authorization, neither you nor the delegate sender can send email to non-verified email addresses.

Also, if you're only sending emails to your email address, I think using Amazon SNS for pub/sub message delivery would be fine instead of Amazon SES.
https://docs.aws.amazon.com/sns/latest/dg/welcome.html

I understand your frustration with the SES production access denials. While I don't have specific information about your exact situation in my sources, I can provide guidance on the SES approval process and potential next steps.

Amazon SES production access requests are evaluated based on several factors including your use case, sending practices, and compliance with AWS policies. The review process is designed to protect the service's reputation and ensure senders follow email best practices, even for low-volume or single-recipient scenarios.

For denials, here are your options:

Appeal Process: If your production access request is denied, you can submit a new request with additional information addressing the concerns raised in the denial. Make sure to clearly articulate:

• The transactional nature of your emails (trading alerts)
• That you are both the sender and sole recipient
• Your bounce and complaint handling procedures (even for self-sending)
• How you'll maintain list hygiene and handle any potential issues

AWS Support: You can open a support case specifically about your SES production access denial. If you have a paid support plan (Developer, Business, or Enterprise), you'll have access to technical support that may provide more detailed guidance on why your request was denied and what specific information could strengthen a resubmission.

Documentation Improvements: Even though you've provided business documentation, consider adding:

• A detailed explanation of your email workflow and infrastructure
• Confirmation that you understand and will comply with email sending best practices
• Details about how you'll monitor sending metrics even with a single recipient

The fact that you have a single recipient doesn't automatically exempt you from the review process, as AWS needs to ensure all senders understand proper email practices and won't change their use case after approval.

Keep your requests professional, detailed, and focused on demonstrating that you understand email deliverability best practices and AWS policies, even if your current use case is limited in scope.