github.com/mweagle/Sparta@v1.15.0/docs_source/content/reference/eventsources/_index.md (about)

     1  ---
     2  date: 2016-03-09T19:56:50+01:00
     3  title:
     4  pre: "<b>Event Sources</b>"
     5  weight: 110
     6  ---
     7  
     8  # Event Sources
     9  
    10  The true power of the AWS Lambda architecture is the ability to integrate Lambda execution with other AWS service state transitions.  Depending on the service type, state change events are either pushed or transparently polled and used as the input to a Lambda execution.
    11  
    12  There are several [event sources](http://docs.aws.amazon.com/lambda/latest/dg/intro-core-components.html) available.  They are grouped into Pull and Push types.  Pull based models use `sparta.EventSourceMapping` values, as the trigger configuration is stored in the AWS Lambda service.  Push based types use service specific `sparta.*Permission` types to denote the fact that the trigger logic is configured in the remote service.
    13  
    14  ## Pull Based
    15  
    16  * [DynamoDB](/reference/eventsources/dynamodb)
    17  * [Kinesis](/reference/eventsources/kinesis)
    18  * [SQS](/reference/eventsources/sqs)
    19  
    20  ## Push Based
    21  
    22  * [CloudFormation](/reference/eventsources/cloudformation) _NOT YET IMPLEMENTED_
    23  * [CloudWatch Events](/reference/eventsources/cloudwatchevents)
    24  * [CloudWatch Logs](/reference/eventsources/cloudwatchlogs)
    25  * [Cognito](/reference/eventsources/cognito) _NOT YET IMPLEMENTED_
    26  * [S3](/reference/eventsources/s3)
    27  * [SES](/reference/eventsources/ses)
    28  * [SNS](/reference/eventsources/sns)