# VPC issues with serverless container deploys

**URL:** <https://forum.serverless.com/t/vpc-issues-with-serverless-container-deploys/21026>\
**Category:** Serverless Framework\
**Created:** [February 27, 2025, 5:30pm UTC](https://forum.serverless.com/t/vpc-issues-with-serverless-container-deploys/21026 "2025-02-27T17:30:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtryearlybird](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@jtryearlybird](https://forum.serverless.com/u/jtryearlybird)\
**Post date:** [February 27, 2025, 5:30pm UTC](https://forum.serverless.com/t/vpc-issues-with-serverless-container-deploys/21026/1 "2025-02-27T17:30:37Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jtryearlybird](https://avatars.discourse-cdn.com/v4/letter/j/47e85d/32.png) [@jtryearlybird](https://forum.serverless.com/u/jtryearlybird)\
**Post date:** [May 15, 2025, 3:36am UTC](https://forum.serverless.com/t/vpc-issues-with-serverless-container-deploys/21026/2 "2025-05-15T03:36:02Z")

</div>

Bump does anyone know if its possible to specify cidr block for vpc?