Troubleshooting Cloud Connectors¶
Common issues and solutions when connecting your cloud marketplace accounts.
AWS Marketplace¶
CloudFormation Deployment Issues¶
Stack Creation Failed: "Resource Already Exists"¶
Symptom: CloudFormation fails with error about existing resources.
Cause: A stack with the same name already exists.
Solution:
- Go to CloudFormation console
- Find the existing
vell-marketplace-rolestack - Delete it
- Try deployment again
Alternatively, use a different stack name when deploying.
Stack Creation Failed: "Insufficient Permissions"¶
Symptom: CloudFormation fails to create the IAM role.
Cause: Your AWS user lacks IAM permissions.
Solutions:
Ask your administrator for these permissions:
Use the Email IAM Administrator button in Vell's wizard to send deployment instructions to someone with IAM permissions.
Role Validation Issues¶
Validation Failed: "Role Not Found"¶
Symptom: Validation fails saying the role doesn't exist.
Causes & Solutions:
- Stack not fully deployed
- Wait for CloudFormation status to show
CREATE_COMPLETE -
Refresh the CloudFormation console
-
Wrong AWS Region
- The role must be created in
us-east-1 -
Check your CloudFormation console region selector
-
Incorrect Role ARN
- Copy the ARN from CloudFormation Outputs tab
- ARN should match:
arn:aws:iam::YOUR-ACCOUNT:role/vell-marketplace-role
Validation Failed: "Access Denied"¶
Symptom: Validation fails with access denied error.
Causes & Solutions:
- Incorrect External ID
- Use the exact External ID from your Vell wizard
- External IDs are case-sensitive
-
Don't manually type it - use the Copy button
-
Trust Policy Misconfigured
- The role must trust Vell's account:
253265132499 -
Verify trust policy in IAM console:
- Go to IAM → Roles
- Find
vell-marketplace-role - Check Trust Relationships tab
-
Stack Deployment Failed
- Check CloudFormation Events tab for errors
- If stack failed, delete it and redeploy
Validation Failed: "Insufficient Permissions"¶
Symptom: Role validates but shows insufficient permissions.
Cause: IAM policy wasn't attached correctly.
Solution:
- Go to IAM → Roles →
vell-marketplace-role - Check Permissions tab
- Should have
VellMarketplaceReadOnlypolicy - If missing, delete stack and redeploy
Connection Issues¶
Connection Shows as "Pending"¶
Symptom: Connection stuck in pending state.
Solutions:
- Complete Validation
- Make sure you clicked "Validate Role" in Step 4
-
Role must pass validation before activation
-
Check Browser Console
- Open browser developer tools (F12)
- Look for JavaScript errors
-
Try a different browser
-
Session Expired
- Wizard sessions expire after 24 hours
- Restart the connection wizard
Connection Shows as "Failed"¶
Symptom: Connection shows failed status.
Causes:
- Role was deleted or modified
- Trust relationship was changed
- External ID mismatch
Solution:
- Delete the connection in Vell
- Delete the CloudFormation stack
- Start over with a fresh deployment
Email Feature Issues¶
Email Not Received¶
Symptom: IAM administrator didn't receive the email.
Solutions:
- Check Spam Folder
- Email might be in spam/junk
-
Add
noreply@vell.aito contacts -
Verify Email Address
- Double-check for typos
-
Resend from wizard
-
Corporate Email Filters
- Check with IT if emails from
vell.aiare blocked -
Whitelist
@vell.aidomain -
Queue Delay
- Emails are queued and may take 1-2 minutes
- Wait a bit and check again
Can't Find CloudFormation Template Attachment¶
Symptom: Email received but template attachment is missing.
Solutions:
- Download from Vell Wizard
- Return to wizard Step 3
-
Click "Download Template" button
-
Download from S3
- Access public template URL:
https://templates.vell.ai/templates/vell-aws-marketplace-role.yaml
General Issues¶
Browser Compatibility¶
Supported Browsers:
- ✅ Chrome 90+
- ✅ Firefox 88+
- ✅ Safari 14+
- ✅ Edge 90+
Common Browser Issues:
- Clear cache and cookies
- Disable ad blockers
- Try incognito/private mode
Session Timeouts¶
Symptom: "Session expired" error during wizard.
Cause: Wizard sessions expire after 24 hours of inactivity.
Solution:
- Start the wizard again
- Your External ID will remain the same
- Complete deployment within 24 hours
Performance Issues¶
Symptom: Slow loading or timeouts.
Solutions:
- Check Internet Connection
- Ensure stable connection
-
Try from different network
-
AWS Console Slow
- CloudFormation deployment depends on AWS
-
Check AWS Status Page
-
Clear Browser Cache
- Clear site data
- Restart browser
Still Need Help?¶
If your issue isn't covered here:
- Check the FAQ
-
Visit our FAQ page
-
Contact Support
- Email: support@vell.ai
-
Include:
- Error message (screenshot)
- CloudFormation Events tab (screenshot)
- Role ARN (if applicable)
- Browser and OS version
-
Join Office Hours
- Schedule a screen share with our team
-
Available Monday-Friday 9am-5pm PST
-
Check Status Page
- Visit status.vell.ai
- See if there are ongoing issues