IA to S3 migrator script #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On the prod server, this file path automatically gets cleaned up by a crontab job
If the files are large enough, they can exceed the file size cap of the Lambda, causing the deploy to fail. Logs are not necessary for the Lambda to run
aprilrieger
reviewed
Oct 1, 2024
aprilrieger
approved these changes
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref:
Add a script that allows downloading, extracting, and uploading files to S3 on the local machine. It then triggers the next preprocess steps (OCR and thumbnail), which still happen in Lambdas.
This step usually happens in a Lamba, but if the Zip file is large enough, it can timeout. This script is intended to be run on the production server.
Steps to use:
tmp/iaids.txtbin/migrate_iaidslog/ia_to_s3_migrator.logto watch the progress