monkut

Just re-reviewing this, and I believe that the client IP is available in "REMOTE_ADDR". https://github.com/zappa/Zappa/blob/master/zappa/wsgi.py#L89-L96 This isn't the lambda context "sourceIp", but I suspect it should be the desired value.

@nickovs Ok, I checked and confirmed that I am using the REMOTE_ADDR value it a project. If it's not available by default from APIGW, I suspect that I configured the...

I don't see a problem adding the lambda context sourceIP, but currently the client IP should be available in "REMOTE_ADDR". https://github.com/zappa/Zappa/blob/master/zappa/wsgi.py#L89-L96

@rehanhwr Can you run `make black` / `make isort` on this?

@kyaryunha Thanks for the contribution. I think we can get this in the next release. The linter is failing, you'll need to run `make black` / `make isort`.

We use isort/black for formatting, you don't need to change the format manually. Currently the linter is failing. You need to run `make isort`, and `make black` to resolve the...

@muddi900 Can you add a testcase for this?

I'm not clear on what the issue is. It sounds like you're setting your api gateway stage to `v1`, but have your zappa stage set to `stage`, is that correct?...

Can you open or link an issue to this?

Yes, if we have `read_capacity_units` and `write_capacity_units` settings in Meta, it would be helpful to have auto-scale capability as well. ``` class Meta: read_capacity_units = 2 # with auto-scale use...