I was having trouble using the cli-input-json by following the AWS documentation which seems simple enough (here), but was as per usual missing a key element that they assume everyone knows. That being that the JSON file needs to be UTF-8 encoded. By default when using Visual Studio Code & Powershell, it would get the skeleton file in UTF-16 LE encoding.
The error that the CLI would provide was a JSON formatting error.
Props goes to Sudarpo Chong with a comment on a similiar post, but doesn't focus on this as a key issue.
Summary:
- ensure JSON file in UTF-8 encoding.