# When does Serverless create a new AWS API Gateway vs overwrite an old one?

**URL:** <https://forum.serverless.com/t/when-does-serverless-create-a-new-aws-api-gateway-vs-overwrite-an-old-one/7893>\
**Category:** Serverless Framework\
**Tags:** aws, api-gateway\
**Created:** [April 4, 2019, 8:07am UTC](https://forum.serverless.com/t/when-does-serverless-create-a-new-aws-api-gateway-vs-overwrite-an-old-one/7893 "2019-04-04T08:07:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![karlthen](https://avatars.discourse-cdn.com/v4/letter/k/cdc98d/32.png) [@karlthen](https://forum.serverless.com/u/karlthen)\
**Post date:** [April 4, 2019, 8:07am UTC](https://forum.serverless.com/t/when-does-serverless-create-a-new-aws-api-gateway-vs-overwrite-an-old-one/7893/1 "2019-04-04T08:07:21Z")

</div>

Hi  
After deploying I’ve noticed that a certain times Serverless overwrites my old API Gateway with new values that I’ve specified in the serverless.yml file and at other times it simply creates a new one, leaving the old behind but stripped of all resources (endpoints for example).

My question is, what could be the cause of this?