integration-docs
Loading

Canva

Version 0.7.0 beta:[] (View all)
Compatible Kibana version(s) 8.16.5 or higher
9.0.0 or higher
Supported Serverless project types
What's this?
Security
Observability
Subscription level
What's this?
Basic
Level of support
What's this?
Elastic

Canva is an online graphic design platform used for creating social media graphics, presentations, posters, documents, and other visual content. Canva provides Audit logs that contain records of user activies in Canva, such as installing a Canva App, exporting a design for download, or a user changing their account settings. These logs can be useful for compliance audits, monitoring for unauthorized activity, and other matters that require details about the creation, access, and deletion of data in Canva.

NOTE:

  • Audit logs are available for organizations that use Canva Enterprise.
  • Canva starts generating Audit logs when an organization upgrades their account to Canva Enterprise and will start logging events for a brand once it joins the Canva Enterprise account.

The Canva integration can be used in two different modes to collect data:

  • AWS S3 polling mode - Canva writes data to S3 and Elastic Agent polls the S3 bucket by listing its contents and reading new files.
  • AWS S3 SQS mode - Canva writes data to S3, S3 pushes a new object notification to SQS, Elastic Agent receives the notification from SQS, and then reads the S3 object. Multiple Agents can be used in this mode.

The Canva integration collects Audit logs in the Audit data stream.

Audit contains the information about the user activies in Canva. The user changing account settings, installing Canva app, managing teams, and groups information can be logged through the Audit logs.

Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host. Elastic Agent is required to stream data from the S3 bucket and ship the data to Elastic, where the events will then be processed via the integration's ingest pipelines.

  • Follow these instructions to forward your Audit log data from Canva to the AWS S3 bucket.
  • Canva adds events to your S3 bucket every minute as a gzipped archive containing JSONL content and requires PutObject permission on the S3 bucket.
  • It stores the files in hourly folders, in the format orgId/yyyy/MM/dd/HH.
  1. Create an Amazon S3 bucket. Refer to these instructions.
  2. The default value of the "Bucket List Prefix" should be empty. However, you can set the parameter "Bucket List Prefix" according to your requirements.
  1. If data forwarding to an AWS S3 Bucket hasn't been configured, then first set up an AWS S3 Bucket as mentioned in the above documentation.
  2. To set up an SQS queue, follow "Step 1: Create an Amazon SQS queue" mentioned in the Amazon Documentation.
  • While creating an SQS Queue, please provide the same bucket ARN that has been generated after creating an AWS S3 Bucket.
  1. Set up event notifications for an S3 bucket. Follow the instructions here.
  • Users have to set the prefix parameter the same as the S3 Bucket List Prefix as created earlier. (for example, log/ for a log data stream.)
  • Select the event type as s3:ObjectCreated:*, select the destination type SQS Queue, and select the queue that has been created in Step 2.

Note:

  • Credentials for the above AWS S3 and SQS input types should be configured using these instructions.
  • Data collection via AWS S3 Bucket and AWS SQS are mutually exclusive in this case.
  1. In Kibana navigate to Management > Integrations.

  2. In the search bar, type Canva.

  3. Select the Canva integration and add it.

    To collect logs via AWS S3, enter the following details:

    • Collect logs via S3 Bucket toggled on
    • Access Key ID
    • Secret Access Key
    • Bucket ARN or Access Point ARN
    • Session Token

    Alternatively, to collect logs via AWS SQS, enter the following details:

    • Collect logs via S3 Bucket toggled off
    • Queue URL
    • Secret Access Key
    • Access Key ID
    • Session Token
  4. Save the integration.

NOTE: There are other input combination options available for the AWS S3 and AWS SQS, please check here.

This is the Audit dataset.