Transferring an Existing AWS Organization to VeUP Ignite
We make onboarding seamless. If you’re joining VeUP Ignite with an existing AWS Organization, we’ll handle the transition together on a quick 30-minute onboarding call with our FinOps team.
Here’s what we’ll cover:
What We Do During the Call
- Change the root email address of your AWS Management Account to one managed by VeUP
- Set up a secure IAM Role (VeUPBillingAdminRole) to give our team limited billing access — never root
- Update billing and tax details to reflect VeUP as your AWS reseller
- Deploy VeUP’s cost management tooling via lightweight CloudFormation templates
View the IAM Role permissions »
Frequently Asked Questions
Why do you need to change the root email address?
We don’t need root access — just the root email address must reflect VeUP’s domain, as required by AWS for resellers like us.
You stay in control. We use an IAM role for daily access, not the root user.
We operate a shared credential model:
- VeUP holds the password
- You retain the MFA
This ensures both parties are required to access the root account — and only when strictly needed.
I use the root user for daily tasks — will I lose access?
You shouldn’t be using root for day-to-day work. AWS strongly recommends using IAM roles or IAM Identity Center instead.
We’ll help you get this set up during onboarding to ensure full operational access, without relying on root credentials.
What if we need root access in future?
Most tasks don’t require it — but if something critical does, we’ll work with you to access the account securely.
You can view AWS’s list of root-only tasks here »
Will I still receive AWS system alerts?
Yes. During onboarding, we’ll make sure your security and ops contacts are added to the account so you still receive all AWS notifications — even if the root email changes.
How can we monitor the root account for security?
We won’t access the root account after onboarding, but for peace of mind you can set up alerts for root login attempts.
Follow this guide to enable root user monitoring »