View a markdown version of this page

Set the application name connection property - Amazon Redshift

Amazon Redshift will no longer support the use of Python UDFs after June 30, 2026. We will start enforcing it in phases. For more information on the details of Python end of life and migration options, see the blog post that was published on June 30, 2025.

Set the application name connection property

When you connect to Amazon Redshift, set the optional application name driver property. This property identifies which application or tool established each connection, which makes it easier to monitor, audit, and troubleshoot your Amazon Redshift environment.

The application name that you provide appears in the application_name column of SYS_CONNECTION_LOG. You can use it to do the following:

  • Track connection sources. Identify which applications, services, or tools connect to your cluster.

  • Troubleshoot performance. Correlate queries with the originating application to isolate performance issues.

  • Audit access. Understand application-level usage patterns across your data warehouse.

The following table shows how to set the application name for each Amazon Redshift driver.

Driver Property Example
JDBC ApplicationName jdbc:redshift://endpoint:port/database?ApplicationName=my-etl-pipeline
ODBC ApplicationName Set ApplicationName=my-bi-tool in the DSN or connection string.
Python application_name redshift_connector.connect(..., application_name='my-data-catalog')

For more information about the application name property for each driver, see the following:

Note

Use a descriptive, consistent naming convention for application names, such as team-service-environment (for example, quicksight-analytics-dashboard-prod). This approach makes it easier to filter and analyze SYS_CONNECTION_LOG data.