Reputation: 498
I'm interested in publishing SES analytics data to SNS and publishing the SNS topic to somewhere (S3?) to store the data permanently.
Our control flow is as follows:
The SNS subscribe() function says after confirming the subscription, it will last for 3 days. I'd like to make it last indefinitely so we can gather email analytics longer than 3 days.
If this is a reasonable approach, how would someone remove that expiration?
If this is the wrong approach, how should I approach storing SES analytics data permanently?
Thank you!
Upvotes: 0
Views: 287
Reputation: 13055
Going through SNS is too much round trip.
SES (Events) --> Firehose --> (S3 / Redshift / Elastisearch)
You can configure SES to send analytics data to Kinesis Firehose. You can configure Kinesis Firehose to deliver to S3 or Redshift or Elastisearch, depending upon your needs.
SES Events to Firehose:
Event Data Transformation with Lambda:
With an intermediate Data transformation with Lambda you can manipulate the data before sending it to the desired destination.
http://docs.aws.amazon.com/firehose/latest/dev/data-transformation.html
Hope it helps.
Upvotes: 1