Now I have to find a place to host number websites on 5 instances, 2 RDS databases and figure a new S3 style of management. If am moving, I am moving everything.

Read from the bottom up.

Hello,

Thank you for providing us with additional information about your Amazon SES account in the US East (Ohio) region. We reviewed this information, but we are still unable to grant your request.

We made this decision because we believe that your use case would impact the deliverability of our service and would affect your reputation as a sender. Furthermore, we also want to ensure that other Amazon SES users can continue to use the service without experiencing service interruptions.

We appreciate your understanding in this matter.

We value your feedback. Please share your experience by rating this and other correspondences in the AWS Support Center. You can rate a correspondence by selecting the stars in the top right corner of the correspondence.

Best regards,
Trust and Safety


Consultant (IAM)

+++++++

Wed Feb 26 2025
11:14:04 GMT-0800 (Pacific Standard Time)
This is very disappointing.

I am an AWS Certified Cloud Practitioner, building this website for a client.

I utilize SES and the AWS SDK PHP on other sites.  As a new customer, I start them with the free tier and them move them up on other AWS Services.  RDS, EC2, S3, VPC, etc.. simple things for small growing businesses.  It still generates money for AWS.

If I am unable to provide SES services as part of my placing customer on AWS, then I wouldn't be able to initiate their use of other AWS Services.  SES and registration emails, are an important part of  guiding the customer to many other AWS services.

If this is the case moving forward, then I will certainly have to consider alternatives.  E.G. GoDaddy Hosting, Microsoft Azure Services.

Please reconsider, as I am not a spammer, and SES is a legitimate and integral part of my business and this customers need.  Otherwise, I will have to put this customer on my API Key, which opens my business up to reputational risk.

Thanks,

Jason
XXX.XXX.XXXX


Attachments
Screenshot 2025-02-26 at 10.57.21 AM.png

+++++
Amazon Web Services

Wed Feb 26 2025
10:07:11 GMT-0800 (Pacific Standard Time)
Was this response helpful? Click here to rate:
Poor

Translate
Hello,

Thank you for providing us with additional information regarding your sending limits. We are unable to grant your request at this time.

We reviewed your request and determined that your use of Amazon SES could have a negative impact on our service. We are denying this request to prevent other Amazon SES customers from experiencing interruptions in service.

For security purposes, we are unable to provide specific details.

For more information about our policies, please review the AWS Acceptable Use Policy ( http://aws.amazon.com/aup/  ) and AWS Service Terms ( http://aws.amazon.com/serviceterms/  ).

Thank you for contacting Amazon Web Services.

We value your feedback. Please share your experience by rating this and other correspondences in the AWS Support Center. You can rate a correspondence by selecting the stars in the top right corner of the correspondence.

Best regards,
Trust and Safety

+++++
Consultant (IAM)

Tue Feb 25 2025
11:10:39 GMT-0800 (Pacific Standard Time)
Thank you for considering my request to increase sending limits. 

Please find below the detailed information requested: 

Email Sending Process: 
- Frequency: We send approximately 100 emails per day, we would never expect more than 1000 as our users are only using the system to access documents requested by them.
- Purpose: Our emails primarily consist of transactional notifications.
- Audience: Our recipient list is non-existent, we are not using lists for any sends with AWS SES.  A user's interaction with our website triggers a transactional email to the user interacting with our system. 

List Management: 
- Collection Method: We collect email addresses through [website sign-ups/purchases/etc.] with clear consent 
- Maintenance: We clean our user database every 90 days to remove inactive user or deals that have closed 

Compliance Procedures: 
- Bounce Management: We manually remove email addresses that bounce after based AWS Complaint information email sent by Amazon’s SES system notification
- Complaint Handling: We would address this on a case by case basis as all emails are transactional.  We have implemented ReCaptcha to CSRF to try and prevent spam/scam(ers) from signing up
- - Additionally we have implemented IP throttling, based on form type submission
- Unsubscribe Process: This would require the user to delete their account as we are only sending transactional emails via AWS SES
- Double Opt-in: We implement double opt-in for all new subscribers to confirm consent Email Content: 
- Our emails typically include:
- - Forgot password/password reset
- - Password was changed notification
- - Scheduling notification if selected in preferences
- - Automatic response that their form submission was received.
- We maintain consistent branding and sender information across all communications 
- We're sending from the verified domain: mydomain.com
- Our authentication systems include SPF, DKIM, and DMARC records 

Future Plans: 
- All email sends via AWS SES are intended to be system based/transactional emails.
- - Forgot password/password reset
- - Password was changed notification
- - Scheduling notification if selected in preferences
- - Automatic response that their form submission was received.
- We will be using either Hubspot or MailChimp for lead and marketing emails.
- We plan to implement [any upcoming improvements to your email program] Please let me know if you require any additional information to process this request.
- No commercial emails will be sent via SES

Attachments
Screenshot 2025-02-25 at 11.10.13 AM.png


++++

Amazon Web Services

Wed Feb 19 2025
15:28:07 GMT-0800 (Pacific Standard Time)
Translate
Hello,


Thank you for submitting your request to increase your sending limits. We would like to gather more information about your use case.

If you can provide additional information about how you plan to use Amazon SES, we will review the information to understand how you are sending and we can recommend best practices to improve your sending experience. In your response, include as much detail as you can about your email-sending processes and procedures.

For example, tell us how often you send email, how you maintain your recipient lists, and how you manage bounces, complaints, and unsubscribe requests. It is also helpful to provide examples of the email you plan to send so we can ensure that you are sending high-quality content that recipients will want to receive.

Note: In order to send email, you need a verified identity such as a verified email address or domain. For the best results, we recommend that you start with a verified domain identity. We ask that you have a verified identity prior to being granted production access. Learn more about domain and email address identities: https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html .

You can provide this information by replying to this message. Our team provides an initial response to your request within 24 hours. If we're able to do so, we'll grant your request within this 24-hour period. However, we may need to obtain additional information from you and it might take longer to resolve your request.

Thank you for contacting Amazon Web Services.

I'm writing a microservice that picks up an email address from the database (or a bunch of email addresses at times) and send them an email about updates related to the service.

I'm looking if Amazon's SES will help me complete my goal. But as my work is progressing, I'm questions related to why should I use SES for sending email? Can I not achieve the same by using my G Suite's email service and send an email using SMTP?

Please help. Why should I use Amazon SES?