# SUSE Rancher setup permission issue

**URL:** <https://forums.suse.com/t/suse-rancher-setup-permission-issue/40886>\
**Category:** Rancher Setup Public Cloud\
**Created:** [June 9, 2023, 6:52am UTC](https://forums.suse.com/t/suse-rancher-setup-permission-issue/40886 "2023-06-09T06:52:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![EnisMurati](https://avatars.discourse-cdn.com/v4/letter/e/85f322/32.png) [@EnisMurati](https://forums.suse.com/u/EnisMurati)\
**Post date:** [June 9, 2023, 6:52am UTC](https://forums.suse.com/t/suse-rancher-setup-permission-issue/40886/1 "2023-06-09T06:52:58Z")

</div>

Hello,  
We have setup SUSE Rancher via AWS Marketplace. We have tried both versions available v20230606 or v20230503. With both versions we have the same permissions issue during the Rancher Setup wizard. IAM permission and role are OK.  
One thing I have to mention is that we are using AWS multiple accounts setup and external IdP.  
We have tested on single AWS account and it works fine.  
Can you help us on this issue?  
Regards,  
Enis

---

<div class="post-metadata">

**Author:** ![bear454](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bear454/32/9125_2.png) [@bear454](https://forums.suse.com/u/bear454)\
**Post date:** [June 16, 2023, 11:48pm UTC](https://forums.suse.com/t/suse-rancher-setup-permission-issue/40886/2 "2023-06-16T23:48:43Z")

</div>

For more complex setups, we recommend doing a manual deployment of Rancher, per the [docs](https://ranchermanager.docs.rancher.com/v2.6/pages-for-subheaders/installation-and-upgrade).

---

<div class="post-metadata">

**Author:** ![kevinayres](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kevinayres/32/7921_2.png) [@kevinayres](https://forums.suse.com/u/kevinayres)\
**Post date:** [June 22, 2023, 7:48pm UTC](https://forums.suse.com/t/suse-rancher-setup-permission-issue/40886/3 "2023-06-22T19:48:31Z")

</div>

Just noticing this Enis. Did you find resolution? While ‘Rancher Setup’ is designed to deploy into a single AWS IAM account, there should be no issue connecting to manage cluster API addresses across multiple accounts using key based or other authentication. Curious if you got over the hurdle.