Follow the tutorial here with your AWS account created previously. We're going to use a Lambda function in AWS to run our filthy, low$-$down spamming enterprise $($sorry$...$ our direct response marketing enterprise$).$ Lambda is very cool because you don't have to setup a server $($it$\text{'}$s sometimes called 'serverless computing'$).$ We just put a little bit of code in there and AWS runs it for us$.$ We just need to configure a few permissions and validate the email address.

You'll need to click around a bit to find all of the menus referenced in the tutorial. AWS can be a little finicky sometimes $-$ you have to "Deploy" any changes to the code, you need to make sure you have clicked to "Create" the permission addition described in the tutorial, and so on$.$

Label your test event name as something with your name in it$,$ like "RyansTestEvent". Also create a more realistic Subject and Body to hopefully have more success passing the spam filter.

There is an error with a variable name in the code. and you'll need to re$-$type some of the quotes in the code. I also had to use the AWS region from my verification email $($mine was us$-$east$-2).$ I was able to use my verified email as both the sender and recipient. If you get a success message in the Test tab but don't receive the email, check your spam, because it will likely be marked as suspicious coming from your own email address.

Don't surrender and ask for help at the first sign of trouble or first error message $-$ you are the troubleshooter.

Save a screenshot of your 'Execution Result' tab from the Test showing success and upload it here. Your name should appear somewhere on the test event as described above.

Now you can send out your home refinancing offer emails to your closest $100,000$ friends! $($Don$\text{'}$t do that$).$

You'll notice that the code has 'async' and callbacks and promises. If you aren't familiar with this model, when a function may take some time $($like sending an email$),$ it can 'call you back' when it is done. This is 'asynchronous' behavior, and is described in Node.js $($server side javascript$)$ in this article.