Key Concepts

• Amazon EventBridge: A serverless event bus that facilitates event-driven architectures. It receives events from various sources and routes them to target services like AWS Lambda.
• CloudWatch Events: Feature within EventBridge (they are very closely aligned).
• AWS Lambda: Serverless computing platform enabling you to run code in response to events without managing servers.

Use Cases

1. Serverless CRON or Rate-Based Jobs:
   • Goal: Execute your Lambda function on a recurring schedule (e.g., hourly, daily).
   • Mechanism: EventBridge Rule utilizing a CRON-like expression (e.g., cron(0 * * * ? *) to trigger hourly).
   • Benefit: No need to manage servers for routine tasks.
2. Reacting to CodePipeline State Changes:
   • Goal: Act in response to changes in your CodePipeline (e.g., deployment started, succeeded, failed).
   • Mechanism: EventBridge Rule with filtering on CodePipeline state change events.
   • Benefit: Automates tasks throughout deployment or CI/CD workflows.

Summary Table

Important Considerations

• Event Patterns: Carefully design the event patterns in your EventBridge rules to correctly capture the events you want to trigger your Lambda functions.
• Error Handling: Implement robust error handling within your Lambda functions to gracefully handle potential issues or exceptions during execution.
• Cost: While convenient, be mindful of cost, especially with frequent CRON-based triggers. EventBridge and Lambda have usage-based pricing models.

Hands on:

Here's a breakdown of the key actions and explanations provided in the transcript, focusing on the practical integration of Lambda with EventBridge.

Steps

1. Create Lambda Function:
   • Function name: lambda-demo-eventbridge
   • Runtime: Python 3.9
2. Create EventBridge Rule:
   • Name: InvokeLambdaEveryMinute
   • Event Bus: Default
   • Pattern: Schedule (every minute)
   • Target: The created Lambda function
3. Verification:
   • Lambda function will show EventBridge as a trigger after creation of the rule.
   • EventBridge permissions automatically grant "invoke function" action to the rule.

Explanation