Email

Email connections allow you to load files that are received as attachments on emails sent to an Etleap provided email address.

Source Setup

Etleap stores the email and the attachments it receives in your organization’s intermediate bucket. To enable this, you will need to update the policy on your S3 Intermediate bucket and the trust policy of its IAM role before you create the connection.

1. Add the statement below to the Statement array of the bucket policy. Replace <bucket> with the name of your bucket. The Intermediate Bucket Permissions section of the Etleap connection setup page shows the statement with the AWS:SourceArn value for your organization.

   {
     "Sid": "AllowEtleapInboundEmail",
     "Effect": "Allow",
     "Principal": { "Service": "ses.amazonaws.com" },
     "Action": "s3:PutObject",
     "Resource": "arn:aws:s3:::<bucket>/email/inbox/*",
     "Condition": {
       "StringEquals": {
         "AWS:SourceAccount": "223848809711",
         "AWS:SourceArn": "arn:aws:ses:us-east-1:223848809711:receipt-rule-set/inbound-email:receipt-rule/email-<organization id>"
       }
     }
   }

2. Set the bucket’s Object Ownership to Bucket owner enforced.

3. If the bucket encrypts objects with SSE-KMS under a customer managed key, add a statement to the key policy. Grant kms:GenerateDataKey* and kms:Decrypt to the ses.amazonaws.com principal, with the same two conditions.

4. Two Etleap principals assume your intermediate connection’s IAM role: the application and the inbound email processor. Keep the trust policy on arn:aws:iam::223848809711:root, or list both roles. The Intermediate Bucket Permissions section names the processor role.

The bucket must be in an AWS Region where Amazon SES email receiving is available . A bucket with a default Object Lock retention period does not work.

When you create the connection, Etleap will generate an email address which will be displayed on the connection page. Send your files to it as attachments.

What Data is Available?

Etleap can ingest any attachment that is one of the supported File Types. Any part of an email that is not the plain text or HTML body counts as an attachment. The subject line and the other headers are not stored.

During pipeline creation, the file picker shows a list of the attachments this connection received. Pick the files you want, or bulk select them with a Filename Regex. Email connections do not offer glob patterns.

Etleap changes the name of an attachment before it stores it:

• It replaces every character other than a letter, a digit, ., _ or - with _.
• It adds a suffix when the name is already taken, for example report_1.csv after report.csv.
• It shortens a name longer than 200 characters.

Filename regex patterns should be written for the stored name, rather than the original.

Etleap rejects any email that carries no attachments, fails the virus or spam check, or is larger than 40 MB. The connection page counts the emails it accepted and rejected, and gives the reason for the last rejection.

How Data is Updated

Etleap writes each attachment once and never changes it, so file changes are not supported. During pipeline creation you will need to select the Update Method that fits your data.

Key Considerations

• Send one attachment per email for a pipeline in Replace Mode. Attachments from the same email can share a modification time, and the pipeline then processes an arbitrary one.
• Use a separate Email connection for each system that sends you files. Each connection has its own address and its own folder, so their file names never collide.
• Deleting the connection stops its address from receiving email.
• Etleap never deletes the attachments it stores in your intermediate bucket, including after you delete the connection.