Tool is unable to identify service account that i created on Grafana server as well as AWS managed grafana.

[parth741]

As per the usage document of amazon-managed-grafana-migrator I am able to identify the AWS managed garafana via
#amazon-managed-grafana-migrator discover --region us-west-2

I have also created service account with below command-
#aws grafana create-workspace-service-account --workspace-id g-abcdef5678
--grafana-role ADMIN
--name grafana_migration

As soon as i execute migrate command i get below error-

Skipping API key creation for https://*****.com/

Creating service account token for service account grafana_migration

error: ValidationException: Invalid Service Account id: grafana_migration
{
RespMetadata: {
StatusCode: 400,
RequestID: "df3d54ae-d0e8-4509-b137-42c2668e3583"
},
Message_: "Invalid Service Account id: grafana_migration"
}

Migration command that am using is-
#amazon-managed-grafana-migrator migrate --src-url https://***.com/ --src-api-key glsa_T**************** --dst g-.grafana-workspace.us-west-2.amazonaws.com --dst-service-account-id grafana_migration

I have a question too, does this tool migrates the datasources configured passwords from source?

[parth741]

@bonclay7 does migration tool migrates the configured password of data sources from grafana server to AWS managed grafana?

[serkanh]

@parth741 Which version are you migrating from, and to which version? If you're using version 8, you should first upgrade or migrate to Grafana version 9 instance. After successfully migrating to version 9, proceed with the upgrade to version 10. Please note that the commands differ slightly at each step.

[parth741]

Hi Team, I am migrating from onprem grafana v10 to aws managed grafana v10. Regards Parth Tripathi

…

On Thu, 11 Jul, 2024, 10:34 pm serkan haytac, ***@***.***> wrote: @parth741 <https://github.com/parth741> Which version are you migrating from, and to which version? If you're using version 8, you should first upgrade or migrate to Grafana version 9 instance. After successfully migrating to version 9, proceed with the upgrade to version 10. Please note that the commands differ slightly at each step. — Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG37ZVZJPHBU4MK3JSCAXCDZL23IZAVCNFSM6AAAAABJPWNWESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGQ2DKMBTGE> . You are receiving this because you were mentioned.Message ID: <aws-observability/amazon-managed-grafana-migrator/issues/30/2223445031@ github.com>

[carlosrodgut]

Hi @parth741,

Surely you already have found out the cause of the issue but just in case.

The value for --dst-service-account-id is a number assigned to the Service Account as ID.

aws grafana list-workspace-service-accounts --workspace-id <WORKSPACE_ID>

{
    "serviceAccounts": [
        [...]
        {
            "grafanaRole": "Admin",
            "id": "<ID>",
            "isDisabled": "false",
            "name": "grafana_migration"
        }
    ],
    "workspaceId": "<WORKSPACE_ID>"
}

The migration from a Grafana Server instance to Amazon Managed Grafana workspace can be performed this way:

amazon-managed-grafana-migrator migrate \
--src-url ${GRAFANA_SRC_URL} \
--src-api-key ${GRAFANA_SRC_API_KEY} \
--dst ${WORKSPACE_ID}.grafana-workspace.${AWS_REGION}.amazonaws.com \
--dst-service-account-id <ID>

Skipping API key creation for <GRAFANA_SRC_URL>

Creating service account token for service account <ID>

Migrating data sources:
[...]
✔ Migrated 60 data sources

Migrating folders:
[...]
✔ Migrated 75 folders

Migrating dashboards:
[..]
✔ Migrated 894 dashboards

Skipping alert rules migration

Removing service account token for service account <ID>

Best Regards,
Carlos