Plugins 〉Amazon Redshift

Grafana Labs

Sign up to receive occasional product news and updates:

Data Source

Amazon Redshift

  • Overview
  • Installation
  • Change log
  • Related content

Grafana 10 breaking change: update Redshift datasource plugin to >=1.8.3

Grafana 10.0.0 was shipped with the new React 18 upgrade. Changes in batching of state updates in React 18 cause a bug in the query editor in Redshift versions <=1.8.2 If you’re using Grafana@>=10.0.0, please update your plugin to version 1.8.3 or higher in your Grafana instance management console.

Redshift data source for Grafana

The Redshift data source plugin allows you to query and visualize Redshift data metrics from within Grafana.

This topic explains options, variables, querying, and other options specific to this data source. Refer to Add a data source for instructions on how to add a data source to Grafana.

Configure the data source in Grafana

To access data source settings, hover your mouse over the Configuration (gear) icon, then click Data Sources, and then click the Amazon Redshift data source.

NameThe data source name. This is how you refer to the data source in panels and queries.
DefaultDefault data source means that it will be pre-selected for new panels.
Authentication ProviderSpecify the provider to get credentials.
Access Key IDIf Access & secret key is selected, specify the Access Key of the security credentials to use.
Secret Access KeyIf Access & secret key is selected, specify the Secret Key of the security credentials to use.
Credentials Profile NameSpecify the name of the profile to use (if you use ~/.aws/credentials file), leave blank for default.
Assume Role Arn (optional)Specify the ARN of the role to assume.
External ID (optional)If you are assuming a role in another account, that has been created with an external ID, specify the external ID here.
Endpoint (optional)Optionally, specify a custom endpoint for the service.
Default RegionRegion in which the cluster is deployed.
AWS Secrets ManagerTo authenticate with Amazon Redshift using AWS Secrets Manager.
Temporary credentialsTo authenticate with Amazon Redshift using temporary database credentials.
ServerlessTo use a Redshift Serverless workgroup.
Cluster IdentifierRedshift Provisioned Cluster to use (automatically set if using AWS Secrets Manager).
WorkgroupRedshift Serverless Workgroup to use.
Managed SecretWhen using AWS Secrets Manager, select the secret containing the credentials to access the database. Note that Provisioned and Serverless stores credentials in a different format. Refer to Storing database credentials in AWS Secrets Manager for instructions.
Database UserUser of the database. Automatically set if using AWS Secrets Manager.
DatabaseName of the database within the cluster or workgroup.
Send events to Amazon EventBridgeTo send Data API events to Amazon EventBridge for monitoring purpose.


For authentication options and configuration details, see AWS authentication topic.

IAM policies

Grafana needs permissions granted via IAM to be able to read Redshift metrics. You can attach these permissions to IAM roles and utilize Grafana's built-in support for assuming roles. Note that you will need to configure the required policy before adding the data source to Grafana. You can check some predefined policies by AWS here.

