# SQS client ignores the fips flag for the service endpoint

**URL:** <https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [November 8, 2021, 11:28pm UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687 "2021-11-08T23:28:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Chang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_chang/32/96862_2.png) [@Andrew\_Chang](https://discuss.elastic.co/u/Andrew_Chang)\
**Post date:** [November 8, 2021, 11:28pm UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687/1 "2021-11-08T23:28:32Z")

</div>

At least in 7.15.1 when using the fips\_enabled flag, only s3 respects the fips configuration. SQS does not. It seems to be hard coded. [beats/input.go at master · elastic/beats · GitHub](https://github.com/elastic/beats/blob/master/x-pack/filebeat/input/awss3/input.go#L164)

---

<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:** [November 9, 2021, 3:36am UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687/2 "2021-11-09T03:36:59Z")

</div>

That's a good point. I'd submit a GitHub issue as there are other AWS services that might need to be updated to accommodate fips besides S3 and sqs.

---

<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:** [November 9, 2021, 12:36pm UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687/3 "2021-11-09T12:36:28Z")

</div>

@Kaiyan_Sheng could we just move the `fips_enabled` setting to the AWS common module?

---

<div class="post-metadata">

**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\
**Post date:** [November 9, 2021, 10:41pm UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687/4 "2021-11-09T22:41:54Z")

</div>

Yes good point! Let's move this config into libbeat aws common. Thank you!!

---

<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:** [December 8, 2021, 12:42am UTC](https://discuss.elastic.co/t/sqs-client-ignores-the-fips-flag-for-the-service-endpoint/288687/5 "2021-12-08T00:42:05Z")

</div>

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