This Guidance provides a set of ready-to-use email templates for Amazon Pinpoint. Customizable and available immediately, use these templates to support the communication needs of any business.
Architecture Diagram

Step 1
The AWS administrator installs the solution guidance AWS CloudFormation template into a stack.
Step 2
The CloudFormation template prompts for parameters such as logo url, company name, address, and color scheme.
Step 3
The email templates installed are customized at installation time to include the parameters captured in order to make them ready to use immediately.
Step 4
Templates are stored in the Amazon Pinpoint template repository.
Step 5
An Amazon Pinpoint user can then use the email templates in any campaigns and journeys they design. Email templates are fully editable and customizable using the Amazon Pinpoint editor.
Step 6
The email templates installed are responsive and look professional on mobile or desktops.
Well-Architected Pillars

The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational Excellence
Use the email templates in campaigns and journeys and install in multiple stacks for A/B testing. Included are instrumentation and tracked metrics. The templates are used only at design time when creating campaigns and they are fully editable by the designer.
-
Security
To factor for secure authentication and authorization, the templates don’t contain service data and are merged at run-time as part of a campaign process inside Amazon Pinpoint. Access to the Amazon Pinpoint service is needed and the templates do not include any sensitive data.
-
Reliability
A reliable application is achieved through HTML-based templates that are installed and edited in Amazon Pinpoint, a regional service. There are no limits or constraints that may affect reliability. As part of this Guidance, you can install CloudFormation templates multiple times into different stacks; stack names are used as part of the template names to ensure uniqueness.
-
Performance Efficiency
The solution guidance only uses Amazon Pinpoint and is purpose-built for this use case. The email templates installed improve performance by saving time when creating templates for email communications.
-
Cost Optimization
Install the CloudFormation template multiple times into different stacks and save approximately 4 hours per marketing campaign. Incur no additional costs or data transfer charges because the standard Amazon Pinpoint pricing model applies to this solution. Additionally, the email templates are used by an individual and loaded into a journey or campaign as part of the Amazon Pinpoint workflow. Therefore, no changes are made to the Amazon Pinpoint scalability.
-
Sustainability
Using the templates in Guidance allows you to scale as Amazon Pinpoint is a regional service and installed into the Amazon Pinpoint service email repository. No hardware is needed to provision this Guidance.
Implementation Resources

The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content

Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.