Add "ice.billing_s3bucketregion" in the README

README.md

@@ -75,6 +75,8 @@ Using basic setup, you don't need any extra code change and you will use the pro
           ice.billing_s3bucketname=billing_s3bucketname1,billing_s3bucketname2
           # prefix of the billing files. multiple prefixes are delimited by ","
           ice.billing_s3bucketprefix=,
+          # location for the billing bucket.  It should be specified for buckets using v4 validation
+          ice.billing_s3bucketregion=eu-west-1,eu-central-1
           # specify your payer account id here if across-accounts IAM role access is used. multiple account ids are delimited by ",". "ice.billing_payerAccountId=,222222222222" means assumed role access is only used for the second bucket.
           ice.billing_payerAccountId=,123456789012
           # specify the assumed role name here if you use IAM role access to read from billing s3 bucket. multiple role names are delimited by ",". "ice.billing_accessRoleName=,ice" means assumed role access is only used for the second bucket.

src/java/sample.properties

@@ -28,7 +28,7 @@ ice.ondemandCostAlertThreshold=250
 # ec2 ondemand hourly cost alert emails, separated by ","
 ice.ondemandCostAlertEmails=
 
-# modify the following 5 properties according to your billing files configuration. if you have multiple payer accounts, you will need to specify multiple values for each property.
+# modify the following 6 properties according to your billing files configuration. if you have multiple payer accounts, you will need to specify multiple values for each property.
 # s3 bucket name where the billing files are. multiple bucket names are delimited by ",". Ice must have read access to billing s3 bucket.
 ice.billing_s3bucketname=billing_s3bucketname1,billing_s3bucketname2
 # location for the billing bucket.  It should be specified for buckets using v4 validation