# Using custom ingest pipeline for AWS integration

**URL:** https://discuss.elastic.co/t/using-custom-ingest-pipeline-for-aws-integration/363381
**Category:** Kibana
**Created:** [July 18, 2024, 11:06pm UTC](https://discuss.elastic.co/t/using-custom-ingest-pipeline-for-aws-integration/363381 "2024-07-18T23:06:07Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![shiftey](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@shiftey](https://discuss.elastic.co/u/shiftey)
#### Post date: [July 18, 2024, 11:06pm UTC](https://discuss.elastic.co/t/using-custom-ingest-pipeline-for-aws-integration/363381/1 "2024-07-18T23:06:07Z")

</div>

Hi there,  
Im fairly new to Elastic/Kibana, please bear with me.

We use Elastic v7.17. I've setup an AWS Cloudwatch integration to collect logs from a custom app which logs to Cloudwatch. The log is unstructured, so I have also created an ingest pipeline to parse the relevant fields.

Question - How do I use/configure the integration to use this pipeline? Also, how can I specify a new index to use for these custom logs?