A parks department runs an ECS container platform in a shared city VPC alongside other applications and needs controlled egress plus tightly scoped service-to-service connectivity. Which networking approach best fits this multi-app VPC?
Select an answer to reveal the explanation.
Short Explanation
Containers in a shared city VPC still need seat belts: private subnets, security groups between services, and intentional egress. Opening every port with public IPs is how a parks app becomes everyone else's problem. ECS lives in the VPC—use the VPC controls.
Full Explanation
ECS tasks participate in VPC networking via ENIs (awsvpc mode) or related patterns, so security groups, subnet placement, and routing still govern connectivity. In a shared municipal VPC, place tasks in private subnets, use security groups to limit service-to-service traffic, and constrain egress with NAT Gateway, VPC endpoints, or approved proxies. Public IPs with permissive rules and default allow-all groups increase lateral risk among co-resident city applications.