lambci / cmda Goto Github PK

BTW. nice piece of work you got. This is not a issue, perhaps a feature request to have CLI create-vpc-endpoint to allowed specifying the AWS region.

When uploading file(s) over ~50mb, the cmda will throw timeout error due to timeout setting in the lambda function. And the cmda will asked to try to fix it by creating a vpc endpoint to S3.

When uploading to a file system that I do not have write permissions for the upload command fails silently.
When uploading to a non-existent directory the upload command fails noisily, as appropriate.
The mkdir command fails as expected, with appropriate messages.

I realize these are two very different execution paths.

cmda myfile.txt /var/task

fails silently

cmda myfile.txt /bar/no_such_dir

fails noisily.

cmda mkdir /var/fail_dir

fails noisily.

ps thanks for this utility!

First, amazing tool and thanks so much for the work into this. I've been exploring using this tool for moving a key service to Lambda unlocked by EFS. So far so good when doing simple things like ls and exec/echo writes. But on my first upload I'm getting his error.

Invoking Lambda to copy files remotely...Rate Exceeded.

I can tell that the Lambda did compress a directory of files ~190MB and compressed ~80MB to the coda bucket. While this was happening, I was watching the CloudWatch Logs of the Lambda and this error above was reached long before I saw the cmda Lambda reach the "END RequestId: ..." part in the log. Eventually CloudWatch shoed this.

REPORT RequestId: f4fa646c-685c-44ab-8c2f-effc69a35cb3	Duration: 524145.03 ms	Billed Duration: 524200 ms	Memory Size: 3008 MB	Max Memory Used: 79 MB	

And after that I could confirm that nothing was uploaded. So thinking something happened during the decompress & write. FYI, I have verified that the cmda setup works by doing something like this.

$ cmda sh -c 'echo hello > /mnt/efs/someremotefile.txt'

Right now my EFS is in Bursting and General Purpose modes. Maybe the write to disk is slow and I should change it to provisioned? Other thoughts? Again, thanks for this heroic 🦸‍♂️🦸‍♀️ tool.

The cmda stack could be reduced to a CDK construct to attach to an existing CDK stack

Currently we just read cached credentials, but we could do the whole flow