# AWS CLI Node

**URL:** <https://community.n8n.io/t/aws-cli-node/33618>\
**Category:** Feature Requests\
**Tags:** node\
**Created:** [November 30, 2023, 2:45am UTC](https://community.n8n.io/t/aws-cli-node/33618 "2023-11-30T02:45:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![prononext](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/prononext/32/14611_2.png) [@prononext](https://community.n8n.io/u/prononext)\
**Post date:** [November 30, 2023, 2:45am UTC](https://community.n8n.io/t/aws-cli-node/33618/1 "2023-11-30T02:45:25Z")

</div>

It would be really nice to have a AWS CLI node available. I am using a docker stack with a included AWS CLI service which I call via SSH node, but that is not a good and save way to go.

Any Ideas?

---

<div class="post-metadata">

**Author:** ![Jon](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jon/32/40174_2.png) [@Jon](https://community.n8n.io/u/Jon)\
**Post date:** [December 2, 2023, 9:53am UTC](https://community.n8n.io/t/aws-cli-node/33618/2 "2023-12-02T09:53:36Z")

</div>

Hey @prononext,

I am not sure on including the AWS CLI itself as that would then be another dependency we would have to worry about but you might be able to make a community node that includes it.

There may be another option as well if the CLI features you are using have API routes available.
