monkut

This issue covers the docker usecase: https://github.com/zappa/Zappa/issues/1140

Yes, BasicAuth in flask doesn't work well with zappa, you may need to integrate with a lambda authorizer to get the effect you desire.

Since zappa does support other authentication methods, it would be nice to have a simple basic auth implementation that could be easily deployed with zappa without having to fiddle around...

It looks like there are a lot of remaining prints in the codebase, can you look into and handle what you can in this PR?

It appears that you're using a black text on white background setting in your terminal. Zappa uses color in the text and I suspect this is due to the text...

I use localstack, but only for it's other aws services support, and test my application against that without *deploying* the application to lambda in localstack.

Not sure what you're asking for here. Are you looking for an example?

If you are using custom domains, I don't think the staging prefix will interfere given a custom domain configuration.

pip-tools is no longer a requirement of zappa, closing.

You could be setting the bucket to something already taken or controlled by another account. Remember that s3 bucket names are globally unique. Try adding a suffix/prefix to the bucket...