Added SNS trigger support

Release 1.3

This release adds the support for SNS trigger support. In other words, you can now send the S3 events to SNS and trigger Lambda function from SNS.

NO CHANGE IN CONFIGURATION FILE FORMAT

Detect and Prevent cyclic duplication

Release 1.2

This release adds the feature to detect and prevent cyclic duplication of objects among S3 bucket in the configuration. This prevents accidental misconfiguration and possibility of an unexpected amount of AWS bill.

NO CHANGE IN CONFIGURATION FILE FORMAT

Added support for SQS

Release 1.1

This release has added support to SQS processing of events.

• The function can take events from SQS as well if you have the source bucket put all event to an SQS.

• The function can take events from SQS where SQS is subscribed to an SNS and source bucket publish a message to SNS on every change.

To Support SQS processing add SQS URL sqs and SQS region sqsRegion in the config file. Otherwise, Leave them empty "" or remove the keys.

Config

{
  "s3copyinput": {
    "region": "us-east-1",
    "sqs": "url of SQS where all S3 change events are stored",
    "sqsRegion": "us-east-1"
    "destinations": [
      "s3copyoutput1",
      "s3copyoutput2"
    ]
  }
}

Initial Release

Initial Release

This is the initial release with S3 trigger support to AWS lambda.

Config File:

Config File is a map of input s3 bucket and detail to copy changes to destination.

{
  "s3copyinput": {
    "region": "us-east-1"
    "destination": [
      "s3copyoutput1",
      "s3copyoutput2"
    ]
  }
}