AWS is shaking up that model by releasing a JavaScript SDK that securely accesses AWS services from the browser, thus eliminating in some cases the need for any server-side code.

Additional Information/Context The ses documentation mention that using sdk the uint8array shouldn't be encoded, but it seems that within aws lambda the sdk expects the content be already encoded. Not ...

The AWS JavaScript SDK should detect $ {filename} in any field (including success_action_redirect) and avoid generating exact match conditions that would interfere with S3's variable substitution.

Node 18 support in AWS Lambda! They're also including v3 of the AWS JavaScript SDK now, which is great news if you're using that - one less thing to bundle in your deployments.