# Changing vpc settings for container deploys / fargate **URL:** \ **Category:** Serverless Framework\ **Tags:** fargate\ **Created:** [May 22, 2025, 7:50pm UTC](https://forum.serverless.com/t/changing-vpc-settings-for-container-deploys-fargate/21211 "2025-05-22T19:50:35Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jtryearlybird](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@jtryearlybird](https://forum.serverless.com/u/jtryearlybird)\ **Post date:** [May 22, 2025, 7:50pm UTC](https://forum.serverless.com/t/changing-vpc-settings-for-container-deploys-fargate/21211/1 "2025-05-22T19:50:35Z")
When deploying to containers (fargate) with serverless, by default the serverless framework deploys a new vpc with cidr block 10.0.0.0/16. Is it possible to specify a different cidr block? I also notice deploying a different stage will not work. In addition “serverless remove --force” does not clean up the vpc that is created. ---
**Author:** ![beenmeckel](https://avatars.discourse-cdn.com/v4/letter/b/8dc957/32.png) [@beenmeckel](https://forum.serverless.com/u/beenmeckel)\ **Post date:** [August 8, 2025, 9:15pm UTC](https://forum.serverless.com/t/changing-vpc-settings-for-container-deploys-fargate/21211/2 "2025-08-08T21:15:35Z")
Consider using fck-nat to use a cheaper EC2 instance compared to the expensive and more reliable VPC NAT. [192.168.100.1](https://1921681001.id/) [192.168.1.1](https://19216811.cam/)