Getting Started / Hands-on / ...

Module 1. Customize the FROM address used for email communications with your users

Customize the FROM address used for email communications with your users

Build a serverless back end

Create a state machine

Deploy a RESTful API

Host a static website

Test your setup

Implementation Instructions

Follow the step-by-step instructions below to Customize the FROM address used for email communications. Click on each step number to expand the section. 

  • Step 1. Select a Region

    You can deploy this workshop in any AWS Region that supports all the services used, which include Amazon AppStream 2.0, Amazon S3, Amazon SES, AWS IAM, AWS Lambda, AWS Step Functions, and Amazon API Gateway. The supported Regions that you can choose from are:

    • US East (N. Virginia)
    • US West (Oregon)
    • EU (Frankfurt)
    • EU (Ireland)
    • Asia Pacific (Tokyo)
    • Asia Pacific (Seoul)
    • Asia Pacific (Singapore)
    • Asia Pacific (Sydney)

    For more information about Regions, see the AWS Region Table.

    To complete these steps, you must have an AWS account. For more information about creating an account, see How do I create and activate a new Amazon Web Services account?

    1. Sign in to the AWS Management console at https://console.aws.amazon.com/console/home.
    2. Type your email address or your AWS account ID, and choose Next.
    3. Type your AWS account password, and choose Sign In.
    4. In the menu in the upper right corner of the console, select the AWS Region that you want.

  • Step 2. Add and verify a new email address identity in Amazon SES

    Amazon SES is an email platform that lets you send and receive email using your own email addresses and domains. Complete the procedure in this section to add and verify an email address identity using the Amazon SES console. You’ll use this email address for testing later in the workshop.
    If you have a new Amazon SES account, certain restrictions are applied to your account to help prevent fraud and abuse, and to protect your reputation as a sender. All new Amazon SES accounts are placed in the Amazon SES sandbox, and all sender email addresses and domains must be verified.

    Note
    Staying in an Amazon SES sandbox environment is sufficient when you are in the development and testing phases. However, we recommend that you move out of the sandbox if you deploy your solution to production. Doing so lets you send emails without any restrictions to users who request to onboard their applications to AppStream 2.0. For more information, see Moving Out of the Amazon SES Sandbox in the Amazon Simple Email Service Developer Guide.

    1. Open the Amazon SES console at https://console.aws.amazon.com/ses/
    2. In the navigation pane, under Identity Management, choose Email Addresses.
    3. Choose Verify a New Email Address.
    4. In the Verify a New Email Address dialog box, type the email address that you want to add and verify in the Email Address field. The email address must be one that you can access.
    5. Choose Verify This Email Address.
    6. A verification email is sent to the email address that you specified. It may take up to an hour for the email to arrive. The message contains the following subject line: Amazon Web Services - Email Address Verification Request in region RegionName," where RegionName is the name of the AWS Region that is selected in the SES console.
    7. When the verification email arrives, open the verification link in the message. Note: The link in the verification message expires 24 hours after the message is sent. If 24 hours have passed since you received the verification email, repeat steps 1 through 7 to receive another verification email with a valid link.
    8. You can check the status of your email address identity in the SES console. In the navigation pane, choose Email Addresses. In the list of email address identities, find the email address that you added, and confirm that the verification status for the address is verified.
Back to introduction
Next: Build a serverless backend