# Create an IAM User

**URL:** <https://discourse.sst.dev/t/create-an-iam-user/92>\
**Category:** Chapter Comments\
**Created:** [May 9, 2018, 6:43pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92 "2018-05-09T18:43:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![anomalyinnovations](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/anomalyinnovations/32/10_2.png) [@anomalyinnovations](https://discourse.sst.dev/u/anomalyinnovations)\
**Post date:** [May 9, 2018, 6:43pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92/1 "2018-05-09T18:43:09Z")

</div>

_From @jayair on Mon Apr 10 2017 00:56:53 GMT+0000 (UTC)_  
  
Link to chapter - [http://serverless-stack.com/chapters/create-an-iam-user.html](http://serverless-stack.com/chapters/create-an-iam-user.html)  
  
_Copied from original issue: [https://github.com/AnomalyInnovations/serverless-stack-com/issues/13](https://github.com/AnomalyInnovations/serverless-stack-com/issues/13)_

---

<div class="post-metadata">

**Author:** ![anomalyinnovations](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/anomalyinnovations/32/10_2.png) [@anomalyinnovations](https://discourse.sst.dev/u/anomalyinnovations)\
**Post date:** [May 9, 2018, 6:43pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92/2 "2018-05-09T18:43:10Z")

</div>

_From @SherpaPsy on Thu Apr 20 2017 08:28:59 GMT+0000 (UTC)_  
  
I wonder if there is a way to reduce the security exposure this creates. I am going to do the cli development and testing on a small ec2 instance (which can be stopped and started to keep costs down), and assign a role to it rather than using credentials. This also bypasses the need to install the aws cli, and hopefully won’t present any issues installing required software!

---

<div class="post-metadata">

**Author:** ![gm-spacagna](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/gm-spacagna/32/612_2.png) [@gm-spacagna](https://discourse.sst.dev/u/gm-spacagna)\
**Post date:** [October 2, 2019, 2:41pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92/3 "2019-10-02T14:41:54Z")

</div>

It does not sound a good idea to me to grant admin permissions to serverless that can be triggered by any developer in continuous integration to execute custom script.  
Is there a more limited policy version you recommend?  
Should we separate the policy for cloud formation and the policy to deploy lambdas into existing resources?

---

<div class="post-metadata">

**Author:** ![jayair](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sst.dev/jayair/32/9_2.png) [@jayair](https://discourse.sst.dev/u/jayair)\
**Post date:** [October 9, 2019, 8:00pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92/4 "2019-10-09T20:00:34Z")

</div>

Yeah for sure. These are meant to be used on your local machine.

For ones that you want to use in your CI, I would create a more restricted role. We talk about it a little here - [https://seed.run/docs/customizing-your-iam-policy](https://seed.run/docs/customizing-your-iam-policy)

---

<div class="post-metadata">

**Author:** ![johnAtTrigram](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@johnAtTrigram](https://discourse.sst.dev/u/johnAtTrigram)\
**Post date:** [February 11, 2023, 10:35pm UTC](https://discourse.sst.dev/t/create-an-iam-user/92/5 "2023-02-11T22:35:11Z")

</div>

Amazon changed the UI for creating users, the guide is outdated