Check if the cluster is accessible on the Properties
page under Network and security settings
Chose Publicly accessible
YES (radio button) when creating the cluster. If this is set to NO then users can only access the cluster from inside the VPC.
This can be changed in the console by navigating to the cluster, clicking the Cluster ˅
button, clicking Modify
. Then change the Publicly accessible
selection and click the blue Modify
It may take a minute or so for the change to take effect.
Check which rules are attached to the security groups in 'Cluster security groups' and also in the Network and Security settings.To enable access to an Amazon Redshift cluster in a VPC
To enable access to an Amazon Redshift cluster that is not in a VPC
- Get the hostname and/or IP address from the FglAM of the agent that cannot connect.
- Sign in to the AWS Console.
- Go into the EC2 Management Console.
- On the left navigation pane, look for the Network & Security header and click Security Groups.
- Click the row with Default in the Group Name's column.
- Select the Inbound tab, then click Edit.
- Add Rule: Type=Redshift, Source=MyIP. (auto-fill)
- Save it.
- On the Redshift dashboard, on the left panel, click on "Security".
- Go to "Security Groups" tab.
- Click on "default" on the list.
- Click "Add Connection Type".
- On the modal, choose "CIDR/IP" on the "Connection Type".
- Your IP address would be automatically populated on the input field.
- Click "Authorize".
After making the changes, use the telnet command to verify whether the connection from the FglAM server to Redshift is successful or not. If the problem persists, contact AWS Redshift support to check if there's an issue on their end.
Ask the network administrators to allow traffic between the FglAM and Redshift.