1
votes

I recently added changes to my python lambda function and tried to redeploy to production using

sls deploy --stage prod

The endpoint appears and the deployment was successful. However, I noticed that the endpoint id changed.

example:
from : https://111222333444.execute-api.us-east-1.amazonaws.com/prod/forecast
to: https://333555777888.execute-api.us-east-1.amazonaws.com/prod/forecast

This is weird since I’ve already done multiple deployments using serverless framework and it never changed the endpoint id before. Another problem is I can’t use the new one created since it does not appear in API Gateway, CloudFormation and even in S3. However, in my serverless cli it said that it was successfully deployed under the same:
• service
• stage
• region
• stack
• resources

The only change I’ve done besides changing that one line of code was I deleted a cron event associated with this endpoint but I strongly feel it shouldn’t have affected this.

Any lead would surely be appreciated. Thank you so much!

P.S Im using the ff:
frameworkVersion: 2
runtime environment: python3.6

1

1 Answers

1
votes

Isn't it accidentally deployed to another AWS account?

You can check arn of resources in sls logs(add -v if you dont see logs in detail) and check if that lambda exists in proper account. Arn has aws account id which is really usable to track where you deployed.