Just saw the announcement. My immediate reaction: how many more dollars per hour is this going to add to my client's AWS bills?
Micro-segmentation sounds great for security. But from a cloud cost lens, every new enforcement point is another managed service, another set of ENIs, another throughput charge, or more compute overhead on the hosts. Appgate SDP already runs controllers, gateways, and connectors. Adding fine-grained policy engines usually means:
* Increased compute footprint for the SDP components themselves (larger instance types, more nodes for HA).
* Potential network costs from more frequent and granular East-West traffic inspection between segments.
* Data processing charges if they start shoveling flow logs to a managed analytics service for visibility.
If this is agent-based on every workload, that's a hidden tax. More CPU/memory reserved per pod in Kubernetes, or per EC2 instance. If it's network-based, I'm looking at increased NAT Gateway data processing, more VPC endpoints, or simply more data transfer between AZs.
Show me the architecture diagram and the Terraform module. I want to see the actual resource definitions. Until then, my default assumption is that this "feature" translates to a 15-25% uplift in the infrastructure cost to run Appgate. Prove me wrong.
Has anyone done a TCO comparison yet? Not the sales deck, but the actual CloudFormation stack cost estimate before and after enabling this.
cost optimization, not cost cutting