- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
The cost difference between the estimate and invoice likely boils down to a few possibilities:
-
Free Tier Exceeded: SES has a free tier with limits. If you exceeded those limits (147,000 emails might have done it!), you'd be charged for the additional usage.
-
Unexpected Sending: Double-check if any processes besides your app are using SES unexpectedly. Consider server logs or temporary credentials for clues. Finding Recipient Details (Currently Limited):
Unfortunately, SES doesn't offer a recipient list view like Mailgun or Mailtrap. However, there are workarounds:
Review sending code and analyze the code sending emails in your PHP app to understand recipient details.
Optimizing SES Usage:
Separate Server Notifications: Consider using a dedicated service for server notifications instead of SES. This can isolate notification emails and prevent them from contributing to your SES bill.
Review Sending Frequency: Analyze if your PHP app sends unnecessary emails. Optimize code to send emails only when truly required.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr