# Wildcarding accountId in serverless.yaml

**URL:** <https://forum.serverless.com/t/wildcarding-accountid-in-serverless-yaml/7053>\
**Category:** Serverless Framework\
**Tags:** cloudformation, variables, iam\
**Created:** [January 17, 2019, 9:28pm UTC](https://forum.serverless.com/t/wildcarding-accountid-in-serverless-yaml/7053 "2019-01-17T21:28:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![piorot](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/piorot/32/2956_2.png) [@piorot](https://forum.serverless.com/u/piorot)\
**Post date:** [January 17, 2019, 9:28pm UTC](https://forum.serverless.com/t/wildcarding-accountid-in-serverless-yaml/7053/1 "2019-01-17T21:28:16Z")

</div>

The serverless.yml I currently use has several iamRoleStatments that reference resources where \* is used for accountId. There are several posts here explaining how to handle referencing the real account id. The question is why should I care. What happens if never give real accountId but leave \*. Are there any risk? Why would someone specify an exact number here

Is my understanding correct that accountId is one for the whole organization and is not operating user specific?