- 新しい順
- 投票が多い順
- コメントが多い順
Yes, Disabling All Active Receipt Rules Stops Billing for Incoming Messages, Amazon SES charges for incoming messages only when they match an address in an active receipt rule. So if you deactivate all receipt rules, SES will: • Still receive the email at the MX endpoint • But won’t process or store the message • And you won’t be billed for that message
If you deactivate all active receipt rules, then no incoming emails will be processed or billed, even if your domain is targeted by spam. SES only charges when an incoming message matches a rule with an action (like storing or forwarding). To protect against unexpected charges, simply remove or disable all receipt rules if you’re not expecting any inbound mail.
To safely prevent unwanted billing: Option 1: Disable all Receipt Rules Go to SES > Email Receiving > Rule Sets Set your active rule set to none, or deactivate/delete rules SES will drop the messages silently, and you won’t be charged.
Option 2: Add a spam filtering Lambda If you still want to accept certain mail but discard spam, create a rule with a Lambda action that: Rejects spam based on headers or sender Only forwards/stores legitimate messages
This adds a layer of cost control and logic before accepting delivery.
I'm not sure this is correct. Once the receipt rule with the lambda is executed, you're going to be billed as far as I read the pricing details. I wanted to make sure in the case of being flooded with unwanted mail I have a mechanism to stop being billed for it. Deactivating all active receipt rules/rule-sets would prevent that as the above answer and the pricing details information seems to indicate
I'm going create a billing alarm that publishes a message to an SNS topic and a Lambda action that then deactivates the receipt rule if the amount exceeds an unacceptable threshold. That should ensure I won't be billed anything excessive...