Onboarding Issues

Our onboarding process focuses on users integrating into our Cross4Cloud platform using the credentials they obtain from their respective cloud providers. However, you may encounter some issues during this process.

When you encounter errors during the onboarding process, we aim to provide you with helpful guidance right within our console. By reviewing the titles below, you can access detailed instructions tailored to address specific issues. Once you've applied these solutions, feel free to retry the process using the Retry button on our console.

---

Error Messages

Reviewing the error message you encountered on our onboarding screen and then checking the relevant section may help us provide you with a better solution.

By reviewing the titles below, you can access detailed instructions tailored to address specific issues. Once you've applied these solutions, feel free to retry the process using the Retry button on our console.

Quota Exceeded

This error is a warning that the allocated quota limit for a particular resource or service has been exceeded. This error can usually be resolved by resource management from the provider's own console. Depending on which provider you are getting an error for, you can go to the relevant section

Amazon Web Service

In Amazon Web Services (AWS) you can request to increase your relevant resource quota with the instruction in here.

info

It may take longer than expected to receive a response to your request for a limit increase. Please check the status of your request repeatedly throughout the process.

Google Cloud Platform

In GCP you can manage your quotas or request a quota increase. For some resources, there is no support for quota increases, so the most effective approach may be to strategically reduce the number of relevant resources in your configuration.

Here are steps you can take to reduce the number of resources:

1. Open the Google Cloud Console.

2. In the left navigation menu, navigate to Quotas.

3. Here you will see a list of existing resources in your project and the details about it. On that page you can mange them by your needs.

warning

If you want to request a quota increase, you can follow the instructions here and get more detailed information.

Google Cloud support will review your request, and you will receive notifications about the status of your request via email or in the Google Cloud Console. The approval process may take some time. It's essential to provide accurate and detailed information in your request to facilitate the review process.

Microsoft Azure

In Microsoft Azure you can request to increase your resource quota by following the instructions here. You will receive a response to your azuredan limit increase request within a reasonable time.

If the above solutions are not sufficient for your problem, or if you cannot find the necessary support from your providers, you may want to consider the following;

• Feel free to reach out to us by providing a detailed description of the issue, along with any relevant images or error messages that you can attach to the email.
• You can open a new account on the same provider and come to our console with the credentials of that account and this will solve your problems in this regard.

Permission Denied

The error message suggests that the service account lacks the necessary permissions for the specified resource, which could include, but is not limited to, the specified bucket. You can follow the steps below to check the required permissions:

• Make sure you follow the steps in the section on Getting Credentials exactly for the relevant provider.

• Go to the console of the relevant provider and check if the roles we created in the Getting Credentials phase have the permissions specified in the error message. If the role is not have the relevant permissions please add them to the role. For that action you can proceed with the relevant provider instructions.

Amazon Web Services

1. Sign in to the AWS Management Console and open the IAM console.
2. In the navigation pane, choose Users.
3. Choose the name of the user whose you created earlier on Getting Credentials - User Creation steps.
4. Choose the Permissions tab. If necessary, open the Permissions policies section.

In this section, you can view all the policies attached to the user. Ensure that none of the required policies are missing. You can review the necessary permissions from the list provided in the relavtive service Permission Assignment step. If the required policies are missing:

1. Choose Add permissions and then choose Attach policies.
2. In the list of Permissions policies, select the check box next to the names of the policies to attach. You can use the search box to filter the list of policies by type and policy name.
3. Click on the Next button and then on the opened page, click on the Add Permission button.

After making these settings, you can retry your operation in the console.

Google Cloud Platform

1. In the Google Cloud console, go to the Roles page.
2. Using the drop-down list at the top of the page, select the project or organization that contains the role that you want to edit.
3. Under the instructions of the service you want to use, click on the role you created in the Getting Credentials - Custom Role Creation step. This will open the details page for that role. You can review the permissions and identify any missing ones. If there are any missing permissions, proceed with the following steps.
4. Click on the three-dot button located in the row of the relevant role and select the Edit option.
5. Click Add Permissions to add new permissions to the role.
6. Click Update to Save the edited role.

After making these settings, you can retry your operation in the console.

Microsoft Azure

1. Go to the search bar and search for Subscriptions, then click Subscriptions under Services.
2. Click on your relevant Subscription Name under Subscriptions.
3. Click on Access Control (IAM) from the left-hand menu, then navigate to the Roles tab.
4. Search for the custom role that we created which named as C4C Custom Role.
5. Click on the three-dot button located in the row of the relevant role and select the Edit option.
6. Then, go to the Permissions tab, where you can add the missing permissions.
7. Then click the +Add permissions button which is located at the top.
8. Search for the relevant permission on that page. After selecting the relevant permissions click Add button.
9. Finally, click the Review+update button to update the permissions for the custom role.

After making these settings, you can retry your operation in the console.

Concurrent Modification

This error typically occurs when the specified bucket name is already in use by another user or project. To resolve the issue;

• This error can also occur in the case of another request updating entity. In that case please wait for the ongoing modification and then retry the operation.

Unauthorized Client

The error you are encountering is typically specific to Azure AD authentication, but you may face similar issues in other cloud providers (AWS, GCP). The error indicates that the application with the specified identifier was not found in the directory. The root cause may vary, but the general troubleshooting approach remains similar. You can solve the problem by performing the following checks:

Amazon Web Services (AWS)

• Ensure that your AWS credentials (access key, secret key) are correctly configured. For that you can check our User Guide.
• Verify that the credentials have the necessary permissions.

Google Cloud Platform (GCP)

• Ensure that the service account used for authentication has the required permissions in GCP.
• Confirm that the GCP account specified in your configuration exists and is active.

Microsoft Azure

• Double-check the application ID to ensure it is correct and that it exists in the specified directory.
• Confirm that the application has been properly installed and consented to in the Azure Portal.

Missing Service Principal

Encountering the Missing Service Principal error can have several potential causes, but here are a few fundamental solutions to address the issue:

• Incorrect or Missing Application ID: Ensure that the provided application ID(client ID) is correct and complete. Verify the application ID details through the Azure Portal or you can follow the instruction for reviewing the Azure Credentials from here.

• Deleted, incorrectly configurated Service Principal: The service principal can be deleted or incorrectly configurated. For checking the service principal details follow the instrutions below:

  1. Go to Azure Portal and log in to your account.
  2. Go to the search bar and look for App Registration, then choose App Registration under Services.
  3. In the opening page look up for the app that you registered in our begginer guide and click it.
  4. Click on the Certificate & secrets section in the menu that opens on the left.

  In that page, you can see all the client secrets connected with that application. If you don't see anything on this page, you have probably deleted the relevant client. You can follow the guide step again for creating the new one.

Disabled APIs

If you encountered this error during onboarding, it indicates that there might have been an issue with enabling the necessary APIs as part of the GCP - Getting Credentials steps. To resolve the error, follow the steps below:

1. Go to GCP Console and log in to your account.
2. Navigate to the project you will use in our platform. Open the Navigation Menu by clicking on the icon in the top left corner of the page. Click on the APIs and Services in the navigation menu.
3. On the displayed page, review the list of enabled APIs for your project.
4. Confirm whether the necessary API is enabled.

If the required API is not enabled, you can enable it by following the instructions in the Enabling APIs step on the relevant service page.

Onboarding Process Interruption

In some cases, you may encounter difficulties completing the onboarding process due to issues such as internet interruptions or accidentally closing the browser tab. In that cases we save your process, and allow you to resume where you left off.

• After ensure that your internet connection is stable, you can reopen the our onboarding page and continue your process.