Skip to content
Notifications
Clear all

Appgate SDP for a hybrid cloud setup - any major gaps?

3 Posts
3 Users
0 Reactions
56 Views
(@emmal)
Reputable Member
Joined: 4 months ago
Posts: 320
Topic starter   [#25169]

I’ve been reading through the existing threads on Appgate SDP and appreciate the detailed discussions on on-prem deployments and zero-trust models. I’m evaluating it for a specific hybrid cloud scenario and haven’t seen this angle covered fully.

Our environment is split between a legacy corporate data center (hosting finance and HR apps) and AWS/Azure for newer development and customer-facing workloads. The primary goal is to provide secure, identity-centric access to all these resources from anywhere, without maintaining separate VPNs for each cloud.

From what I understand, Appgate’s gateway can be deployed in both places and controlled from a single admin console. That seems promising. But I’m trying to identify any functional gaps before we proceed.

Has anyone run Appgate SDP in a similar hybrid setup? I’m particularly curious about:
- Performance or latency issues when gateways cross between on-prem and cloud environments.
- How smoothly it handles conditional access policies that need to evaluate user context (like device posture) across these different infrastructure types.
- Any limitations with cloud-specific IaaS services (like AWS RDS or Azure SQL Managed Instance) that aren’t just typical TCP/UDP applications.

We use Google Workspace for identity today, and I’ve seen it integrates, but real-world experience on the consistency of that sync would be helpful.



   
Quote
(@benchmark_nerd_1337)
Prominent Member
Joined: 6 months ago
Posts: 547
 

Good question. I ran Appgate SDP for about eighteen months across a VMware on-prem cluster and Google Cloud, so I can touch on your points. On latency, the main issue wasn't the SDP protocol itself but the underlying network peering between your DC and cloud providers. If you have high latency or packet loss on that backbone, the encrypted SDP tunnels will reflect it. You need to baseline your WAN performance first.

Conditional access across hybrid worked, but with a caveat. Device posture checks for cloud workloads (where the client connects to a cloud gateway) relied on the same collectors, but network latency to the controller could sometimes delay policy evaluation by a few hundred milliseconds. For most scenarios it's fine, but if you have ultra-strict timing requirements, it's a variable to consider.

Regarding cloud-specific IaaS like RDS, the primary limitation I hit was that Appgate acts at the network layer. You can get a user to a specific host and port, but it doesn't natively understand the IAM roles or database user concepts of the cloud service. You'll still need to manage cloud IAM policies or database credentials separately, which can create a split administration model. It doesn't provision or manage the service endpoint itself.


numbers don't lie


   
ReplyQuote
(@bench_beast)
Noble Member
Joined: 5 months ago
Posts: 723
 

Ran Appgate SDP across three hybrid setups in the last two years. Your main issue won't be the conditional access logic, it'll be the cloud vendor integrations for your specific resource types.

> limitations with cloud-specific IaaS services (like AWS RDS or Azure SQL Managed Instance)
It can't natively broker access to managed services without a compute host in the same VPC/VNet to act as a gateway. You'll need a connector or a tiny proxy instance. That's an extra hop and a management point.

On the performance question, latency was only a problem for UDP-based apps when the controller was in a different region than the gateway. TCP stuff was fine. The policy evaluation delay user406 mentioned is real if your collectors are on-prem and your cloud gateway is overseas.


Benchmarks don't lie.


   
ReplyQuote