> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/troubleshooting-aws-role-assumptions-in-same-aws-account-or-cross-accounts.md).

# Troubleshooting AWS Role Assumptions in same AWS account or cross-accounts

### Issue <a href="#issue" id="issue"></a>

Administrators may encounter role-assumption planning complications. This article is created to help with some of the role-assumption issues. The most relevant Spinnaker services that won't be able to make a role assumption in AWS but may still rely heavily on it are:

* `Clouddriver` When defining providers for accounts and Lambda targets\* `Terraformer` When running Terraform actions in the same AWS account or cross-accounts.\* `Kayenta` When setting metrics, configuration, and object storage Depending on a company's setup and security policy, these situations can be challenging.

### Cause <a href="#cause" id="cause"></a>

An incorrect role assumptions setup in AWS might occur due to various reasons:

* complex configurations\* security policies around AWS cross-account role assumptions