Architecture Flow
Here, we are assuming a common website-to-cloud migration scenario, where you have registered your domain name with a 3rd party domain registrar and after migration of your website to Amazon S3. From there, you switched to Amazon Route 53 as your DNS provider. You contacted your DNS provider and updated the name server (NS) record to use the name servers in the delegation that you set in Amazon Route 53 (find step-by-step details in the AWS S3 development guide). Your email server still belongs to your DNS provider as you brought that in the package when you registered your domain with a multi-year contract.
Following is the architecture flow with detailed guidance.
In the above diagram, the customer is submitting their inquiry through a "contact us" form, which is hosted in an Amazon S3 bucket as a static website. Information will flow in three simple steps:
- Your "contact us" form will collect all user information and post to Amazon API Gateway restful service.
- Amazon API Gateway will pass collected user information to an AWS lambda function.
- AWS Lambda function will auto generate an e-mail and forward it to your mail server using Amazon SES.
 | |
No comments:
Post a Comment