Blogs

AWS Fargate Security with Sidecars - Aquasec

Aquasec

How to protect workloads on AWS Fargate by running Aqua MicroEnforcer as a sidecar container, so that the image doesn’t need to be modified.

Visit Site

Embracing the Future: AWS Customers Leverage Fargate for ECS and EKS DeploymentsAquasec Cloud Workload Security: Aqua Shines in GigaOm's Radar ReportAquasec Aqua and HashiCorp Enable Cloud Native Security, Zero-Trust ApproachesAquasec TrailShark: Understanding AWS API and Service InteractionsAquasec Cloud VM Security with Aqua CSPAquasec Empowering Security: Bridging Talk to Action at RSA 2024Aquasec Cloud Security Trends & Challenges: Complete GuideCybersecurity Exchange Security Implementation for Responsible AI: A Practical FrameworkCybersecurity Exchange Re: April 23rd AWS EU-WEST-1 Service InterruptionRedis How to Conduct an AI Agent Security Audit [+ Checklist]Zapier Grafana Is Not Worried About AWS CommercializationThenewstack DevSecOps: Why Security Shouldn’t be Sacrificed for SpeedThenewstack Security Considerations for API-Driven Apps Deployed to CloudThenewstack Oso Unbundles Security AuthorizationThenewstack Cloud Systems: Deploying to Amazon ECSPulumi Pulumi ESC and External Secrets Operator: The Perfect Solution for TodayPulumi AWS Enterprise Container Management with PulumiPulumi IaC Best Practices: Implementing RBAC and SecurityPulumi Neo Integrations: MCP Servers and Cloud CLIsPulumi Sidecars: A low-latency trust boundary for SandboxesModal