AWS Signer causes large OTA file size / object size increase

0

When using AWS Signer to sign an AWS IoT OTA update, how much bigger should I expect the signed binary to be?
The file size / object size of the signed binary in S3 is much larger than the unsigned binary.
I'm signing using the following AWS CLI command:
$ aws signer start-signing-job
--source 's3={bucketName=my_OTA_bucket,key=my_OTA_binary.bin,version=my_latest_version_GUID}'
--destination 's3={bucketName=my_OTA_bucket,prefix=signed-}'
--profile-name my_code_signing_profile

How many KB should I expect the AWS Signer to add to the resulting OTA binary?

-Brant

brant
已提問 3 年前檢視次數 236 次
1 個回答
0

I discovered the increase in size caused by AWS Signer is expected and only affects the size of signed S3 object and the signed object in transport.

The raw binary size of the OTA on the IoT thing is not affected.

The signed binary is stored as JSON with the raw payload binary encoded in text, resulting in the increase in file size.
The signed JSON file is comprised of "rawPayloadSize", "signature", "signatureAlgorithm" description and
a "payload" text encoding of the binary.

When it reaches the thing, the encoded binary's signature is checked and the payload is converted into the original OTA binary file.

-Brant

brant
已回答 3 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南