Help with some tutorial or blogs for setting up Warp with AWS redshift?
Hi all, has anyone come across any good blogs or documentation that can be used to replace Pritunl VPN with Warp?
As an example: if one of my teams is using the VPN to connect and do something on AWS Redshift. How would I go about configuring this with Warp. Any articles of similar instances would be amazing.
I’m just getting started off with Zero Trust so my apologies if this is something super basic that I’m not able to figure out.🙇♂️
Sorry if this is the wrong place to ask. Just trying to get this sorted. 🙆♂️
6 Replies
Can you go into a bit more detail about what problem you're trying to solve? I'm not familiar with how Redshift works. When you say "do something", do you mean access to a webinterface?
Sorry should have been more specific.
The redshift instance has its own VPC on AWS and I’ve created a EC2 instance in that VPC to which I’ve deployed CloudflareD. I’ve then mentioned the route in the routes tab and set a specific virtual network to be assigned to the tunnel. What I’m stuck on is that since Redshift uses port 5439 to connect - how would I set up an Access application for it? I want my team to basically connect to this Warp virtual network and be able to access applications running in that VPC. I’ve done this for a server that hosts a website and it’s SSH but Redshift running internally without public access on port 5439 is where I’m currently stuck.
Would you know which Access application I should use for this or if they’re even required at all?
Update: I’ve created a dedicated virtual network for Redshift team and created a EC2 instance in the same VPC as Redshift after which I configured the private IP and routes in the tunnel. This worked with me being able to reach the redshift instance through Warp.
Given the current set up do you think an Access application of any sort is required to improve on this? I’ve also created a network policy to only allow specific users access to their virtual network since there isn’t a way of hiding the network from being visible. (Unless there is an option to hide the virtual network from everyone except specific users? ) 🤔
You need Access if you want to control who has access to your private network. If everyone in your organization is allowed, you don't need Access.
Ah well we do want only specific teams to have access to it. I assumed if I created separate virtual network for the team and set it up with a network policy to only allow specific teams access to the virtual network it would help. Any clues on which Access category this would go under?
That sounds like it would work, though you don't have a lot of granularity that way. Access also provides you with additional authentication methods, but if you don't need that, it doesn't really matter.
Gotcha - appreciate the help and advice. I’ll look into it further and see what else I could get set up for it. 🙌