143 karma · joined March 29, 2013
To answer your question, there isn't really a workaround for this yet, although indexing should be much quicker than "days". All the keys are listed recursively before running the lambda expression locally. If you have a huge number of files, this can take several minutes, maybe hours depending on the scope.
A workaround I've been considering is using a generator function to list the keys; that way, the lambda expression can start immediately, generating keys as it needs them.
Edit: This is not related to aws lambda...sorry for the confusion
Writing this was a necessity for me, being a 1-person data team coming from a Node.js background.
Similarly, Python 2 might not be made anymore, but it is used everywhere, and people are making new things with it. So...it's also not obsolete.
I'm very hopeful for quicksight, but unfortunately it feels very clunky and hard to use at the moment. Hopefully they improve the clunky UI and give it a SQL inerface.