AWS Create OTA Discrepancy

Dear all,

I am still playing with the new OTA library and noticed a job-document syntax discrepancy between jobs created via the boto3 create_ota_update and the usual FreeRTOS-ARF-Job creation user interface from the console.
I noticed that from the console, the file array contains the key sig-sha256-ecdsa while when created from the boto3 library, the key name is sig-sha-256-ecdsa, which is not compatible with the new OTA library (parse failure).

Is that only me ? Or does it depend on the platform ID I use ? Or something else?

Thank’s in advance. Lucas

PS: by the way, could it be possible to add the FileVersion’s in the Job Document ? It would be really helpful :slight_smile:

Ok I think this issue has already been notified here Lack of validation/documentation of correct value for hashAlgorithm when creating an OTA update · Issue #3121 · boto/boto3 · GitHub . And we should take care of changing the HASH algorithm from “SHA-256” to “SHA256” …

Hi @lucas
Can you please help in raising your issue in Issues · aws/aws-sdk · GitHub repository?