AWS Textract Microservice - python or node or go
Budget: $150 – $250 USD
We want to be able to process a bunch of PDFs with text textract in a similar way as the aws console. The way we see this working is that you can setup a trigger on a s3 folder and we will dump in our pdfs there and it will process them 1 at a time and output a zip file to another folder of the results. today we upload a pdf like this and download the zip - https://www.dropbox.com/s/n05ygt9vna6fnmt/2021-10-29_14-48-23.png?dl=0 and we get back this https://www.dropbox.com/s/t7szrrz7jivl4w4/2021-10-29_14-48-35.png?dl=0 but now we need to scale this a bit beyond 1 file at a time.
we will not need a ui interface from my view we will put in a pdf to a folder called "input" you will grab that pdf and put it in a folder called "output" and you will also put the zip there when textract is done generating it (make sure same name as pdf). when we are done the "input" folder should be empty and we can drop in more of them as needed.
if there is a failure for some reason the lambda should write the problem in some sort of log file instead of the zip file that was expected. it can be named the same as the pdf
your code can be in node, python, or go. and needs to be commented for how we deploy the serverless function. we would like to make sure variables like the s3 bucket are easy to manage and update as needed without needing to touch source and make a new build.
while developing this solution you will need to use your own aws account. my team will deploy when you are done using just your documented repo details.
would be good if you can use serverless.com framework for the code so its easy to manage.
in your response let me know anything specific to textract so i know its not a robot bid. if its missing mention of this i will remove it
we will not need a ui interface from my view we will put in a pdf to a folder called "input" you will grab that pdf and put it in a folder called "output" and you will also put the zip there when textract is done generating it (make sure same name as pdf). when we are done the "input" folder should be empty and we can drop in more of them as needed.
if there is a failure for some reason the lambda should write the problem in some sort of log file instead of the zip file that was expected. it can be named the same as the pdf
your code can be in node, python, or go. and needs to be commented for how we deploy the serverless function. we would like to make sure variables like the s3 bucket are easy to manage and update as needed without needing to touch source and make a new build.
while developing this solution you will need to use your own aws account. my team will deploy when you are done using just your documented repo details.
would be good if you can use serverless.com framework for the code so its easy to manage.
in your response let me know anything specific to textract so i know its not a robot bid. if its missing mention of this i will remove it