01 / Deliver
Access your customer-specific deployment package and guided CloudShell installation scripts.
MODEL 02 / CUSTOMER-HOSTED
Your AWS account.
Your dedicated appliance.
Deploy ESBA in dedicated, hardened EC2 infrastructure that you own and select, then configure protection for the traffic flowing through each deployed location.
DEPLOYMENT ON YOUR TERMS
A guided path from discovery to protected traffic.
A customer-specific delivery package and installation scripts guide your IT professional through provisioning, activation and staged cutover in a supported AWS environment.
02 / Install
Provision a dedicated EC2 appliance in your AWS account, with isolated management and selected protected networks.
03 / Cut over
Begin with monitor-only verification where the deployment workflow requires it; route selected traffic through the appliance when ready to enable enforcement.
PLACE IT WHERE THE RISK IS
Protect distinct areas of your infrastructure.
Multiple appliances can be deployed across supported traffic paths, each with its own configured protected networks and security policies.
In front of protected resources
Use supported AWS traffic steering to inspect connections to the systems that matter.
At traffic aggregation points
Design protection alongside load-balancer and application access boundaries.
Between connected environments
Apply policies where traffic crosses VPC or data-center paths, subject to supported routing and integration constraints.
CUSTOMER PORTAL / LICENSING / UPDATES
You choose when to update.
Use the ESBA Customer Portal to manage activation, obtain deployment/update packages, view the current release, and approve a software update and cutover at a time you select. New features are included according to the active software license terms and entitlement.
Explore the management experience ↗