Help Center/ Migration Center/ Tool Guide/ FAQs/ What Can I Do If AK/SK Verification Fails?
Updated on 2024-12-02 GMT+08:00

What Can I Do If AK/SK Verification Fails?

Symptom

When you tried to register an Edge device to MgC, a message was displayed indicating that the AK/SK authentication failed.

Possible Causes

Possible causes are:

  • The entered AK or SK is incorrect.
  • The AK/SK pair has been deleted or disabled.
  • The programmatic access mode is not enabled for the account that owns the AK/SK pair.
  • The time on the server where Edge was installed is inconsistent with the local standard time.

Solutions

  • The entered AK or SK is incorrect.

    Check whether the entered AK/SK pair of the Huawei Cloud account is correct, especially whether any spaces or characters are missed during the copy. Enter the AK/SK pair for authentication again.

  • The AK/SK pair has been deleted or disabled.
    Choose My Credentials > Access Keys to check whether the AK is in the list.
    • If it is not, use an AK/SK pair in the list for authentication or create an AK/SK pair.
    • If it is, check whether it is disabled. If the AK is disabled, enable it.
  • The programmatic access mode is not enabled for the account that owns the AK/SK pair.
    1. Sign in to the management console.
    2. Click the username in the upper right corner and choose Identity and Access Management.
    3. In the navigation pane on the left, choose Users and click the username you used for migration.
    4. Check whether Programmatic access is selected for Access Type. If it is nor, click next to Access Type, select Programmatic Access, and click Yes

  • The time on the server where Edge was installed is inconsistent with the local standard time.
    1. On the Windows server where Edge was installed, open Date and Time.

    2. On the Date and Time page, enable Set time automatically and click Sync now to trigger time synchronization.
    3. Ensure that the time zone and time are the same as the local standard time, return to the Edge console, and query the MgC migration projects again.