Documentation Grafana documentation Data sources Prometheus Configure AWS authentication (deprecated)

Migrate from Prometheus SigV4 to Amazon Managed Service for Prometheus

For background on this change, refer to Prometheus data source update: Redefining our big tent philosophy.

What changed in Grafana 13

In Grafana 13, the prometheusTypeMigration feature toggle is enabled by default and deprecated. This means:

• Prometheus data sources configured with SigV4 authentication are automatically migrated to the dedicated Amazon Managed Service for Prometheus plugin on Grafana startup.
• You no longer need to manually enable the feature toggle.
• Grafana Cloud users are migrated automatically with no action required.
• Dashboards, alerts, and queries continue to work after migration without changes.

Check migration status

To determine if your Prometheus data sources have been migrated:

1. Navigate to Connections > Data sources.
2. Select your Prometheus data source.
3. Look for a migration banner at the top of the configuration page.

The banner displays one of the following messages:

• “Migration Notice” — The data source has been migrated to the Amazon Managed Service for Prometheus plugin.
• “Deprecation Notice” — The data source hasn’t been migrated yet.
• No banner — No migration is needed (the data source doesn’t use SigV4).

Configure the Amazon Managed Service for Prometheus data source

After migration (or for new setups), configure the dedicated plugin:

1. Navigate to Connections > Data sources.
2. Select your Amazon Managed Service for Prometheus data source.
3. In the Auth section, configure SigV4 authentication:

4. Set the HTTP URL to your Amazon Managed Service for Prometheus workspace endpoint: https://aps-workspaces.us-west-2.amazonaws.com/workspaces/ws-12345678-1234-1234-1234-123456789012/

5. Click Save & test to verify the connection.

Provision the data source

YAML Copy

apiVersion: 1
datasources:
  - name: Amazon Managed Prometheus
    type: grafana-amazonprometheus-datasource
    url: https://aps-workspaces.us-west-2.amazonaws.com/workspaces/ws-12345678-1234-1234-1234-123456789012/
    jsonData:
      httpMethod: POST
      sigV4Auth: true
      sigV4AuthType: keys
      sigV4Region: us-east-2
    secureJsonData:
      sigV4AccessKey: <ACCESS_KEY>
      sigV4SecretKey: <SECRET_KEY>

Replace <ACCESS_KEY> and <SECRET_KEY> with your AWS credentials.

Troubleshoot migration issues

Amazon Managed Service for Prometheus plugin not installed

Symptom: Migration doesn’t occur or the data source type is missing.

Solution:

1. Navigate to Connections > Add new connection and search for “Amazon Managed Service for Prometheus”.
2. Install the plugin if it isn’t already installed.
3. For air-gapped environments, download the plugin from the Grafana plugin catalog and install it manually.

“401 Unauthorized” after migration

Symptom: The migrated data source returns authentication errors.

Solution:

1. Self-hosted Grafana: Verify that grafana-amazonprometheus-datasource is included in forward_settings_to_plugins under the [aws] heading in your .ini configuration file.
2. Grafana Cloud: Contact Grafana Support.

Rollback the migration

If you need to revert migrated data sources back to the core Prometheus type:

1. Set prometheusTypeMigration to false in your Grafana configuration feature toggles. For more information, refer to Manage feature toggles.
2. Restart Grafana.
3. Obtain a bearer token with read and write permissions for the data source API. For more information, refer to Data source API.
4. Run the following rollback script, providing your Grafana URL and bearer token:

sh Copy

#!/bin/bash

GRAFANA_URL=""
BEARER_TOKEN=""
LOG_FILE="grafana_migration_rollback_$(date +%Y%m%d_%H%M%S).log"

log_message() {
    local message="$1"
    local timestamp=$(date '+%Y-%m-%d %H:%M:%S')
    echo "[$timestamp] $message" | tee -a "$LOG_FILE"
}

update_data_source() {
    local uid="$1"
    local data="$2"

    response=$(curl -s -w "\n%{http_code}" -X PUT \
        -H "Content-Type: application/json" \
        -H "Authorization: Bearer $BEARER_TOKEN" \
        -d "$data" \
        "$GRAFANA_URL/api/datasources/uid/$uid")

    http_code=$(echo "$response" | tail -n1)
    response_body=$(echo "$response" | sed '$d')

    if [[ "$http_code" -ge 200 && "$http_code" -lt 300 ]]; then
        log_message "$uid reverted successfully"
    else
        log_message "$uid error: HTTP $http_code - $response_body"
    fi
}

if ! command -v jq &> /dev/null; then
    echo "Error: jq is required but not installed."
    exit 1
fi

if [[ -z "$GRAFANA_URL" || -z "$BEARER_TOKEN" ]]; then
    echo "Error: Set GRAFANA_URL and BEARER_TOKEN variables at the top of the script."
    exit 1
fi

log_message "Starting AMP to Prometheus rollback"

response=$(curl -s -w "\n%{http_code}" -X GET \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer $BEARER_TOKEN" \
    "$GRAFANA_URL/api/datasources/")

http_code=$(echo "$response" | tail -n1)
response_body=$(echo "$response" | sed '$d')

if [[ "$http_code" -lt 200 || "$http_code" -ge 300 ]]; then
    log_message "Error fetching data sources: HTTP $http_code"
    exit 1
fi

total=$(echo "$response_body" | jq '[.[] | select(.jsonData["prometheus-type-migration"] == true and .type == "grafana-amazonprometheus-datasource")] | length')
log_message "Found $total data sources to revert"

echo "$response_body" | jq -c '.[] | select(.jsonData["prometheus-type-migration"] == true and .type == "grafana-amazonprometheus-datasource")' | while read -r data; do
    uid=$(echo "$data" | jq -r '.uid')
    read_only=$(echo "$data" | jq -r '.readOnly // false')

    if [[ "$read_only" == "true" ]]; then
        log_message "$uid is readOnly — edit the type to 'prometheus' in the provisioning file instead."
        continue
    fi

    updated_data=$(echo "$data" | jq '.type = "prometheus" | .jsonData["prometheus-type-migration"] = false')
    update_data_source "$uid" "$updated_data"
done

log_message "Rollback complete. Log: $LOG_FILE"

If you continue to experience issues, check the Grafana server logs for detailed error messages and contact Grafana Support.