Connect Amazon ECS or Kubernetes clusters and create protection policies to start monitoring your container environment with Container Security.
The following table describes the platform support for different ECS and EKS deployments.
|
AWS ECS
|
AWS EKS
|
Azure
|
GCP
|
Self-managed | ||||
|
Fargate
|
EC2
|
Fargate
|
EC2
|
GKE (STD)
|
GKE (Autopilot)
|
OpenShift/Gardener
|
||
|
Admission controller
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
||
|
Runtime Security
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
Runtime Vulnerability Scanning
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
Runtime Malware Scanning
|
Y
|
Y
|
Y
|
Y
|
Y
|
|||
|
Drift detection
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
Continuous Container Configuration Protection
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
||
Get Container Security protection up and running quickly and start monitoring your
container
environment for vulnerabilities and policy violations in 5 easy steps.
-
Connect a cluster:
-
Deploy Container Security to one or more of your Kubernetes or Amazon ECS clusters.
-
Amazon ECS: Amazon ECS clusters or Amazon ECS Fargate clusters
-
Monitor policy violations and vulnerability detections
 |
NoteContainer Security supports asset configuration and management with Terraform. For
details,
see the Trend Vision One Terraform Provider.
|