# AWS ES Request signing

**URL:** <https://community.temporal.io/t/aws-es-request-signing/337>\
**Category:** Community Support\
**Created:** [July 31, 2020, 11:57pm UTC](https://community.temporal.io/t/aws-es-request-signing/337 "2020-07-31T23:57:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthew\_Anger](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/matthew_anger/32/134_2.png) [@Matthew\_Anger](https://community.temporal.io/u/Matthew_Anger)\
**Post date:** [July 31, 2020, 11:57pm UTC](https://community.temporal.io/t/aws-es-request-signing/337/1 "2020-07-31T23:57:36Z")

</div>

Can temporal have support to enable AWS request signing? The default credential chain should work for most scenarios I would expect. We forked cadence to add it to ours so we can use AWS RBACL to secure our ES cluster.

---

<div class="post-metadata">

**Author:** ![ryland](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/ryland/32/11_2.png) [@ryland](https://community.temporal.io/u/ryland)\
**Post date:** [July 31, 2020, 11:58pm UTC](https://community.temporal.io/t/aws-es-request-signing/337/2 "2020-07-31T23:58:08Z")

</div>

I will absolutely make sure this is communicated internally as it’s a very reasonable request.

---

<div class="post-metadata">

**Author:** ![KyleNightfall](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/kylenightfall/32/95_2.png) [@KyleNightfall](https://community.temporal.io/u/KyleNightfall)\
**Post date:** [August 21, 2020, 4:50pm UTC](https://community.temporal.io/t/aws-es-request-signing/337/3 "2020-08-21T16:50:45Z")

</div>

Just FYI @ryland I think this is a duplicate of this feature request here: [Add support for AWS elasticsearch request signing](https://community.temporal.io/t/add-support-for-aws-elasticsearch-request-signing/213)