Chalice Deploy Time Out

[sendaimono]

I don't know which python runtime you use. Working configuration for 3.6 is (both need to be specified in requirements.txt)

psycopg2==2.7.7
psycopg2-binary==2.7.7

make sure that you deploy your app from same runtime architecture that lambda uses. Maybe try building the app in docker-image python3.6-stretch

[wutachih]

Thank you for the hint.

It doesn't help me much. The AWS lambda backend doesn't seem to handle latency well. The lambda update also consumes quite a bit of bandwidth.

On Wed, Nov 17, 2021 at 8:00 AM Mikołaj Kowal @.***> wrote:

I don't know which python runtime you use. Working configuration for 3.6 is (both need to be specified in requirements.txt)

psycopg2==2.7.7 psycopg2-binary==2.7.7

• make sure that you deploy your app from same runtime architecture that lambda uses. Maybe try building the app in docker-image python3.6-stretch

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/aws/chalice/issues/1836#issuecomment-971720527, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIFTARSMK3WGMNWF3MALLZ3UMPGTPANCNFSM5IAG4ITA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

-- Michael

[theobouwman]

I gave my functions the exact same configurations.

But the functions in server-aws-development can access internet (tested it with GET call to google.com), but the authoriser function server-aws-token_authorizer can't. How is this possible?