Zappa deployment throwing 404 error
See original GitHub issueContext
I am using connexion for my Flask application. I am getting a 404 error \ while accessing teh endpoint. I have tried to dummy down the issue I am facing at https://github.com/ctippur/zappa-connexion-sample
I have had success deploying applications using connexion and zappa. I am trying to use newer versions of the libraries to deploy code. Looks like the app gets initialized but I get a 404 error on any endpoint. I am able to test locally without any issues. I also downloaded the lambda code and was able to run the application locally as well.
My python version is 3.6.3 Zappa version - 0.48.2
Expected Behavior
The ‘/’ endpoint should return the current time.
Actual Behavior
I get a 404 error.
Possible Fix
Steps to Reproduce
https://github.com/ctippur/zappa-connexion-sample/blob/master/README.md
Your Environment
- Zappa version used: 0.48.2
- Operating System and Python version: MacOS High Sierra 10.13.2
- The output of
pip freeze
:https://github.com/ctippur/zappa-connexion-sample/blob/master/requirements.txt - Link to your project (optional): https://github.com/ctippur/zappa-connexion-sample
- Your
zappa_settings.py
: https://github.com/ctippur/zappa-connexion-sample/blob/master/zappa_settings.json
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
Server error when trying to reach a domain [Zappa]
I deployed a website to AWS using Zappa (a few hours ago). I can access the API gateway url but when I try...
Read more >Using Zappa and AWS Lambda to deploy serverless Django ...
There is an SQLite version conflict that seems to throw an error when Zappa is being run. To avoid this, you may need...
Read more >Adding a 404 Not Found Page to your Static Site — Eleventy
A 404: Not Found page is a pretty standard thing on the web. ... throw new Error(`Expected a \`${NOT_FOUND_PATH}\` file but could not...
Read more >zappa - PyPI
Zappa makes it super easy to build and deploy server-less, event-driven Python applications (including, but not limited to, WSGI web apps) on AWS...
Read more >SQLite 3.8.3 or later is required (found 3.7.17)-django
When I deploy using Zappa I get this error: Error: Warning! Status check on the deployed lambda failed. A GET request to '/'...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi, it looks like you may have figured this out already. Based on this issue , try updating your zappa_settings.json line from
"app_function": "swagger_server.app.app"
to"app_function": "swagger_server.app"
Hi all, I faced the same issue and came here for the solution, and @michellecsw comment helped me a lot.
For any one who’s reading this comment, I believe in any case if you get Code: 404 for the API request you may find this issue here. This is actually not an issue in the zappa library. When we prepare the zappa settings file, we need to make sure Flask app is accessible from zappa framework. i.e. lambda handler in zappa only calls the method
app.run(port=PORT)
. Hence the prerequisites for creatingapp
object must be done.