aws-code-deploy artifact issue zip file

[azam pasha]

1. I'm using the Bitbucket Pipe aws-code-deploy:1.6.0 to upload and deploy a zip artifact to an EC2 instance via AWS Code Deploy. The FOLDER and S3_BUCKET options correctly place the artifact in the desired S3 path, and the deployment triggers successfully.
2. However, the uploaded file in S3 has a MIME type of binary/octet-stream instead of application/zip. Because of this, the file isn't recognized as a ZIP when downloaded directly from S3, causing issues in manual usage or validation.
3. Previous versions like 0.2.10 uploaded it with the correct type but lacked support for setting a folder path in S3.
4. Has anyone else experienced this? Is there a workaround or plan to support setting the correct MIME type in newer pipe versions?

[Jim Knepley - ReleaseTEAM]

Hi @azam pasha, welcome to the community. 

Looking at the source code, the content-type isn't specified in the call to put_object(), and using "binary/octet-stream" as a default isn't that far-fetched. I honestly don't think the MIME type of the object upload makes a difference, but I could be completely wrong about that.

Are you setting the BUDLE_TYPE variable in your pipeline? It defaults to "zip," but that has more to do with the code deployment than the file upload. I would look there first.

[azam pasha]

yes, we are setting BUNDLE_TYPE : "zip", variable in the code deployment step

[Jim Knepley - ReleaseTEAM]

OK, good.

What symptoms are you referring to when you say "the file isn't recognized as a ZIP when downloaded"?