> * Having to assume a role in another account can complicate code, especially if you may or may not have to assume a role depending on the circumstances. One

> * Having to assume a role in another account can complicate code, especially if you may or may not have to assume a role depending on the circumstances. One workaround I usually implement for this is to always have to assume a role. Meaning that, basically, your base permissions only allow you to assume roles. To actually do the job, you need a separate one, in whichever account. This way, it's also easier to standardize roles across accounts. A action requires R role.