Why do I receive a "Invalid Amazon Configuration" error message when saving my Actions app configuration?

When updating the Actions app's configuration, especially when editing any Amazon Web Services information, administrators might receive the following error message upon saving the configuration.

Invalid Amazon Configuration

If this happens, here's a few things to try in order to fix the situation.

1. Ensure that a non-root user is being used, and if not, create one
   1. Login to your Amazon Web Services Management Console
   2. Go to the Identity and Access Management
   3. In the left navigation, click on Users
   4. On the Users screen, confirm that the user used in the Actions app's configuration is one of the users listed
   5. If no users appear, create a user through the Identity and Access Management system
      1. Click the Create User button
      2. On the User Details page, create a User Name, and click the Next button
      3. On the Set permissions page, in the Permissions options section, select "Attach policies directly", and in the Permissions policies section, type "AmazonSESFullAccess" into the search bar and check the box next to the AmazonSESFullAccess policy, and click the Next button
      4. On the Review and create page, click the Create user button
      5. On the Users page, click the name of the newly created user
      6. On the User page, click the Security credentials tab, and in the Access keys section click the Create access key button
      7. On the Access key best practices & alternatives page, select Third-party service, and check the confirmation box, and click the Next button
      8. On the Set description tag, just click the Create access key button
      9. On the Retrieve access keys page, save the Access key and Secret access key in a safe place for use by Soapbox Engage
      10. Use the new created user's access keys in the Soapbox Engage Action apps configuration section for AWS Key and AWS Secret. 
2. Ensure that the Amazon Web Services user you're using has full access to the Simple Email Service (Amazon SES)
   1. Login to your Amazon Web Services Management Console
   2. Go to the Identity and Access Management
   3. In the left navigation, click on Users
   4. On the Users screen, click on the name of the user that is associated with the Amazon API keys you've entered in the Actions app
   5. If "AmazonSESFullAccess" is not listed as a Permissions section for the user...
      1. Click the "Add permissions" button
      2. On the Add Permissions screen, select "Attach existing policies directly"
      3. Search for "AmazonSESFullAccess"
      4. In the results, tick the checkbox next to AmazonSESFullAccess
      5. Click "Next" button
      6. Click "Add permissions" button
3. Ensure that the AWS Host URL is formatted properly in the Actions app configuration
   1. Login to your Soapbox Engage administrator
   2. Go to Actions > Configuration
   3. On the Actions Configuration page, ensure that the AWS Host URL is one of the following values based on the organization's AWS region

      1. US East (Ohio) - https://email.us-east-2.amazonaws.com

      2. US East (N. Virginia) - https://email.us-east-1.amazonaws.com

      3. US West (N. California)- https://email.us-west-1.amazonaws.com

      4. US West (Oregon) - https://email.us-west-2.amazonaws.com