After following the deployment notes and deploying this solution I found that this was not transferring any data. After some Investigation I found StartFileTransfer API calls returning InvalidRequestException errors. This seems to be related to an extra forward-slash ("/") in the localDirectoryPath requestParameter on this line: https://github.com/aws-samples/file-transfer-sync-solution/blob/main/transfer_sync_service/lambda/sync_files/sync_files.py#L239
LocalDirectoryPath=f"/{event['SyncSettings']['LocalRepository']['BucketName']}/{event['SyncSettings']['LocalRepository']['Prefix']}{current_prefix}",
There is an extra slash between {event['SyncSettings']['LocalRepository']['BucketName']} and {event['SyncSettings']['LocalRepository']['Prefix']} because {event['SyncSettings']['LocalRepository']['Prefix']} already has a leading forward-slash?
After following the deployment notes and deploying this solution I found that this was not transferring any data. After some Investigation I found StartFileTransfer API calls returning InvalidRequestException errors. This seems to be related to an extra forward-slash ("/") in the localDirectoryPath requestParameter on this line: https://github.com/aws-samples/file-transfer-sync-solution/blob/main/transfer_sync_service/lambda/sync_files/sync_files.py#L239
LocalDirectoryPath=f"/{event['SyncSettings']['LocalRepository']['BucketName']}/{event['SyncSettings']['LocalRepository']['Prefix']}{current_prefix}",There is an extra slash between
{event['SyncSettings']['LocalRepository']['BucketName']}and{event['SyncSettings']['LocalRepository']['Prefix']}because{event['SyncSettings']['LocalRepository']['Prefix']}already has a leading forward-slash?