← HTTP / Webhook + AWS integrations

CloudWatch Logs - Put Log Event with AWS APIon New Requests from HTTP / Webhook API

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

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
CloudWatch Logs - Put Log Event with the AWS API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜
Trusted by 250,000+ developers from startups to Fortune 500 companies:
Trusted by 250,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 Event 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 Message
    6. Configure Timestamp
    7. 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 log event to the specified log stream. [See docs](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-cloudwatch-logs/classes/putlogeventscommand.html)
Version:0.1.0
Key:aws-cloudwatch-logs-put-log-event

Action Code

import common from "../../common/common-cloudwatch-logs.mjs";
import { toSingleLineString } from "../../common/utils.mjs";

export default {
  ...common,
  key: "aws-cloudwatch-logs-put-log-event",
  name: "CloudWatch Logs - Put Log Event",
  description: toSingleLineString(`
    Uploads a log event to the specified log stream.
    [See docs](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-cloudwatch-logs/classes/putlogeventscommand.html)
  `),
  version: "0.1.0",
  type: "action",
  props: {
    aws: common.props.aws,
    region: common.props.region,
    logGroupName: common.props.logGroupName,
    logStreamName: common.props.logStreamName,
    message: {
      type: "string",
      label: "Message",
      description: "The event message",
    },
    timestamp: {
      type: "integer",
      label: "Timestamp",
      description: "The Unix timestamp for when the event occurred, in milliseconds",
    },
    sequenceToken: {
      type: "string",
      label: "Sequence token",
      description: toSingleLineString(`
        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: true,
    },
  },
  async run({ $ }) {
    const params = {
      logGroupName: this.logGroupName,
      logStreamName: this.logStreamName,
      logEvents: [
        {
          message: this.message,
          timestamp: this.timestamp,
        },
      ],
    };
    if (this.sequenceToken) {
      params.sequenceToken = this.sequenceToken;
    }
    const response = await this.putLogEvents(params);
    if (response.rejectedLogEventsInfo) {
      $.export("$summary", "Log event was rejected");
    } else {
      $.export("$summary", "Successfully stored log");
    }
    return response;
  },
};

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.
Messagemessagestring

The event message

Timestamptimestampinteger

The Unix timestamp for when the event occurred, in milliseconds

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