Apica Ascent S3 Import App Extension (PULL)

Apica Ascent can ingest data directly from any S3 compatible object storage. Head over to the App extensions to create an object importer app extension.

You can find App extensions under the Explore menu

Once inside the App extension menu, select AWS S3/Compatible Object store

Create the extension and provide the settings for accessing your object store bucket. The settings menu provides options that allow customization that is specific to vendor object store implementations.

And that is all you need. You data from the Object store bucket will show up as a flow in the Apica Ascent platform

Apica Ascent S3 exporter Lambda function (PUSH)

Creating a Lambda function

Apica Ascent provides a CloudFormation template to create the Apica Ascent S3 exporter Lambda function.

You can also download the CloudFormation template from our client-integrations GitHub repository.

This CloudFormation stack creates a Lambda function and its necessary permissions. You must configure the following attributes.



Application name - a readable name for Apica Ascent to partition logs.


Cluster ID - a readable name for Apica Ascent to partition logs.


Namespace - a readable name for Apica Ascent to partition logs.


IP address or hostname of the Apica Ascent server.


JWT token to securely ingest logs. Refer here to generate ingest token.

Configuring S3 trigger

Once the CloudFormation stack is created, navigate to the AWS Lambda function (logiq-s3-logs-exporter) and add a S3 trigger.

On the Add trigger page, select S3. Next, select the Bucket you'd like to forward logs from and add a Prefix.

Once this configuration is complete, any new log files in the S3 bucket will be streamed to the Apica Ascent cluster.

Last updated