Enabling Google services and configuring service accounts

Before you can begin a migration, you must perform the steps below in the sections:

Enabling the Cloud SDK and required services
Configuring service accounts

Enabling the Cloud SDK and required services

All Migrate for Anthos and GKE users must configure the Cloud SDK and enable the required Google services.

Preparing the Cloud SDK

To prepare gcloud:

Install and initialize the Cloud SDK.
Update Cloud SDK:
```
gcloud components update
```
Make sure that Cloud SDK is authorized to access your data and services:
```
gcloud auth login
```
A new browser tab opens and you are prompted to choose an account.
Set the credentials required to access a Cloud Storage bucket.

For an individual user, use the following gcloud command:
```
gcloud auth application-default login
```
A new browser tab opens and you are prompted to choose an account.

Alternatively, if you are using a service account, set the GOOGLE_APPLICATION_CREDENTIALS environment variable to the path of the JSON file that contains your service account key:
```
export GOOGLE_APPLICATION_CREDENTIALS="[PATH]"
```

Enabling required services

Migrate for Anthos and GKE requires that you enable the following Google services:

Name	Title
`servicemanagement.googleapis.com`	Service Management API
`servicecontrol.googleapis.com`	Service Control API
`cloudresourcemanager.googleapis.com`	Cloud Resource Manager API
`compute.googleapis.com`	Compute Engine API
`container.googleapis.com`	Kubernetes Engine API
`containerregistry.googleapis.com`	Google Container Registry API
`cloudbuild.googleapis.com`	Cloud Build API

To confirm that the required services are enabled:

gcloud services list

If you do not see the required services listed, enable them:

gcloud services enable servicemanagement.googleapis.com servicecontrol.googleapis.com cloudresourcemanager.googleapis.com compute.googleapis.com container.googleapis.com containerregistry.googleapis.com cloudbuild.googleapis.com

For more information about the gcloud services, see gcloud services.

Configuring service accounts

A service account is a special kind of account used by an application or a virtual machine (VM) instance, not a person. Applications use service accounts to make authorized API calls.

For example, a Compute Engine VM may run as a service account, and that account can be given permissions to access the resources it needs. This way the service account is the identity of the service, and the service account's permissions control which resources the service can access.

When using Migrate for Anthos and GKE, you create two service accounts:

A service account used by Migrate for Anthos and GKE to access Container Registry and Cloud Storage. This service account is required for Migrate for Anthos and GKE components to be able to access the Container Registry and to access a Cloud Storage bucket. If you are not using these data repositories, you do not have to define this service account. See Defining data repositories for more.
A service account for using Compute Engine as a migration source. This service account is used to access Compute Engine resources when migrating Compute Engine VMs. If you are not using Compute Engine as a migration source then you can omit this service account.

Best practices when using service accounts

As a best practice, create a separate service account in the same project as you are using for Migrate for Anthos and GKE. Then assign the service account only the permissions necessary to perform the required operation. In that way, you limit the permissions associated with the service account.

Creating a service account for accessing Container Registry and Cloud Storage

Create a service account with the storage.admin role and pass it when you install Migrate for Anthos and GKE components:

Create the m4a-install service account:

gcloud iam service-accounts create m4a-install \
 --project=PROJECT_ID

Grant the storage.admin role to the service account:
```
gcloud projects add-iam-policy-binding PROJECT_ID  \
 --member="serviceAccount:m4a-install@PROJECT_ID.iam.gserviceaccount.com" \
 --role="roles/storage.admin"
```
Note: Depending on the security configuration of your project, you might be prompted to select a condition. Often selecting the option of None is correct, but confirm that with your security team.

Download the key file for the service account:

gcloud iam service-accounts keys create m4a-install.json \
 --iam-account=m4a-install@PROJECT_ID.iam.gserviceaccount.com \
 --project=PROJECT_ID

After downloading the service account key as a JSON file, you can install Migrate for Anthos and GKE on the destination Google Kubernetes Engine cluster using the procedure described in Installing Migrate for Anthos and GKE.

Creating a service account for using Compute Engine as a migration source

To use Compute Engine as a migration source, create a service account with the compute.viewer and compute.storageAdmin roles:

Create the m4a-ce-src service account:

gcloud iam service-accounts create m4a-ce-src \
 --project=PROJECT_ID

Grant the compute.viewer role to the service account:
```
gcloud projects add-iam-policy-binding PROJECT_ID  \
 --member="serviceAccount:m4a-ce-src@PROJECT_ID.iam.gserviceaccount.com" \
 --role="roles/compute.viewer"
```
Note: Depending on the security configuration of your project, you might be prompted to select a condition. Often selecting the option of None is correct, but confirm that with your security team.

Grant the compute.storageAdmin role to the service account:

gcloud projects add-iam-policy-binding PROJECT_ID  \
 --member="serviceAccount:m4a-ce-src@PROJECT_ID.iam.gserviceaccount.com" \
 --role="roles/compute.storageAdmin"

Download the key file for the service account:

gcloud iam service-accounts keys create m4a-ce-src.json \
 --iam-account=m4a-ce-src@PROJECT_ID.iam.gserviceaccount.com \
 --project=PROJECT_ID

After downloading the service account key as a JSON file, you can create a source for migrating Compute Engine workloads. See Adding a migration source.

What's next

Configuring a cluster overview