This topic describes how to add Simple Log Service as a sink for an event stream in the EventBridge console.
Prerequisites
Create an event stream
Log on to the EventBridge console. In the left-side navigation pane, click Event Streams.
In the top navigation bar, select a region and click Create Event Stream.
-
On the Create Event Stream panel, enter a Task Name and Description, configure the parameters below, and click Save.
-
Task configuration
-
In the Source, Filtering, and Transformation steps, configure the filter and transformation rules, and click Next. For more information about how to configure event transformations, see Use Function Compute to clean message data.
-
In the Sink step of the configuration wizard, set Service Type to Simple Log Service and configure the following parameters.
Parameter
Description
Example
Project
Select the project that you created in Simple Log Service.
test-project
Logstore
Select the Logstore that you created in Simple Log Service.
test-logstore
Topic
Enter a name for the topic.
test-topic
Content
Specifies the portion of the event to route. For more information, see Event transformation.
Complete Event
Role
The role that EventBridge assumes to write events to Simple Log Service. For more information about the required permission policy for the role, see Route events to Simple Log Service.
testRole
-
-
Task properties
Configure the retry policy and dead-letter queue for the event stream. For more information, see Retry policies and dead-letter queues.
-
-
On the Event Streams page, find the event stream you created and click Enable in the Actions column.
The configuration takes effect in 30 to 60 seconds. You can view the progress in the Status column on the Event Streams page.
Verify the results
-
Log on to the Simple Log Service console.
-
In the project list, click your project.
-
On the Logstores page, click your Logstore.
-
Click Search & Analyze to view the results.
On the query results page, the Raw Logs tab displays Application Load Balancer (ALB) Layer 7 access log (alb_layer7_access_log) entries, including fields such as
app_lb_id,body_bytes_sent,client_ip,host,http_host,request_method,request_uri, andscheme.