AWS Billing Correlation - Support Any Storage Class

[bpayt2]

Environment:

• OpenShift v4.2
• AWS Account is member of AWS Organization

Request:
This feature requires the report to be in an AWS S3 Bucket as that is the default location for AWS Cost and Usage Reporting.

I am requesting support to read the AWS Cost and Usage Reports from any storage medium. I am using AWS EFS as the default storage class provisioner; would like to be able to configure the below (It is understood that the NFS PV would be created ahead of time in the operator namespace):

apiVersion: metering.openshift.io/v1
kind: MeteringConfig
metadata:
name: "operator-metering"
spec:
openshift-reporting:
spec:
awsBillingReportDataSource:
enabled: true
type: "sharedPVC"
sharedPVC:
claimName: "aws-billing"
reporting-operator:
spec:
config:
aws:
claimName: "aws-billing"
presto:
spec:
config:
aws:
claimName: "aws-billing"
hive:
spec:
config:
aws:
claimName: "aws-billing"

###Justification

• Do not want to use static AWS IAM User keys
• AWS account with OpenShift Cluster is a member account in AWS Organization; reports are currently emailed and loaded to AWS EFS.
• Any configuration version that supports a PV instead of AWS S3 would be acceptable

Thanks for the review!