Enhanced consistency in ResourceType and ServiceName across a resourceId-related charge records

[ijurica]

Description

Consider refining the definitions of the Resource Type and Resource Name columns to ensure that all charge records associated with a specific Resource ID MUST(?) adhere to the same Resource Type and SHOULD(?) fall within the same Service Name.

Proposed approach

Adjust the definitions of ResourceType and ServiceName columns to encourage stricter consistency across charge records tied to a particular Resource ID.

[cnharris10]

@ijurica In the majority cases, this makes sense. In cases where a managed service leverages an IaaS service (ex: CloudWatch), the ResourceType might conflict with the ServiceName.

In the screenshot below for AWS, I could see a provider label, the service is CloudWatch but the resource is an EC2 Instance ARN.

• ResourceType --> Compute Instance (based on resource id)
• ServiceName --> Cloud Monitoring

Would we want to use SHOULD over MUST to account for special cases like this?

[ijurica]

I agree with @cnharris10 , SHOULD is a better fit