Here is a minimal policy example:

  "Version": "2012-10-17",
  "Statement": [
      "Sid": "AllowReadingMetricsFromRedshift",
      "Effect": "Allow",
      "Action": [
      "Resource": "*"
      "Sid": "AllowReadingRedshiftQuerySecrets",
      "Effect": "Allow",
      "Action": ["secretsmanager:GetSecretValue"],
      "Resource": "*",
      "Condition": {
        "Null": {
          "secretsmanager:ResourceTag/RedshiftQueryOwner": "false"

Query Redshift data

The provided query editor is a standard SQL query editor. Grafana includes some macros to help with writing more complex timeseries queries.


MacroDescriptionOutput example
$__timeEpoch(column)$__timeEpoch will be replaced by an expression to convert to a UNIX timestamp and rename the column to timeUNIX_TIMESTAMP(dateColumn) as "time"
$__timeFilter(column)$__timeFilter creates a conditional that filters the data (using column) based on the time range of the paneltime BETWEEN '2017-07-18T11:15:52Z' AND '2017-07-18T11:15:52Z'
$__timeFrom()$__timeFrom outputs the current starting time of the range of the panel with quotes'2017-07-18T11:15:52Z'
$__timeTo()$__timeTo outputs the current ending time of the range of the panel with quotes'2017-07-18T11:15:52Z'
$__timeGroup(column, '1m')$__timeGroup groups timestamps so that there is only 1 point for every period on the graphfloor(extract(epoch from time)/60)*60 AS "time"
$__schema$__schema uses the selected schemapublic
$__table$__table outputs a table from the given $__schema (it uses the public schema by default)sales
$__column$__column outputs a column from the current $__tabledate
$__unixEpochFilter(column)$__unixEpochFilter be replaced by a time range filter using the specified column name with times represented as Unix timestampcolumn >= 1624406400 AND column <= 1624410000
$__unixEpochGroup(column)$__unixEpochGroup is the same as $__timeGroup but for times stored as Unix timestampfloor(time/60)*60 AS "time"

Table Visualization

Most queries in Redshift will be best represented by a table visualization. Any query will display data in a table. If it can be queried, then it can be put in a table.

This example returns results for a table visualization:

SELECT {column_1}, {column_2} FROM {table};

Timeseries / Graph visualizations

For timeseries / graph visualizations, there are a few requirements:

  • A column with a date or datetime type must be selected
  • The date column must be in ascending order (using ORDER BY column ASC)
  • A numeric column must also be selected

To make a more reasonable graph, be sure to use the $__timeFilter and $__timeGroup macros.

Example timeseries query:

  avg(execution_time) AS average_execution_time,
  $__timeGroup(start_time, 'hour'),
group by
order by
  start_time,query_type ASC;
Fill value

When data frames are formatted as time series, you can choose how missing values should be filled. This in turn affects how they are rendered: with connected or disconnected values. To configure this value, change the "Fill Value" in the query editor.

Inspecting the query

Because Grafana supports macros that Redshift does not, the fully rendered query, which can be copy/pasted directly into Redshift, is visible in the Query Inspector. To view the full interpolated query, click the Query Inspector button, and the full query will be visible under the "Query" tab.

Templates and variables

To add a new Redshift query variable, refer to Add a query variable. Use your Redshift data source as your data source for the following available queries:

Any value queried from a Redshift table can be used as a variable. Be sure to avoid selecting too many values, as this can cause performance issues.

To display a custom display name for a variable, you can use a query such as SELECT hostname AS text, id AS value FROM MyTable. In this case the variable value field must be a string type or cast to a string type.

After creating a variable, you can use it in your Redshift queries by using Variable syntax. For more information about variables, refer to Templates and variables.


Annotations allow you to overlay rich event information on top of graphs. You can add annotations by clicking on panels or by adding annotation queries via the Dashboard menu / Annotations view.

Example query to automatically add annotations:

  time as time,
  environment as tags,
  humidity as text
  $__timeFilter(time) and humidity > 95

The following table represents the values of the columns taken into account to render annotations:

timeThe name of the date/time field. Could be a column with a native SQL date/time data type or epoch value.
timeendOptional name of the end date/time field. Could be a column with a native SQL date/time data type or epoch value. (Grafana v6.6+)
textEvent description field.
tagsOptional field name to use for event tags as a comma separated string.

Provision Redshift data source

You can configure the Redshift data source using configuration files with Grafana's provisioning system. For more information, refer to the provisioning docs page.

Here are some provisioning examples.

Using AWS SDK (default)

apiVersion: 1
  - name: Redshift
    type: redshift
      authType: default
      defaultRegion: eu-west-2

Using credentials' profile name (non-default)

apiVersion: 1


  • name: Redshift type: redshift jsonData: authType: credentials defaultRegion: eu-west-2 profile: secondary

Using accessKey and secretKey

apiVersion: 1


  • name: Redshift type: grafana-redshift-datasource jsonData: authType: keys defaultRegion: eu-west-2 secureJsonData: accessKey: ‘<your access key>’ secretKey: ‘<your secret key>’

Using AWS SDK Default and ARN of IAM Role to Assume

apiVersion: 1
  - name: Redshift
    type: grafana-redshift-datasource
      authType: default
      assumeRoleArn: arn:aws:iam::123456789012:root
      defaultRegion: eu-west-2

Pre-configured Redshift dashboards

Redshift data source ships with a pre-configured dashboard for some advanced monitoring parameters. This curated dashboard is based on similar dashboards in the AWS Labs repository for Redshift. Check it out for more details.

Follow these instructions for importing a dashboard in Grafana.

Imported dashboards can be found in Configuration > Data Sources > select your Redshift data source > select the Dashboards tab to see available pre-made dashboards.

Get the most out of the plugin

Async Query Data Support

Async Query Data support enables an asynchronous query handling flow. With Async Query Data support enabled, queries will be handled over multiple requests (starting, checking its status, and fetching the results) instead of having a query be started and resolved over a single request. This is useful for queries that can potentially run for a long time and timeout. You'll need to ensure the IAM policy used by Grafana allows the following actions redshift-data:ListStatements and redshift-data:CancelStatement.

Async query data support is enabled by default in all Redshift datasources.

Async Query Caching

To enable query caching for async queries, you need to be on Grafana version 10.1 or above, and to set the feature toggles useCachingService and awsAsyncQueryCaching to true. You'll also need to configure query caching for the specific Redshift datasource.

Installing Amazon Redshift on Grafana Cloud:

For more information, visit the docs on plugin installation.



  • Migrate to new form styling in config and query editors in #287


  • Fix: use ReadAuthSettings to get authSettings in #288


  • Upgrade grafana-aws-sdk to replace GetSession usages with GetSessionWithAuthSettings #284


  • Add keywords by @kevinwcyu in
  • Add missing regions and use the region resource handler in the frontend by @iwysiu in
  • Plugin.json: update schema reference URL by @leventebalogh in
  • Fix E2E: Update region before sending the /secrets resource request by @idastambuk in
  • Update for added context in grafana-aws-sdk by @njvrzm in

New Contributors

  • @leventebalogh made their first contribution in
  • @njvrzm made their first contribution in


  • Remove the redshiftAsyncQuerySupport feature toggle + styling improvements in


  • Upgrade @grafana/async-query-data from 0.1.10 to 0.1.11


  • Update grafana/aws-sdk-go to 0.20.0


  • Bump from 0.37.0 to 0.44.0 by @dependabot in
  • Upgrade grafana-plugin-sdk-go; add underscore, debug to package resolutions by @fridgepoet in

Full Changelog:


  • Migrate Query and config editors to new form styling under feature toggle #255
  • Support Node 18 #249
  • Fix datasource type in provisioning docs in #246


  • Fix async queries by not calling ListStatements in GetQueryID #252


  • upgrade @grafana/aws-sdk to fix a bug in temporary credentials


  • Update grafana-aws-sdk to v0.19.1 to add il-central-1 to opt-in region list


  • Upgrade @grafana/async-query-data to reduce minimum query time


  • Upgrade grafana/aws-sdk-react dependency #239
  • Fix connection error when changing access and secret key #235
  • Support async query caching #233


  • Add support for Redshift Serverless by @yota-p


  • Upgrade @grafana/aws-sdk to v0.0.47 to support numeric values when applying template variables to SQL queries
  • Fix async queries and expressions


  • Upgrade re: Grafana 10


  • Upgrade grafana/aws-sdk-react to 0.0.46


  • Update grafana-aws-sdk version to include new region in opt-in region list
  • Security: Upgrade Go in build process to 1.20.4
  • Update grafana-plugin-sdk-go version to 0.161.0 to avoid a potential http header problem.


  • Update async-query-data with a fix for errors in #220


  • Update backend dependencies


  • Fix converting rows with FLOAT, FLOAT4, and BOOLEAN by @iwysiu in #213
  • Add header component to Query Editor by @idastambuk in #214
  • Use organization ISSUE_COMMANDS_TOKEN with reduced scope by @iwysiu in #210


  • Remove run and cancel buttons in annotations editor in


  • Migrate to create-plugin by @iwysiu in
  • Update code coverage in workflow to latest by @idastambuk in
  • Update @grafana/aws-sdk by @kevinwcyu in
  • Update @grafana/ packages by @idastambuk in
  • Upgrade grafana-aws-sdk to v0.12.0 by @fridgepoet in


  • Hide the stop button when async query data support is not enabled


  • Add Async Query Data Support


  • Update @grafana dependencies to v8.5.10


  • Security: Upgrade Go in build process to 1.19.3


  • Security: Upgrade Go in build process to 1.19.2


  • Upgrade to grafana-aws-sdk v0.11.0 by @fridgepoet in


  • Add database security monitoring dashboards by @yota-p in


  • Add support for context aware autocompletion by @sunker in


  • Bug fix for auth issues with when using keys and dependency upgrades (
  • Updates to code coverage


What's Changed

  • Update grafana-aws-sdk by @andresmgot in
  • Autocomplete: Render SQL editor in case feature toggle is enabled by @sunker in
  • fix: WLM panels query fix by @vgkowski in
  • Custom redshift language by @sunker in
  • Align Monaco language with official language ref by @sunker in

Full Changelog:


  • Reduces backoff time factor to retrieve results.
  • Upgrades internal dependencies.


  • Add details in the datasource card #130
  • Enable WithEvent to send an event to the AWS EventBridge #132


Fixes bugs for Endpoint and Assume Role settings.


Fixes a bug preventing from getting null values in a query.


Fixes a bug preventing from creating several data sources of the plugin in the same instance.


Initial release.


Improved curated dashboard.


Allow to authenticate using AWS Secret Manager. More bug fixes.


Third preview release. Includes curated dashboard.


Second release.


Initial release.