2.2.1 Sign-up Overview

The MySQL HeatWave on AWS sign-up process has two starting points, one for users with an Oracle Cloud Account, and one for users without an Oracle Cloud Account.

If you have an existing Oracle Cloud Account, the user that you register with must either be a member of the Administrators group in the OCI Default identity domain or have the following permissions:

• manage heatwave-registration

• manage policies

• manage domains

• manage groups

• read limits

• inspect tenancies

For information on creating policies, see Getting Started with Policies.

If you do not have an Oracle Cloud Account, the OCI user account you create during the sign-up process is automatically added to the Administrators group in the OCI Default identity domain. For more information, see The Default Identity Domain.

After signing into or registering for an Oracle Cloud Account, you are guided through the MySQL HeatWave on AWS sign-up process by the Set up MySQL HeatWave on AWS dialog, which takes you through requesting an OCI account upgrade, subscribing to an OCI region, requesting a registration limit increase, and provisioning the MySQL HeatWave on AWS service.

Important

MySQL HeatWave on AWS requires a subscription to the US East (Ashburn) region on OCI. The service is integrated with OCI in that region for identity and access management and billing.

After you subscribe your tenancy to the US East (Ashburn) region, you cannot unsubscribe it. Your identity data is replicated to this region and other services might be permitted to replicate your data to it. If this region is in a different legal jurisdiction than the regions that you currently occupy, there could be legal implications with regard to GDPR and other privacy legislation.

Before signing up for the MySQL HeatWave on AWS Service, verify that the subscription to the US East (Ashburn) region is not going to cause any issues for you and your organization.

The account upgrade, region limit increase, and registration limit increase requests may take some time to complete. As a result, there may be a waiting period at these stages, requiring you to return later and resume the setup once the requests are completed. The Set up MySQL HeatWave on AWS dialog keeps track of where you are in the setup process. You can return to the setup dialog at any time to check the status of your requests and continue the setup.

Warning

It is recommended that you do not change your Oracle Cloud Account name after provisioning the MySQL HeatWave on AWS service, as it can cause a loss of access to the MySQL HeatWave on AWS service, requiring Support assistance.