johanneswu

You can now use a account-level suppression list to override the global suppression list though.

> If an address is on the global suppression list, but not on your account level suppression list (which means you want to send to it), and you do send to it, Amazon SES will still attempt delivery, but if it bounces, the bounce will affect your own reputation

[1] https://docs.aws.amazon.com/ses/latest/dg/lists-and-subscrip...

Without paywall https://archive.is/tzEcD

I don't know ryandamm, so I can't judge whether he is pro- or anti-vax, but you should be fact checking every article before sharing it.

Doing basic checks like "what else did the authors publish" seem fairly sensible.

Those are also our biggest pain points together with slow deployments (cloudfront distributions can take 10-20 minutes to update, which is required to rollout a new version) and no support for lambda aliases. We forwarded that to our contacts at AWS, please also do that :-)

Disclaimer: I work at Contentful.

If you are already using Cloudflare that is correct, if you don’t that is an alternative.

Adding another vendor into your stack can often come with none engineering complexity (e.g. data protection forms, contractual requirements from customers another vendor you need to work with, etc.) so this is an alternative to stay in AWS when you already use it.

Disclaimer: I work at Contentful.

I completely agree. If building a read-only fallback would require a lot of engineering and added a lot of complexity I would also say it is overkill, but as this solution doesn’t (happy to argue about that). It was an acceptable tradeoff for us as we already replica the underlying s3 buckets for disaster recovery as you already pointed out.

We also run our underlying Content Delivery APIs in two AWS regions so this was a logical extension.

If the added complexity is worth for your use-case can only be decided by you and I hope the article provided some guidance around that vs. just being a copy & paste gist.

Source: I work at Contentful.

You are correct, this has been implemented before Origin Groups have been released and they might be a viable alternative, but we haven’t tested them yet.

Source: I work at Contentful.

Now on https://status.aws.amazon.com/

Intermittent DNS Resolution Errors

We are investigating reports of occasional DNS resolution errors with Route 53 and our external DNS providers. We are actively working towards resolution.

There is a technique called "memory ballooning" http://www.vmwarearena.com/vmware-memory-management-part-3-m..., which is probably also used by HyperV to free memory again.