# Serverless v3 - How to import existing AWS API Gateway with new version

**URL:** <https://forum.serverless.com/t/serverless-v3-how-to-import-existing-aws-api-gateway-with-new-version/16465>\
**Category:** Serverless Framework\
**Created:** [December 27, 2021, 8:36am UTC](https://forum.serverless.com/t/serverless-v3-how-to-import-existing-aws-api-gateway-with-new-version/16465 "2021-12-27T08:36:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrzonca](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@mrzonca](https://forum.serverless.com/u/mrzonca)\
**Post date:** [December 27, 2021, 8:36am UTC](https://forum.serverless.com/t/serverless-v3-how-to-import-existing-aws-api-gateway-with-new-version/16465/1 "2021-12-27T08:36:44Z")

</div>

Hi,

After migration to Framework Core: 3.0.0-pre there is a deprecation:  
`When an external API Gateway is used and imported via provider.apiGateway.restApiId , both provider.logs.restApi and provider.tracing.apiGateway options are ignored.`

Even if I don’t have `provider.logs` or `provider.tracing` section, still getting error during deployment:  
`When external API Gateway resource is imported via "provider.apiGateway.restApiId", property "provider.tracing.apiGateway" is ineffective.`  
How to handle above in serverless v3? Deployment is possible only when section provider.apiGateway was removed but I still need to import ApiGateway