Troubleshooting Guide

Common issues and their solutions for TagOps.

Account Issues

Account Verification Failed

Symptoms: Cannot verify AWS account during setup

Solutions:

  1. Verify CloudFormation stack completed successfully
  2. Check IAM role name matches exactly (case-sensitive)
  3. Confirm External ID is correct

Global resources arent being arent scanned

Symptoms: Your global resources like IAM arent recognized by TagOps

Solutions:

  1. Verify CloudFormation stack completed successfully (including us-east-1 region)
  2. Check IAM role name matches exactly (case-sensitive)
  3. Confirm External ID is correct

CloudTrail Warning

Symptoms: Warning that CloudTrail is not enabled

Impact: Event-based tagging won't work

Solutions:

  1. Enable CloudTrail in your AWS account
  2. Configure multi-region trail
  3. Check trail status in AWS Console

Account Permissions Warning

Symptoms: Warning that TagOps IAM Role missing permissions

Impact: Some tagging functionaly won't work

Solutions:

Update TagOps Onboarding CloudFormation Stack

  • Click the Edit button on the account with the warning and select "Update CloudFormation Stack."
  • Choose "Replace existing template" and paste the following URL:
    https://s3-prod-tagops-public-183017936296-eu-west-1.s3.eu-west-1.amazonaws.com/customer_onboarding_cf.yaml
  • Continue with the CloudFormation deployment flow as you did during the Account Onboarding CloudFormation stack provisioning.

CloudFormation Update Fails

Issue: Stack update fails with validation error

Solutions:

  • Verify region codes are valid AWS regions
  • Check region format: region-name-number (e.g., us-east-1)
  • Ensure no spaces in comma-separated list
  • Review CloudFormation events for specific error messages

Regions Not Appearing in TagOps

Issue: Updated CloudFormation stack but regions don't show in TagOps

Solutions:

  1. Verify stack update completed successfully
  2. Click Verify Account in TagOps to refresh configuration
  3. Click Update Account to apply changes

Scanning Issues

No Resources Found

Symptoms: Inventory is empty after scan

Solutions:

  1. Verify scan is enabled in Settings
  2. Check allowed regions include where resources exist
  3. Confirm allowed services includes resource types
  4. Review service configuration in Settings

Tagging Issues

Tags Not Applied

Symptoms: Scan runs but tags aren't applied

Solutions:

  1. Verify rules are enabled
  2. Check rule conditions match resources

Wrong Tags Applied

Symptoms: Resources have incorrect tags

Solutions:

  1. Review rule conditions and actions
  2. Check rule priority
  3. Verify template values are correct
  4. Look for rule conflicts

Failed to Tag Resources

For detailed information about resources that fail to be tagged, see the Failed to Tag Resources documentation.

Performance Issues

Slow Dashboard Load

Symptoms: Dashboard takes long to load

Solutions:

  1. Clear browser cache
  2. Check network connectivity

API Issues

401 Unauthorized

Symptoms: API calls return 401 error

Solutions:

  1. Token expired - log in again
  2. Invalid token - clear cache and re-login
  3. Check Authorization header format

403 Forbidden

Symptoms: API calls return 403 error

Solutions:

  1. User lacks required permissions
  2. Check user role (Administrator/PowerUser/ReadOnly)
  3. Verify subscription is active
  4. Contact administrator

UI Issues

Buttons Disabled

Symptoms: Cannot click buttons in UI

Solutions:

  1. Check user permissions (may be ReadOnly)
  2. Verify required fields are filled
  3. Check for validation errors
  4. Reload page

Account Not Appearing After Adding

Symptoms: Account doesn't show in table

Solutions:

  • Wait for account initialization (up to 30 seconds)
  • Click Refresh button
  • Check browser console for errors
  • Verify account was actually added (check for success notification)

Cannot Remove Account

Symptoms: Remove button disabled or fails

Solutions:

  • Check your permissions (requires PowerUser or Administrator)
  • Verify account is not in use by active scans
  • Try refreshing the page
  • Contact support if issue persists

Reporting Issues

When contacting support, include:

  • Description of the issue
  • Steps to reproduce
  • Screenshots if applicable
  • Browser and version
  • Time when issue occurred
  • Error messages from console

You can report issue via 'Support & Feedback' page in the console