\n
Here are the current Network Security settings of the cluster. The only thing I have changed is that I have made it Publicly accessible (the value changed from No to Yes). But I haven't changed anything in VPC and VPC security group. As far as I see, all Inbound and Outbound traffic is allowed.
\n\nAnything I might have missed?\nShould I add a firewall rule to my local machine for this port as well?
\nUPDATE:
\nInbound rules for the VPC Group\n
Outbound rules for the VPC Group\n
If you check your security group (SG), you can notice that the source
in the inbound
rule is sg-9054xxxx
. This means that all internet traffic is blocked.\nYou can only connect to your redshift from EC2 instance having same SG.
Alternatively, you can modify the source
of the inbound
rule in the SG to be your home/work ip address/range, or any IP address (not recommended).
Other option is to setup a bastion instance in a public subnet with ssh connectivity. Then you can setup ssh tunnel
between between your windows and redshift using the bastion. Similar for VPN connection.
To query redshift you may also use its data api. This does not require establishing a regular connection to the cluster.
\n","author":{"@type":"Person","name":"Marcin"},"upvoteCount":1}}}Reputation: 7278
I have installed the 64x Amazon Redshift ODBC driver on my Windows 10 and it shows up under System DSN tab of ODBC Data Source Administrator (64-bit). I click on Configure and as I enter the connection information from my Amazon Redshift cluster properties, I face the following error:
Here are the current Network Security settings of the cluster. The only thing I have changed is that I have made it Publicly accessible (the value changed from No to Yes). But I haven't changed anything in VPC and VPC security group. As far as I see, all Inbound and Outbound traffic is allowed.
Anything I might have missed? Should I add a firewall rule to my local machine for this port as well?
UPDATE:
Inbound rules for the VPC Group
Outbound rules for the VPC Group
Upvotes: 1
Views: 4632
Reputation: 238937
If you check your security group (SG), you can notice that the source
in the inbound
rule is sg-9054xxxx
. This means that all internet traffic is blocked.
You can only connect to your redshift from EC2 instance having same SG.
Alternatively, you can modify the source
of the inbound
rule in the SG to be your home/work ip address/range, or any IP address (not recommended).
Other option is to setup a bastion instance in a public subnet with ssh connectivity. Then you can setup ssh tunnel
between between your windows and redshift using the bastion. Similar for VPN connection.
To query redshift you may also use its data api. This does not require establishing a regular connection to the cluster.
Upvotes: 1