Redshift Serverless (IAM)
Last modified on April 17, 2025
Overview
A datasource consists of a database resource and the credentials used to access it. This guide describes how to add Redshift Serverless (IAM) as a datasource in the Admin UI.
Prerequisites
To add a datasource, make sure you have met the following prerequisites:
- Properly configure an account for your resource.
- The hostname or endpoint you enter for your resource must be accessible by at least one gateway or relay. To verify this, log in to the gateway or relay and use the
nc -zv <YOUR_HOSTNAME> <YOUR_PORT>Netcat command. For example, usenc -zv testdb-01.fancy.org 5432. If your gateway server can connect to this hostname, you can proceed.
-z flag to check for listeners without sending data and the -v flag to show verbose output. If you do not have Netcat, you can use a package manager such as APT (Advanced Package Tool) to install it. On Linux-based distributions, run apt-get install netcat.Add a Resource
To add your Redshift Serverless (IAM) resource to StrongDM, use the following steps.
- Log in to the StrongDM Admin UI.
- Go to Resources > Datasources.
- Click Add datasource.
- Select Redshift Serverless (IAM) as the Datasource Type and set other configuration properties for your new database resource.
- Complete all required fields.
- Click Create to save the resource.
- Click the resource name to view status, diagnostic information, and setting details.
Resource properties
Configuration properties are visible when you add a datasource or when you click to view its settings. The following table describes the settings available for Redshift Serverless (IAM).
| Property | Requirement | Description |
|---|---|---|
| Display Name | Required | Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >) |
| Datasource Type | Required | Select Redshift Serverless (IAM) |
| Proxy Cluster | Required | Defaults to “Use legacy routing”; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource |
| Hostname | Required | Hostname for your resource; must be accessible to a gateway or relay |
| Port | Required | Port to use when connecting to Redshift; default port value is 5439 |
| Bind Interface | Read only | IP address to which the port override of this resource is bound. The IP address value is automatically generated in the 127.0.0.1 to 127.255.255.254 IP address range after the resource is created. The default is 127.0.0.1. You can modify this value with your preferred bind interface value later under Settings > Port Overrides. |
| Port Override | Optional | Automatically generated with a value between 1024-59999 as long as that port is not used by another resource; preferred port can be modified later under Settings > Port Overrides |
| Database | Required | Name of the database you will be connecting to with this datasource |
| Restrict Database | Optional | When selected, limits all connections to the configured database |
| Region | Required | AWS region to connect to (for example, us-east-1) |
| Role Assumption ARN | Optional | Role ARN, such as arn:aws:iam::000000000000:role/RoleName, that allows users accessing this resource to assume a role using AWS AssumeRole functionality |
| Workgroup | Required | Workgroup name in the AWS Console (for example, redshift-workgroup) |
| Resource Tags | Optional | Resource tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev) |
Resource status
After a resource is created, the Admin UI displays that resource as unhealthy until the health checks run successfully. When the resource is ready, the Health icon indicates a positive, green status.
When the resource does not display a positive status, click the resource name to go to the Diagnostics tab and check for errors.