AWS ACTION
CloudWatch Logs - Put Log Event
Uploads a log event to the specified log stream. See docs
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's AWS account once, then configure and run CloudWatch Logs - Put Log Event from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "aws-cloudwatch-logs-put-log-event",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
aws: { authProvisionId: "apn_xxxxxxx" },
region: "AWS Region",
logGroupName: "CloudWatch Log Groups",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "aws-cloudwatch-logs-put-log-event",
"configured_props": {
"aws": { "authProvisionId": "apn_xxxxxxx" },
"region": "AWS Region",
"logGroupName": "CloudWatch Log Groups"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "aws",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "aws-cloudwatch-logs-put-log-event",
arguments: {
region: "AWS Region",
logGroupName: "CloudWatch Log Groups",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
region AWS Region | string | The AWS region Required Dynamic |
logGroupName CloudWatch Log Groups | string | The name of the log group Required Dynamic |
logStreamName CloudWatch Log Streams | string | The name of the log stream for the chosen log group Required Dynamic |
message Message | string | The event message Required |
timestamp Timestamp | integer | The Unix timestamp for when the event occurred, in milliseconds Required |
sequenceToken Sequence token | string | The sequence token obtained from the response of the previous PutLogEvents call. An upload in a newly created log stream does not need a sequence token. You can also get the sequence token using DescribeLogStreams. If you call PutLogEvents twice within a narrow time period using the same value for sequenceToken, both calls might be successful or one might be rejected. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- aws-cloudwatch-logs-put-log-event
- Version
- 0.1.3
- App
- AWS
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