Troubleshooting

This page lists common errors and known issues encountered while integrating AWS IAM with Zluri, and instructions on how to fix them.

If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].

When does this error occur?

While connecting AWS IAM to Zluri with insufficient permissions or incorrect Role ARN/ExternalId.

How to resolve:

Ensure the user has the necessary permissions to read users.
Double-check that the Role ARN and ExternalId are correct.
If you see this error during sync, the permissions for the user who connected the integration may have been modified or revoked. Restore the required permissions and reconnect the integration.

When does this error occur?

How to resolve:

Reconnect the integration using the correct and active Role ARN value.
If the Role ARN used to connect the integration is now expired or revoked, generate a new Role ARN and reconnect.

When does this error occur?

While connecting AWS IAM to Zluri with insufficient permissions to read billing info, or with incorrect Role ARN/ExternalId.

How to resolve:

Always copy and paste the Role ARN and ExternalId directly from AWS to avoid typos or missing characters.
If you continue to face issues, verify that your permissions, Role ARN, and ExternalId are active and have not been changed or revoked in AWS.

If your issue is not listed here, please contact Zluri at [email protected] with the error details for further assistance.

Updated about 15 hours ago