← HTTP / Webhook + AWS integrations

Cloudwatch Logs - Put Log Events with AWS APIon New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for AWS, HTTP / Webhook and + other apps remarkably fast.

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Cloudwatch Logs - Put Log Events with the AWS API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a HTTP / Webhook trigger and AWS action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New Requests trigger
    1. Optional- Configure Body Only
    2. Optional- Configure Response Status Code
    3. Optional- Configure Response Content-Type
    4. Optional- Configure Response Body
    5. Connect your HTTP / Webhook account
  3. Configure the Cloudwatch Logs - Put Log Events action
    1. Connect your AWS account
    2. Select a AWS Region
    3. Select a CloudWatch Log Groups
    4. Select a CloudWatch Log Streams
    5. Configure Log data
    6. Optional- Configure Sequence token
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.
Version:0.1.1
Key:http-new-requests

Trigger Code

import http from "../../http.app.mjs";

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

Trigger Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.
LabelPropTypeDescription
N/AhttpInterface$.interface.httpThis component uses $.interface.http to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the run() method of the component.
Body OnlyemitBodyOnlyboolean

This source emits an event representing the full HTTP request by default. Select true to emit the body only.

Response Status CoderesStatusCodestring

The status code to return in the HTTP response

Response Content-TyperesContentTypestring

The Content-Type of the body returned in the HTTP response

Response BodyresBodystring

The body to return in the HTTP response

HTTP / WebhookhttpappThis component uses the HTTP / Webhook app.

Trigger Authentication

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook

Get a unique URL where you can send HTTP or webhook requests

Action

Description:Uploads a batch of log events to the specified log stream. [See the docs](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CloudWatchLogs.html#putLogEvents-property) for more information
Version:0.0.1
Key:aws-cloudwatch-logs-put-log-events

Action Code

import aws from "../../aws.app.mjs";

export default {
  name: "Cloudwatch Logs - Put Log Events",
  version: "0.0.1",
  key: "aws-cloudwatch-logs-put-log-events",
  description: "Uploads a batch of log events to the specified log stream. [See the docs](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CloudWatchLogs.html#putLogEvents-property) for more information",
  props: {
    aws,
    region: {
      propDefinition: [
        aws,
        "region",
      ],
    },
    logGroupName: {
      description: "The name of the log group you'd like to write logs to",
      type: "string",
      propDefinition: [
        aws,
        "logGroupNames",
        (configuredProps) => ({
          region: configuredProps.region,
        }),
      ],
    },
    logStreamName: {
      description: "The name of the log stream within your log group",
      type: "string",
      propDefinition: [
        aws,
        "logStreamNames",
        (configuredProps) => ({
          logGroupName: configuredProps.logGroupName,
          region: configuredProps.region,
        }),
      ],
    },
    logEvents: {
      label: "Log data",
      description: "An array of log events. Each log event must contain a `timestamp` (the time the event occurred) and a `message`. [See the docs](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CloudWatchLogs.html#putLogEvents-property)",
      type: "string[]",
    },
    sequenceToken: {
      label: "Sequence token",
      description: "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.",
      type: "string",
      optional: true,
    },
  },
  type: "action",
  async run({ $ }) {
    const {
      logGroupName,
      logStreamName,
      logEvents,
      region,
      sequenceToken,
    } = this;
    const l = logEvents.length;
    if (!l) {
      throw new Error("No log data was written to CloudWatch. Please enter log data according to the format in the AWS docs: https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CloudWatchLogs.html#putLogEvents-property");
    }
    const data = await this.aws.logsPutLogEvents(
      region,
      logGroupName,
      logStreamName,
      logEvents,
      sequenceToken,
    );
    $.export("$summary", `Successfully stored ${l} log${l === 1
      ? ""
      : "s"}`);
    return data;
  },
};

Action Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

LabelPropTypeDescription
AWSawsappThis component uses the AWS app.
AWS RegionregionstringSelect a value from the drop down menu.
CloudWatch Log GroupslogGroupNamestringSelect a value from the drop down menu.
CloudWatch Log StreamslogStreamNamestringSelect a value from the drop down menu.
Log datalogEventsstring[]

An array of log events. Each log event must contain a timestamp (the time the event occurred) and a message. See the docs

Sequence tokensequenceTokenstring

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.

Action Authentication

AWS uses API keys for authentication. When you connect your AWS account, Pipedream securely stores the keys so you can easily authenticate to AWS APIs in both code and no-code steps.

Follow the AWS Instructions for creating an IAM user with an associated access and secret key.

As a best practice, attach the minimum set of IAM permissions necessary to perform the specific task in Pipedream. If your workflow only needs to perform a single API call, you should create a user and associate an IAM group / policy with permission to do only that task. You can create as many linked AWS accounts in Pipedream as you'd like.

Once done, enter your access and secret key below.

About AWS

On-demand cloud computing platforms and APIs

More Ways to Connect AWS + HTTP / Webhook

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.