Create smtp-unthrottle-request.md

docs/how-to/aws-vpc-setup/smtp-unthrottle-request.md

@@ -0,0 +1,43 @@
+# AWS Request Process to un-throttle SMTP traffic in AWS account
+
+## Overview
+
+This how-to provides information on the AWS request process lift the SMTP traffic (port 25) restriction in an AWS account. It is important to note that this request is different from an AWS support ticket or service quota request. It is a separate request to un-throttle
+port 25 traffic - the throttle is set to "0" by default. 
+
+## Requirements
+
+Before accessing and completing the SMTP request form, the following information must be gathered in conjunction with the system / account owner.
+
+1. **Who** -   System team or account owner Point of Contact.
+2. **Where** - Govcloud accounts and region(s) requiring smtp functionality and paired commercial account details. Although traffic will be within govcloud, the request is
+		   is submitted within the AWS commercial paired account. Document the email address for the shared AWS account inbox, i.e. "csvd.aws+cedsci-dev-ew@census.gov".
+3. **What** -  Resources in scope - Request for Lambda and EC2. If available provide at least one Lambda ARN or EC2 IP address / PTR DNS record that 
+		   will be sending the SMTP traffic. While AWS states this information is optional, it is helpful to include for AWS review.
+4. **Why** -   Detailed use case for justification – this will be supplied to AWS for review and lifting the throttle on port 25 (SMTP).
+
+
+
+## AWS Form Request Process
+
+1. After capturing the account details in step 2 above ("where"), log into the paired commercial account via the AWS Console.
+2. Duplicate the browser tab, and paste the following link:
+	[Request to emove email sending limitations](https://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/ec2-email-limit-rdns-request)
+3. Enter in the required information from Steps 2, 3, and 4. This includes:
+   - Shared inbox email address associated with AWS account
+   - Use Case Description, including language that specifies lambdas and EC2 instance usage. A recent example of an approved use-case is:
+
+      "This is a request for the paired govcloud account -<alias and account number here, us-gov-east-1 and us-gov-west-1 regions>
+       It is to facilitate the sending of email notifications and alerts from AWS Lambda functions and EC2 instances,
+       we require support for SMTP traffic across our accounts. This functionality is essential for integrating various services and 
+       maintaining effective communication with our stakeholders. These applications require the ability to send emails notifying stakeholders 
+       of successful processing, as well as information regarding any processing failures. Email recipients will be internal Census stakeholders." 
+   - If available Elastic IP address info and Reverse DNS reocrds. There can be multiple instances of these. This information is optional.
+
+4. Within 5-10 minutes after submission, AWS will send an email to the address supplied in Step 3. It will be from Amazon Web Services<trustandsafety@support.aws.com>. 
+   Please note:
+   - Request tracking ID 
+   - AWS Request ID
+5. Within 24-48 hours, AWS will provide an update to the request, approving, denying, or requesting more information to process the request. 
+   If there is an issue (such as deny response to the request), open a case with AWS support and contact the Census AWS TAM for futher assistance. 
+