# Deploy not re-creating ENI's when in a VPC

**URL:** <https://forum.serverless.com/t/deploy-not-re-creating-enis-when-in-a-vpc/7518>\
**Category:** Serverless Framework\
**Created:** [February 27, 2019, 3:24am UTC](https://forum.serverless.com/t/deploy-not-re-creating-enis-when-in-a-vpc/7518 "2019-02-27T03:24:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dms](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@dms](https://forum.serverless.com/u/dms)\
**Post date:** [February 27, 2019, 3:24am UTC](https://forum.serverless.com/t/deploy-not-re-creating-enis-when-in-a-vpc/7518/1 "2019-02-27T03:24:15Z")

</div>

Hello,

I have my lambda’s in a VPC and originally this created ENI’s (I think). I manually deleted them as CloudFormation was taking a long time to detach them (this is in dev), however when I did `sls deploy` again, it did not re-establish ENI’s. Everything deployed fine, just no ENI’s attached to any of the lambdas.

Any ideas on why this could be or if there’s a different method to re-establish them?

This is my config, minus function details.

```
provider:
  name: aws
  runtime: nodejs8.10
  timeout: 6
  stage: dev
  region: us-east-1
  excludeDevDependencies: true
  package:
exclude:
  - .gitignore
  - .git/**
  - test/**
  vpc:
securityGroupIds:
  - sg-0af1fa1fca5dcbbc6
subnetIds:
  - subnet-0379e30cee9iad8a0
  - subnet-0551484ca7364aedn
  iamRoleStatements:
- Effect: 'Allow'
  Action:
    - 'lambda:InvokeFunction'
  Resource: '*'
- Effect: 'Allow'
  Action:
    - 'cognito-identity:*'
    - 'cognito-idp:Admin*'
  Resource: '*'
  resources:
Resources:
  UploadBucket:
    Type: AWS::S3::Bucket
    Properties:
      BucketName: mtestbucket
      AccessControl: PublicRead
      CorsConfiguration:
        CorsRules:
          - AllowedMethods:
              - GET
              - PUT
              - POST
              - HEAD
            AllowedOrigins:
              - '*'
            AllowedHeaders:
              - '*'

```

Thank you