AWS Billing download is failing due to unsupported resource id format in AWS billing data csv file.DescriptionIssue: The AWS provider billing download in Cloud Cost management encounters a failure when there are line items from "AWSGlue" product with unsupported resource id format in the downloaded billing data CSV file. Root Cause: In general, the resource ids are expected a string without any quotes. But for "AWSGlue" product, resource ids comes with double quotes. We had a similar issue with another product AWS Chime Dial-In. Applicable 4.0 release. Sample Resource Id: "resource_id":"{"microServiceUuid":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"&comma"microService":"CATALOG"&comma"region":"us-east-1"&comma"stage":"prod"&comma"audit":true}" Steps to Reproduce Steps to reproduce: Log in to instance and setup the AWS environment.Make sure that the line items from 'AWSGlue' product should present in the downloaded billing data CSV file.Run AWS billing download.AWS billing download fails with below error Error: Processing failed with error: AWSCSVRecordProcessor :: xxxxxxxxxxxx-aws-billing-daily-00001.csv.zip:: SNRestAPIInvoker:: SNRestAPIInvoker:: SNRestAPIInvoker:: SNRestAPIInvoker:: {"status_code":500,"message":"{\"error\":{\"message\":\"Script Evaluation Exception\",\"detail\":\"Cannot convert com.glide.rest.util.RESTRuntimeException: The payload is not valid JSON. to org.mozilla.javascript.ScriptableObject (sys_ws_operation.0b2fe5e8cb6940108941d796634c9ce2.operation_script; line 10)\"},\"status\":\"failure\"}"}WorkaroundAdded code to handle AWS Billing Download failure due to special characters present in Resource ID. Steps to apply the fix and validate in 4.0 version of cloud cost management: Please find the attached update set which contains the fix for PRB1697873.Use the scope Cloud Integrations AWS to commit the update set sys_remote_update_set_b37b7c28c346311039a5f663e401311b.xmlRerun billing download and wait for it to complete without any failure in the execution.Related Problem: PRB1697873