path contained the path to the file on your local filesystem instead of the path where the file should be stored on s3,
filename however stores the path+filename to the file in s3,
and therefore now returns the correct s3 object (with metadata, md5 etc.)
if the file is present on s3 and the md5 equals with the local version of the file,
the file will not be uploaded again (speeding up the overall process of deployment)
path contained the path to the file on your local filesystem instead of the path where the file should be stored on s3, filename however stores the path+filename to the file in s3, and therefore now returns the correct s3 object (with metadata, md5 etc.)
if the file is present on s3 and the md5 equals with the local version of the file, the file will not be uploaded again (speeding up the overall process of deployment)