# AWS lambda plugin chain provider

**URL:** <https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555>\
**Category:** Questions\
**Created:** [July 24, 2018, 10:24pm UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555 "2018-07-24T22:24:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![neoshadybeat](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/neoshadybeat/32/217_2.png) [@neoshadybeat](https://discuss.konghq.com/u/neoshadybeat)\
**Post date:** [July 24, 2018, 10:24pm UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/1 "2018-07-24T22:24:05Z")

</div>

Is It posible use a chain provider from IAM role instead of add manually the credentials?

Kind regards  
Cayetano

---

<div class="post-metadata">

**Author:** ![thibaultcha](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thibaultcha/32/340_2.png) [@thibaultcha](https://discuss.konghq.com/u/thibaultcha)\
**Post date:** [July 25, 2018, 2:41pm UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/2 "2018-07-25T14:41:39Z")

</div>

Hi,

I am not sure what you mean exactly. If you could elaborate on your use-case, that’d be great. We recently received a PR for IAM roles on the proxy side:

> <https://github.com/Kong/kong/pull/3639>

Does this seem like something you are referring to?

---

<div class="post-metadata">

**Author:** ![neoshadybeat](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/neoshadybeat/32/217_2.png) [@neoshadybeat](https://discuss.konghq.com/u/neoshadybeat)\
**Post date:** [July 25, 2018, 3:08pm UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/3 "2018-07-25T15:08:36Z")

</div>

After the review ot that PR I have seen another one that it’s related with my issue [https://github.com/Kong/kong/pull/2777](https://github.com/Kong/kong/pull/2777)

So I think that right now It’s not possible

Kind regards  
Cayetano

---

<div class="post-metadata">

**Author:** ![thibaultcha](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thibaultcha/32/340_2.png) [@thibaultcha](https://discuss.konghq.com/u/thibaultcha)\
**Post date:** [July 25, 2018, 3:10pm UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/4 "2018-07-25T15:10:37Z")

</div>

Yes, you would be correct in that most likely, what you are asking for is not currently possible, given Kong has no integration with IAM roles as of today.

This other PR relates to the Lambda plugin though, not the proxy itself.

But again, an explanation of your use-case would be most helpful, this way we can ensure an existing PR (or future one) eventually supports it.

---

<div class="post-metadata">

**Author:** ![neoshadybeat](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/neoshadybeat/32/217_2.png) [@neoshadybeat](https://discuss.konghq.com/u/neoshadybeat)\
**Post date:** [July 26, 2018, 8:57am UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/5 "2018-07-26T08:57:44Z")

</div>

My use case is the following one:

Use kong instead the AWS api gateway for lambdas and not pass the AWS credentails manually, using the IAM role of the machine that is executing kong

Kind regards  
Cayetano

---

<div class="post-metadata">

**Author:** ![thibaultcha](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/thibaultcha/32/340_2.png) [@thibaultcha](https://discuss.konghq.com/u/thibaultcha)\
**Post date:** [July 26, 2018, 9:06am UTC](https://discuss.konghq.com/t/aws-lambda-plugin-chain-provider/1555/6 "2018-07-26T09:06:24Z")

</div>

@neoshadybeat Tanks for sharing!