Amazon SES

The Amazon SES (Simple Email Service) connector integrates the Netmera platform with Amazon Web Services' scalable and reliable email sending infrastructure. This integration allows Netmera clients to send high-volume marketing campaigns and crucial transactional emails using the AWS cloud.

Overview

Attribute	Details
Connector Name	Amazon SES
Category	Email Providers / Cloud Services
Provider	Amazon Web Services (AWS)
Primary Function	Cloud-based transactional and marketing email delivery
Netmera Component	AwsMailAdapterImpl and AwsSesServiceImpl
Data Flow	Outbound (Netmera > Amazon SES)
Priority Ranking	Rank 2 (Prioritized after SetRow, if service permission is granted)

The integration leverages dedicated Java classes (AwsMailAdapterImpl and AwsSesServiceImpl) to communicate with the SES API, routing email requests efficiently to the chosen AWS region.

Use Cases and Benefits

1. High-Volume Email Campaigns: Utilizing Amazon's infrastructure for bulk sending marketing emails created through the Netmera Control Panel (Messages > Create Message > Email).

2. Transactional Email Support: Sending crucial system emails, such as password resets, verification links (nm.mail.verification.url), notifications, and API-triggered transactional messages, is reliably handled by SES.

3. Attachment Handling: The integration supports including file attachments in emails. For this functionality, files are first uploaded to a Cloud Storage Connector (like Amazon S3 or Azure Storage) and then included in the SES message payload.

4. Scalability and Deliverability: Netmera utilizes SES to benefit from AWS's high deliverability rates and massive scalability, which are essential for clients managing large customer bases.

5. Event Tracking: Configuration Set Name parameter allows leveraging advanced SES features like event tracking (sends, opens, clicks, bounces) and reputation metrics, managed within the AWS environment.

Data Flow

The Amazon SES integration has an Outbound data flow, managed by the Mail Adapter service layer in Netmera.

1. Request Initiation: An email sending command (e.g., campaign or transactional) is issued within Netmera.

2. Provider Selection: The MailSenderServiceImpl checks active email connectors. If the client has permission to use AWS Mail Server Service and SES is configured, it is selected (ranking generally second, after SetRow).

3. API Call: The AwsMailAdapterImpl securely authenticates using the configured AWS credentials and constructs the necessary API request, submitting the email content (including HTML and attachment URLs) to the designated SES endpoint.

4. Delivery: AWS SES handles the final transmission of the email to the recipient's mail server.

$\text{Netmera Mail Sender} \xrightarrow[\text{AwsMailAdapterImpl}]{\text{SES API Call}} \text{Amazon SES} \rightarrow \text{Recipient Mailbox}$

Configuration Reference

The configuration requires standard AWS IAM credentials tied to a user with SES sending permissions.

Parameter	Type	Description	AWS Context
region	String	The AWS region where your SES service is configured (e.g., "eu-west-1").	Determines the API endpoint location.
accessKey	String	Your AWS IAM user's Access Key ID.	Used for programmatic API authentication.
secretKey	String	Your AWS IAM user's Secret Access Key.	Used for secure API authentication.
configurationSetName	String	The name of a Configuration Set created in SES.	Optional; used for reputation monitoring and event publishing.

Setup Instructions

The setup process requires specific actions within the AWS Console before configuring Netmera.

Step 1: AWS Prerequisites

1. Create an AWS account and navigate to the IAM (Identity and Access Management) service.

2. Create a dedicated IAM user with "Programmatic access" enabled and attach a policy granting permission to send emails via SES (e.g., AmazonSESFullAccess).

3. Obtain and save the Access Key ID and Secret Access Key (the secret key is shown only once).

4. Navigate to the SES Console and verify the email address(es) or domain(s) you plan to use for sending.

5. If the account is new, it will be in Sandbox mode. You must apply to AWS Support for production access to increase daily sending quotas and remove restrictions on recipient addresses.

Step 2: Configure in Netmera

1. Access the Netmera Control Panel and go to the Connectors section.

2. Select the Amazon SES connector.

3. Input the Region, Access Key, Secret Key, and optionally, the Configuration Set Name.

4. Click Save Configuration.

Usage Notes & Considerations

1. Sandbox Restrictions: Newly configured SES accounts are severely limited by AWS, restricting sending only to verified addresses. Production access must be secured through AWS support to begin large-scale sending.

2. Rate and Quota Limits: AWS imposes initial daily sending quotas and maximum send rates. High-volume senders must regularly monitor these limits within the AWS Console and request increases directly from AWS if necessary.

3. Credential Dependency: If the IAM user credentials (accessKey, secretKey) are changed or revoked in the AWS Console, the Netmera connector will fail immediately, requiring manual update in the Netmera configuration.

4. Priority Sequencing: Amazon SES is prioritized below the SetRow connector. If SetRow is active and configured with the necessary service permission, email traffic will be routed through SetRow first, bypassing SES. You must manage the priority settings (via service permissions) if you intend to use SES as the primary channel.

5. Attachment Storage: Attachments must be hosted externally before sending. Netmera relies on the proper configuration of an AWS S3 (Amazon Storage) or Azure Storage connector to handle the media file uploads referenced in the email.

Analogy: If your messaging system is a fleet of delivery trucks, Amazon SES acts as leasing a large, optimized fleet of cargo planes from AWS.

It offers unparalleled capacity and speed (scalability and deliverability), but you must first clear the security checkpoints (Sandbox mode and production request) and ensure your keys (Access/Secret Keys) are always correct to dispatch the messages.