Serverless deploy does not create API gateway

Question

Here is my serverless.yml file:

service: investor-bot


provider:
  name: aws
  runtime: python3.9
  stage: dev


functions:
  post:
    handler: handler.hello
    events:
      - http:
          path: ita-investor-bot
          method: get

Here is code (even with this code it does not work):

def hello(event, context):
    return {"statusCode": 200}

I exported my AWS credentials and ran serverless deploy:

Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Uploading CloudFormation file to S3...
Serverless: Uploading artifacts...
Serverless: Uploading service investor-bot.zip file to S3 (12.77 MB)...
Serverless: Validating template...
Serverless: Updating Stack...
Serverless: Checking Stack update progress...
.......................................
Serverless: Stack update finished...
Service Information
service: investor-bot
stage: dev
region: us-east-1
stack: investor-bot-dev
resources: 11
api keys:
  None
endpoints:
  GET - https://933zcto8tc.execute-api.us-east-1.amazonaws.com/dev/ita-investor-bot
functions:
  post: investor-bot-dev-post
layers:
  None
Serverless: Removing old service artifacts from S3...
Serverless: Deprecation warning: Resolution of lambda version hashes was improved with better algorithm, which will be used in next major release.
            Switch to it now by setting "provider.lambdaHashingVersion" to "20201221"
            More Info: https://www.serverless.com/framework/docs/deprecations/#LAMBDA_HASHING_VERSION_V2

Toggle on monitoring with the Serverless Dashboard: run "serverless"

I see nothing at the AWS account in API Gateway. I can not access endpoint:

There is an endpoint, it's just that the code therein is throwing an unhandled error, so API gateway returns 500; if there was no endpoint, it would 404. — Adam Smooch
– Adam Smooch, Commented Oct 28, 2021 at 16:18
To debug your code, look in the AWS console for he specific errors being thrown: console.aws.amazon.com/cloudwatch/home... or you can also tail the logs from your CLI: serverless logs -f <functionName> -t — Adam Smooch
– Adam Smooch, Commented Oct 28, 2021 at 16:19
Also, try including "body": "" in your return...? serverless.com/framework/docs/providers/aws/examples/… — Adam Smooch
– Adam Smooch, Commented Oct 28, 2021 at 16:22
@AdamSmooch No, there is nothing in logs and in cloudwatch. I mentioned, that at API Gateway page api does not appear, there is literally nothing. — peter ignatiev
– peter ignatiev, Commented Oct 28, 2021 at 17:07
and when you login here? aws.amazon.com/api-gateway. Post screenshots of Cloudwatch + API-gateway UIs — Adam Smooch
– Adam Smooch, Commented Oct 28, 2021 at 18:41

Aaron Stuyvenberg · Accepted Answer · 2021-10-29 13:46:25Z

1

There's definitely a deployed API Gateway. You've deployed your stack in us-east-1, my best guess is that you're using the AWS console in another region.

When logged in to the AWS console, use the region switcher on the top-right to switch to us-east-1, from there you should see your API Gateway, lambda function, and cloudwatch logs.

answered Oct 29, 2021 at 13:46

Aaron Stuyvenberg

3,7971 gold badge12 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Daniel Kats · Accepted Answer · 2023-10-24 16:32:26Z

0

If anyone is finding this question in 2023, I encountered this problem as well and found that the API gateway is not created if you only define the function (just define the handler). The API gateway will be created when you add the keys events -> http -> path + method to your function definition.

answered Oct 24, 2023 at 16:32

Daniel Kats

5,63415 gold badges75 silver badges113 bronze badges

Collectives™ on Stack Overflow

Serverless deploy does not create API gateway

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related