4 ms·
When the documentation says "this may cost you money" what they really mean is "this will cost you a lot of money the moment your email address gets onto any sp
by mark242 5y ago
When the documentation says "this may cost you money" what they really mean is "this will cost you a lot of money the moment your email address gets onto any spam lists". The number of lambda invocations will go through the roof, and even if you're able to catch 90% of the spam before dumping messages into S3, the cost of putting a message into a bucket will make your bill skyrocket periodically as spammers temporarily find their way past SES's built-in filters, which happens every so often.
- maerF0x0 5y agodepends how you define a lot of money. How much would this cost to receive 30k messages per month?
- mark242 5y agoAssuming a default message size of ~10kbytes the SES pricing is about $6 for the connections plus the chunks. Your lambda pricing is negligible and the S3 pricing gets you another dollar or so. But you're operating at the wrong scale-- 30k messages to a domain can happen in an hour by a spammer doing a directory attack. The point is that this solution is extremely open to abuse that happens all day every day over SMTP. Without a fixed-cost firewall to reject messages and only allow clean messages through to this solution, you are going to have escalating costs.
- megous 5y agoThat's a lot of money for a LKML subscription. :)