-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ValueError: Insufficient data - ... bytes requested but only 18358 available on AWS Lambda/Amazon Linux #48
Comments
@robincsamuel what is the server you are communicating with? |
@abhishek-ram it’s a django-pyas2 project running on an AWS EC2 (ubuntu) |
@abhishek-ram I did some testing and it works fine on my local system. I connected my local application to the remote database (the DB lambda use) so that the keys are the same (they are loaded from the database) and it worked fine with the same payload, send from the same server I used with the lambda. I've also logged the keys & payload from the lambda and that too is fine. |
Then it is most likely an issue with the build of the server where its running |
yeah, that's my guess too. It's a standard AWS Lambda platform. I've posted the issue on asn1crypto repo as well. |
I’m closing this assuming it’s asn1crypto issue. |
I'm trying to build an AS2 gateway with AWS Lambda (Amazon Linux, x86_64), using chalice. I got a base version working fine on my local system.
However, I'm facing several issues with different configurations and the major one is the decryption/decompression issue with asn1crypto library.
Below is the stack trace,
Here's is a similar issue, wbond/asn1crypto#85
Any hints would be helpful, and thanks for the package :)
The text was updated successfully, but these errors were encountered: