Amazon EventBridge 통합
Amazon EventBridge를 활용해 이벤트 버스를 구축하고 다양한 소스의 이벤트를 라우팅하며 AWS 계정 전반에 강력한 이벤트 기반 통합을 구성합니다.
Amazon EventBridge 통합은(는) CoddyKit의 무료 Serverless AWS Lambda Development 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Serverless AWS Lambda Development 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Serverless AWS Lambda Development 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
What is Amazon EventBridge?
Welcome to a deeper dive into event-driven architectures! Today, we'll explore Amazon EventBridge, a powerful service that acts as a central nervous system for your serverless applications.
EventBridge is a serverless event bus that makes it easy to connect applications together using data from your own apps, Software-as-a-Service (SaaS) applications, and AWS services.
EventBridge Core Concepts
EventBridge operates on a few key concepts:
- Event Bus: A pipeline that receives events. There's a Default Event Bus for AWS service events, and you can create Custom Event Buses.
- Rules: Filters that match incoming events based on their content (event patterns).
- Targets: The AWS services or endpoints that an event is sent to when a rule matches.
The Default Event Bus
Every AWS account automatically has a Default Event Bus. This bus receives events from over 200 AWS services, like S3, EC2, Lambda, and CloudTrail.
You don't need to configure these sources; they publish events to the default bus automatically. This allows you to react to changes and activities across your AWS environment without custom code.
Custom Event Buses & Sources
While the default bus handles AWS events, you can create Custom Event Buses to manage events from your own applications or third-party SaaS providers.
This allows you to centralize event routing for your entire ecosystem. Event sources can be:
- AWS Services: (via Default Bus)
- SaaS Partners: (e.g., Zendesk, Shopify)
- Custom Applications: Your own microservices or monoliths.
Creating Event Patterns (Rules)
Rules are how EventBridge knows which events to route where. Each rule has an event pattern, a JSON structure that defines the criteria an event must meet to be matched.
Event patterns can match specific fields, prefixes, or even check for the existence of fields. They are highly flexible for filtering.
Event Pattern Example
Here's an example of an event pattern that matches any PutObject operation on an S3 bucket:
This pattern ensures only S3 object creation events trigger the rule.
{
"source": ["aws.s3"],
"detail-type": ["AWS API Call via CloudTrail"],
"detail": {
"eventSource": ["s3.amazonaws.com"],
"eventName": ["PutObject"]
}
}EventBridge Targets
Once an event matches a rule, EventBridge sends it to one or more targets. Targets are the downstream services that process the event.
Common targets include:
- AWS Lambda functions
- Amazon SQS queues
- Amazon SNS topics
- AWS Step Functions state machines
- Kinesis streams
- and many more!
Lambda as an EventBridge Target
Lambda functions are a very common target for EventBridge. When a rule matches an event, EventBridge invokes your Lambda function, passing the event data as the input.
This allows you to build highly responsive, event-driven microservices that react to changes across your AWS environment or custom applications.
Handling EventBridge Events in Lambda
Let's look at a Python Lambda function designed to receive and process an EventBridge event. The event parameter will contain the full JSON event payload.
We'll simulate an S3 PutObject event for demonstration.
import json
def lambda_handler(event, context):
print("Received event from EventBridge:")
print(json.dumps(event, indent=2))
source = event.get('source')
detail_type = event.get('detail-type')
if source == 'aws.s3' and detail_type == 'AWS API Call via CloudTrail':
bucket_name = event['detail']['requestParameters']['bucketName']
object_key = event['detail']['requestParameters']['key']
print(f"S3 PutObject event detected for bucket: {bucket_name}, key: {object_key}")
else:
print(f"Unknown event source: {source}, detail-type: {detail_type}")
return {
'statusCode': 200,
'body': json.dumps('Event processed successfully!')
}
# Simulate a local invocation for testing
if __name__ == '__main__':
sample_s3_event = {
"version": "0",
"id": "c6183e20-7f51-4091-8656-e23a31c51e0f",
"detail-type": "AWS API Call via CloudTrail",
"source": "aws.s3",
"account": "123456789012",
"time": "2023-10-27T10:00:00Z",
"region": "us-east-1",
"resources": [],
"detail": {
"eventSource": "s3.amazonaws.com",
"eventName": "PutObject",
"requestParameters": {
"bucketName": "my-cool-bucket",
"key": "new-image.jpg"
}
}
}
print("--- Simulating Lambda with EventBridge event ---")
lambda_handler(sample_s3_event, None)
print("--- Simulation complete ---")EventBridge Quick Check
You want to trigger a Lambda function whenever a new user signs up in your custom application. Your application publishes a UserSignedUp event to your custom event bus.
Which of the following event patterns would correctly match this specific event?
Recap: EventBridge Power
In this lesson, we explored Amazon EventBridge, understanding its role as a central event bus for your serverless applications. You learned about:
- Event Buses: Default, Custom, and Partner.
- Rules: Using event patterns to filter events.
- Targets: Sending matched events to services like Lambda.
- How to integrate Lambda to process EventBridge events.
EventBridge is key to building scalable, loosely coupled, and responsive event-driven architectures.
자주 묻는 질문
“Amazon EventBridge 통합” 강의는 무료인가요?
네 — “Amazon EventBridge 통합” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Serverless AWS Lambda Development 강의 전체를 잠금 해제할 수 있습니다. Serverless AWS Lambda Development 강의에는 총 4개의 강의가 포함되어 있습니다.
“Amazon EventBridge 통합”에서 뭘 배우나요?
Amazon EventBridge를 활용해 이벤트 버스를 구축하고 다양한 소스의 이벤트를 라우팅하며 AWS 계정 전반에 강력한 이벤트 기반 통합을 구성합니다. 브라우저에서 직접 실행하는 실습 코드로 Serverless AWS Lambda Development을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Serverless AWS Lambda Development을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Serverless AWS Lambda Development은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“Amazon EventBridge 통합” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Serverless AWS Lambda Development 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Serverless AWS Lambda Development 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- 이벤트 기반 마이크로서비스 구축
- Amazon EventBridge 통합
- Kinesis를 활용한 실시간 처리
- 분산 트랜잭션을 위한 사가 패턴