# AWS CloudTrail SQS integration issues

**URL:** <https://discuss.elastic.co/t/aws-cloudtrail-sqs-integration-issues/299783>\
**Category:** Beats\
**Tags:** fleet, beats-module, filebeat\
**Created:** [March 15, 2022, 8:04pm UTC](https://discuss.elastic.co/t/aws-cloudtrail-sqs-integration-issues/299783 "2022-03-15T20:04:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bil15](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bil15/32/103083_2.png) [@bil15](https://discuss.elastic.co/u/bil15)\
**Post date:** [March 15, 2022, 8:04pm UTC](https://discuss.elastic.co/t/aws-cloudtrail-sqs-integration-issues/299783/1 "2022-03-15T20:04:56Z")

</div>

Hello!  
I'm trying to ingest AWS CloudTrail logs via AWS integration in Fleet using S3 input (SQS).  
I followed this article to configure CloudTrail logs forwarding to SQS:  
[https://docs.rapid7.com/insightidr/aws-cloudtrail-sqs/](https://docs.rapid7.com/insightidr/aws-cloudtrail-sqs/)

I've installed integration on Fleet server agent itself and customized configuration like this (Queue URL is 100% correct).

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/c/ec370e5ddb2cfec2b1baf84e66c13ef3ffd4b31f.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c509bcdb39671c2cb3d3eba8c9b8c60eedcd6a21.png)

But I'm constantly facing an error:

```auto
Message: Failed processing <mark>SQS</mark> message
Error Message: 	
failed processing SQS message (message will be deleted): non-retryable error: the message is an invalid S3 notification: missing Records field
Stacktrace: github.com/elastic/beats/v7/x-pack/filebeat/input/awss3.(*sqsS3EventProcessor).ProcessSQS
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/awss3/sqs_s3_event.go:157
github.com/elastic/beats/v7/x-pack/filebeat/input/awss3.(*sqsReader).Receive.func1
	/go/src/github.com/elastic/beats/x-pack/filebeat/input/awss3/sqs.go:91
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1581

```

Has anyone faced the same issue?  
I feel like the issue on Elastic side, not AWS.

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [March 16, 2022, 3:16am UTC](https://discuss.elastic.co/t/aws-cloudtrail-sqs-integration-issues/299783/2 "2022-03-16T03:16:32Z")

</div>

Looks like u didn't setup which events get pushed to the queue properly. It should only be object creations.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 13, 2022, 5:17am UTC](https://discuss.elastic.co/t/aws-cloudtrail-sqs-integration-issues/299783/3 "2022-04-13T05:17:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.