I start up my application and call a couple of API calls simultaneously to the backend.
The backend is already warm and thus is able to process the API calls immediately.
The application received the API responses in time and no 503 errors occurred.
Actual Behavior
I get a 503 timeout error in my application when I make the first API call.
When I try again then it works fine.
From the tail logs from zappa I assume that the keep_warm_callback had no effect on the application and did not keep the lambda warm.
These are the tial logs from zappa:
Context
Expected Behavior
I start up my application and call a couple of API calls simultaneously to the backend. The backend is already warm and thus is able to process the API calls immediately. The application received the API responses in time and no 503 errors occurred.
Actual Behavior
I get a 503 timeout error in my application when I make the first API call. When I try again then it works fine. From the tail logs from zappa I assume that the keep_warm_callback had no effect on the application and did not keep the lambda warm. These are the tial logs from zappa:
Possible Fix
Steps to Reproduce
Your Environment
pip freeze
:zappa_settings.yaml
:dev: app_function: "app.app" "aws_region": "eu-west-3" "profile_name": "project-name" "project_name": "project-name-backend" "s3_bucket": "project-bucket" cors: true "vpc_config": "SubnetIds":