If you’re interested in enabling any of these advanced settings, please contact support via the chat widget to discuss your requirements.
- AWS
- GCP
Compliance
ECR Scanning
Enable Amazon ECR image scanning to automatically scan container images for software vulnerabilities.AWS GuardDuty
AWS GuardDuty provides intelligent threat detection for your EKS cluster, monitoring for malicious activity and unauthorized behavior.KMS Encryption
Enable AWS Key Management Service (KMS) encryption for Kubernetes secrets stored in etcd.AWS CloudWatch Logging
Configure which EKS cluster control plane log types are sent to AWS CloudWatch. These logs help with debugging, auditing, and monitoring your cluster’s control plane components.CloudWatch Observability Agent
You may also enable the CloudWatch Observability agent as an EKS add-on for enhanced cluster monitoring.Load Balancer
Configure the type of load balancer used for your cluster’s ingress.Control Plane Access
Private Cluster
When Private cluster is enabled, Porter provisions the EKS cluster with both public and private API server endpoint access, and restricts the public endpoint to an IP allowlist containing Porter’s control-plane IPs plus any customer CIDRs you add. This configuration is SOC2 / HIPAA compliant.Porter intentionally does not enable EKS “private-only” endpoint mode. Private-only forces every control-plane call — including Porter’s — through a VPN or VPC-peered path, which adds operational complexity and has historically caused outages for customers. Public + private with a tight IP allowlist meets the same compliance requirements and is significantly more reliable.
porter kubectl and porter helm commands; it does not control how the EKS API server endpoint itself is exposed.
