After a successful deploy, the CF script, Lambda functions, and API Gateway are not in the AWS console

After a successful deploy, the CF script, Lambda functions, and API Gateway are not in the AWS console. The only thing that was sent to AWS was the zip file to S3.

Why was nothing deployed?

As you can see, everything looks like it worked perfectly:

Serverless: Select: selecting functions for deployment
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...
Serverless: Uploading service .zip file to S3 (1.76 KB)...
Serverless: Validating template...
Serverless: Updating Stack...
Serverless: Checking Stack update progress...
CloudFormation - UPDATE_IN_PROGRESS - AWS::CloudFormation::Stack - ovation-nexus-sandbox
CloudFormation - UPDATE_IN_PROGRESS - AWS::Lambda::Function - SampleLambdaFunction
CloudFormation - UPDATE_COMPLETE - AWS::Lambda::Function - SampleLambdaFunction
CloudFormation - CREATE_IN_PROGRESS - AWS::ApiGateway::Deployment - ApiGatewayDeployment1535555356080
CloudFormation - CREATE_IN_PROGRESS - AWS::ApiGateway::Deployment - ApiGatewayDeployment1535555356080
CloudFormation - CREATE_COMPLETE - AWS::ApiGateway::Deployment - ApiGatewayDeployment1535555356080
CloudFormation - UPDATE_COMPLETE_CLEANUP_IN_PROGRESS - AWS::CloudFormation::Stack - ovation-nexus-sandbox
CloudFormation - DELETE_IN_PROGRESS - AWS::ApiGateway::Deployment - ApiGatewayDeployment1535555231495
CloudFormation - DELETE_COMPLETE - AWS::ApiGateway::Deployment - ApiGatewayDeployment1535555231495
CloudFormation - UPDATE_COMPLETE - AWS::CloudFormation::Stack - ovation-nexus-sandbox
Serverless: Stack update finished...
Service Information
service: ovation-nexus
stage: sandbox
region: us-east-1
stack: ovation-nexus-sandbox
api keys:
  None
endpoints:
  GET - https://hc91kx80wa.execute-api.us-east-1.amazonaws.com/sandbox/sample
functions:
  sample: ovation-nexus-sandbox-sample

But I’m not seeing anything in the AWS console.

sls -v
1.30.3
  1. Check the region you deployed to is the same region you’re using in the AWS console.
  2. Check the account you’re using for deployment is the same one you logged into the console with.

It’s almost certainly going to be one of those two things.

@buggy you’re a genius. Just had to switch my region…