Check account linking, user access and your connected opportunity workflows in the AWS Console. Start with what your team can verify now.
Review AWS migration guidanceCompany-email sign-inPartner Central identity
Linked account. IAM access.Roles and permissions
AWS Partner Central is available in the AWS Console. AWS guidance says partners using legacy company-email access need account linking and migration.
After migration, users access Partner Central through the linked AWS account with the appropriate IAM roles and permissions.
Review the linked account, users and workflows:
Review which users need Partner Central access and the permissions they should receive.
AWS says the linked account becomes permanent after migration. Review it before initiating the move.
Test the workflows your team depends on, rather than assuming every connector is already ready.
AWS migration does not establish Azure or GCP readiness. Review each cloud workflow against its own current guidance.
For Microsoft, review the referral fields and Marketplace information that apply to your opportunity. For GCP, review the relevant partner and opportunity workflow.
Keep these reviews connected at the pipeline level, while respecting each provider's access and program rules.
Microsoft announced App Accelerate as a unified offer for incentives, benefits and co-sell support. Confirm current terms and availability directly with Microsoft.
Do not treat an AWS account migration, a transactable listing or a connected CRM as automatic App Accelerate eligibility.
Use a separate review for Microsoft Marketplace and co-sell operating requirements.
Check the linked AWS account and the permissions your opportunity workflow uses.
Review current Microsoft referral and Marketplace guidance for the opportunity.
Bring AWS, Azure and GCP work together without treating one provider's status as another provider's approval.
Start with the account, access and workflow context your team needs to check.
Review plans and Starter trialFollow the AWS migration process for account linking, IAM access and initiating the move. AWS says migration typically takes 2 to 6 hours and recommends non-business hours because users cannot access Partner Central during migration.
Vela can support a connected co-sell operating workflow. Verify the integration and access in your account rather than assuming a universal setup time or no-downtime guarantee.
Review the AWS instructions and coordinate with your IAM administrator.
AWS says partners using legacy company-email credentials need linking and migration. Partners registered directly in the new console without legacy access do not need linking.
AWS says the linked account is permanent after migration. Review the account choice before starting.
Map users to appropriate IAM policies with your IAM administrator, following the AWS migration instructions.
AWS says migration typically takes 2 to 6 hours depending on data, and users cannot access Partner Central while it runs.
Use the current AWS migration and account-linking guidance for your account state. This guide is not a migration-status check.
Review the connected opportunity workflow your team relies on after migration.
Review plans and Starter trial