Properly parse the JSON additionalArtifactKeys

[andrewmcgilvray]

Parsing fails when it is an array of strings.
"additionalArtifactKeys":[{"artifactType":"QuicksightManifest","name":"QuickSight/cost_report_hourly_gzip-20210501-20210601-QuickSightManifest.json"},{"artifactType":"RedshiftCommands","name":"20210501-20210601/20210809T193620Z/cost_report_hourly_gzip-RedshiftCommands.sql"},{"artifactType":"RedshiftManifest","name":"20210501-20210601/20210809T193620Z/cost_report_hourly_gzip-RedshiftManifest.json"}]

[andrewmcgilvray]

This change will definitely help people that have any of these options turned on in their cost and usage reports :

Without this change Ice will fail.

[adapasuresh]

Hi Jimroth,

I did deploy the docker image "" into my AWS EKS cluster with below "ice.properties" and am getting below error.
Can you suggest if am missing anything here. S3 has correct permissions with access_ket and secret_key.

ice.properties

Some configuration need some value passed into them.

Do not remove or comment out configurations that have ','

ice.processor=true
ice.reader=true
ice.work_s3bucketname=plural-ice/detailed-billing-bucket
ice.work_s3bucketregion=ap-south-1
ice.work_s3bucketprefix=work/
ice.numthreads=5
ice.hourlyData=true
ice.tagCoverage=none
ice.highstockUrl=https://code.highcharts.com/stock/4.2.1/highstock.js
ice.companyName=Pinelabs
ice.reader.localDir=/mnt/ice_reader
ice.monthlycachesize=12
ice.notice=
ice.processOnce=false
ice.startMonth=2017-06
ice.processor.localDir=/mnt/ice_processor
ice.reservationCapacityPoller=false
ice.breakoutFamilyReservationUsage=false
ice.writeJsonFiles=
ice.tagCoverage=none
ice.reservationPeriod=oneyear
ice.reservationUtilization=PARTIAL
ice.billing_s3bucketname=plural-ice/work-bucket
ice.billing_s3bucketregion=ap-south-1
ice.billing_s3bucketprefix=,
ice.billing_payerAccountId=,
ice.use_blended=
ice.costAndUsageStartDate=2017-10
ice.costAndUsageNetUnblendedStartDate=2019-01
ice.edpDiscounts=2019-01:5
ice.customTags=.

[nfonrose]

Hi Suresh, The stacktrace seems to indicate that a call to the EC2 describeRegions is getting a "Denied error" / 403. The IAM user (or Role) you are using needs more than S3 access. Nicolas

…

-- Nicolas Fonrose | Teevity | Founder +33.6.61.35.43.31 https://teevity.com - Cloud Costs Analytics for AWS, GCP and Azure powered by NetflixOSS Ice twitter - @nfonrose / @Teevity

On Wed, Aug 16, 2023 at 3:37 PM Suresh Adapa ***@***.***> wrote: Hi Jimroth, I did deploy the docker image "" into my AWS EKS cluster with below "ice.properties" and am getting below error. Can you suggest if am missing anything here. S3 has correct permissions with access_ket and secret_key. ice.properties Some configuration need some value passed into them. Do not remove or comment out configurations that have ',' ice.processor=true ice.reader=true ice.work_s3bucketname=plural-ice/detailed-billing-bucket ice.work_s3bucketregion=ap-south-1 ice.work_s3bucketprefix=work/ ice.numthreads=5 ice.hourlyData=true ice.tagCoverage=none ice.highstockUrl=https://code.highcharts.com/stock/4.2.1/highstock.js ice.companyName=Pinelabs ice.reader.localDir=/mnt/ice_reader ice.monthlycachesize=12 ice.notice= ice.processOnce=false ice.startMonth=2017-06 ice.processor.localDir=/mnt/ice_processor ice.reservationCapacityPoller=false ice.breakoutFamilyReservationUsage=false ice.writeJsonFiles= ice.tagCoverage=none ice.reservationPeriod=oneyear ice.reservationUtilization=PARTIAL ice.billing_s3bucketname=plural-ice/work-bucket ice.billing_s3bucketregion=ap-south-1 ice.billing_s3bucketprefix=, ice.billing_payerAccountId=, ice.use_blended= ice.costAndUsageStartDate=2017-10 ice.costAndUsageNetUnblendedStartDate=2019-01 ice.edpDiscounts=2019-01:5 ice.customTags=. [image: image] <https://user-images.githubusercontent.com/98078573/261042241-761013ad-3621-4300-87ca-20f0122e4036.png> — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJJJLUFPSRPUDY2OUGCYDXVTLJXANCNFSM5N4OLLSA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>