Thank you. You solved the problem! In going through my config file to get a minimal example I realized I was using the wrong profile setting. That would do it.

Thanks again and sorry for the noob error. 😦

I also faced the similar issue, and I was using a profile that is not my default aws profile.

Description

• What went wrong? serverless deploy --aws-profile assumed_role failed with an error, for a project using a pre-existing VPC.

• What did you expect should have happened? serverless deploy --aws-profile assumed_role should have completed without error.

• What was the config you used? My serverless.yml defines provider.vpc.securityGroupIds to a single security group, and provider.vpc.subnetIds to three security groups.

• What stacktrace or error message from your provider did you see?

Serverless: Packaging service… Serverless: Excluding development dependencies… Serverless: Injecting required Python packages to package… Serverless: Uploading CloudFormation file to S3… Serverless: Uploading artifacts… Serverless: Uploading service MossService.zip file to S3 (72.05 KB)… Serverless: Validating template… Serverless: Updating Stack… Serverless: Checking Stack update progress… … Serverless: Operation failed! Serverless: View the full error output:

Serverless Error ---------------------------------------

An error occurred: SchedulerLambdaFunction - Error occurred while DescribeSecurityGroups. > EC2 Error Code: InvalidGroup.NotFound. EC2 Error Message: The security group ‘sg-3cfe0674’ > does not exist (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 6741f2d1-5ca3-4eb0-8148-4db53275a43b).

Get Support -------------------------------------------- Docs: docs.serverless.com Bugs: github.com/serverless/serverless/issues Issues: forum.serverless.com

Your Environment Information --------------------------- Operating System: darwin Node Version: 12.10.0 Framework Version: 1.61.0 Plugin Version: 3.2.7 SDK Version: 2.2.1 Components Core Version: 1.1.2 Components CLI Version: 1.4.0

Additional Data

I have also tried these two commands to confirm both security group and subnets exist. aws ec2 describe-security-groups --group-ids <sg-id> --profile assumed_role aws ec2 describe-subnets --profile assumed_role --subnet-ids subnet-redacted subnet-redacted

• Serverless Framework Version you’re using:

Framework Core: 1.61.0
Plugin: 3.2.7
SDK: 2.2.1
Components Core: 1.1.2
Components CLI: 1.4.0

• Operating System: macOS Mojave 10.14.5
• Stack Trace: see above
• Provider Error messages: see above
• AWS configuration: I have made sure both ~/.aws/config and ~/.aws/credentials are set correctly with the profile name and credentials.

Ok - not sure if this related to what you said @jokeyrhyme but I’ve got it working now.

Serverless doesn’t seem to use my default region (where the VPC is) as listed in ~/.aws/config so was trying to deploy to the Serverless default region us-east-1.

Would be awesome if Serverless would honour this file or maybe make it mandatory to provide a region in your config? Just some ideas.