AWS Lambda to extract static assets from CodePipeline Artifact to S3

Dear freelancers, we need a simple AWS-Lambda function that may be attached to AWS-CodePipeline. The CodePipeline-artifact passed to the Lambda-function is round about 200 MB to 300 MB in size with about 10.000 assets that need to be extracted to S3. Only files with definable file-extensions within definable folders and their subfolders should be extracted and synced with an S3-bucket. Therefore, an JSON-String will be set at CodePipeline invocation of Lambda-Function. *Parameters that should be set in CodePipeline:* - Folders (array of Strings containing foldernames, each with trailing slash) - Fileextensions (array of Strings containing f.e. ".js", ".css" and so on) - Target-Bucket (string - may be in another region as the codepipeline) *Rules* - files outside the defined folders should be ignored. - files with other file extensions should be ignored. - the file-extension must exactly match - while *.js is allowed, *.json might not. *.[login to view URL] would be okay, if *.js is allowed. - files existing on S3 (that match the rules for folder and file-type above) but do not exist in the Artifact should be removed from S3 (they may have existed in a previous version). - Only changed files should be copied to S3 (because of the amount of assets) - The folders in S3 may contain more file / objects then AWS API command listObjects() will return in a single request *Performance / Speed is really important.* - The whole process should take as less time as possible best much below 1 minute. - The listObjects() command should only be executed against the listed folders because the whole bucket may contain 250k files and more in folders, that are irrelevant for the sync-process. - The sync should be processed async so that putObjects & deleteObjects operations are processed in parallel but the number of parallel putObject and deleteObject operations should be capped so that they don't exceed AWS limits or result in a out of memory exception. - On production, the lambda-function will get max Memory possible assigned. Node.JS ore Python may be used (if possible with one of them) to develop this functionality. If you have any questions, feel free to ask.