I added a cross-account role using the cf template for 10+ AWS accounts, all part of the same organization. The roles are correct and they are verified when adding the credentials to lucid. Problem starts when doing the import process, it gives me an error telling me it had trouble importing/updating the data from the datasets.
Starting checking and the only different thing (I’ve done this process many time) I can see is this:
The scope, before, always used to say “account” in the scope section, but now all of these new credentials say “organization” in the scope section. Anyone know why this happens, and how to fix it?
- The stack was successfully created in all accounts.
- All the roles have the necessary trust policy and policies, including readonlyaccess.
- The credentials creation process in lucid goes ok but it’s the importing process that fails.
- The only different thing with past imports is the last detail mentioned, the “scope” section. When it say account it works, when its says organization it doesn’t. Adding SS for reference:
