A bit tangential, but please for all that is good in this world, stop depending on static AWS IAM User keys in an integration product. https://docs.sendwithses.

A bit tangential, but please for all that is good in this world, stop depending on static AWS IAM User keys in an integration product. https://docs.sendwithses.com/how/how-to-generate-aws-keys-for-sending-emails-programmatically-via-simple-email-service-ses- https://docs.sendwithses.com/how/how-to-generate-aws-keys-fo.... You should absolutely be using cross-account roles which, with role assumption, vends ephemeral credentials when you need them. https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cr... A compromise of your vault (and hopefully not remote code execution) means the attacker at least can't blast a billion emails out at someone elses expense.