If you encounter any issues during the onboarding or deployment process, follow these steps to diagnose and resolve them efficiently:
Step1: Verify All Permissions Are Correctly Set
Ensure that the necessary IAM permissions are granted for the user or role performing the deployment. Missing or insufficient permissions may cause failures during onboarding.
- Check IAM role and policy assignments
- Ensure the user has administrative privileges or the required set of permissions
- Confirm that AWS services involved in the deployment have the necessary permissions
Step2: Clean Up Previous Failed Onboarding Attempts
If you are retrying the onboarding process due to a previous failure, make sure all remnants of the prior attempt are removed before trying again.
- Delete any incomplete AWS CloudFormation stacks
- Remove any IAM roles or policies that may have been created in the failed attempt
- Ensure there are no residual configurations that could cause conflicts in a new attempt
Step3: Verify Deployment in the Correct AWS Region
AWS services are region-specific, and deploying in an incorrect region can lead to failures.
- Double-check that you are operating in the intended AWS region
- Verify the selected region in the AWS Management Console or CLI
- Ensure that all required AWS resources are available in that region
Step4: Confirm Required Policies Are Attached to the User
The onboarding process requires the user executing the deployment to have the correct IAM policies assigned. The required privileges include:
- AWS CloudFormation Execution – Ability to create, update, and delete CloudFormation stacks
- IAM Role and Policy Creation – Permissions to create and manage IAM roles and policies
- Lambda Execution – Permissions to deploy and execute AWS Lambda functions and reach to our server to acknowledge successful onboarding.
- Service-Specific Permissions – Depending on the services being configured, additional permissions may be needed for scan for which policy is automatically created in cloud formation, manually with role and policy creation steps (e.g., read S3 configuration, EC2, Security Groups, etc. or patching permissions such as create, update or delete.)
Use the AWS IAM Console or AWS CLI to confirm that the logged-in user has the required permissions before proceeding.
Step5: Contact Support if Issues Persist
If you have verified the above steps and are still facing issues, reach out to the support team for assistance.
- Provide detailed logs and error messages
- Mention the AWS services and region you are working with
- Describe the steps already taken for troubleshooting
