If AWS Cost and Usage report (CUR) has resource tags with similar names but in different cases, the platform rename columns in FlexReport to map the actual tag names in CUR by appending 1
at the end of every uppercase character. The converted name then will be appended to the original tag name with `__ ` separator.
For example: If the following user-defined tags are present in CUR,
resourceTags/user:client
resourceTags/user:Client
resourceTags/user:cLient
then the FlexReport column names in the platform will be renamed in the following manner:
Original Tag Name |
Renamed Tag Name |
FlexReport Column Name |
---|---|---|
|
|
|
|
|
|
|
|
|
Note that, if a similarly named tag with a different case is introduced in a subsequent CUR, then the platform would first show the initial column name as is but eventually would also show the two columns renamed as per the logic given in the table.
For example: If resourceTags/user:client
is present in the 2020-06
CUR, you will see resourceTags_user:client
as FlexReport column name in the UI and API. But if a new similar tag resourceTags/user:Client
is added in a subsequent CUR drop, either in the same month of 2020-06
or in a subsequent month like 2020-07
, then the platform will rename the FlexReport column name. However, the original column name resourceTags_user:client
would remain in FlexReports, and its data would correspond to from when the column was included until when the second similar tag was introduced.
Therefore, you will see a total of three FlexReport column names in the UI and API. FlexReport column name: resourceTags_user:client
, resourceTags_user:client___user:client
, resourceTags_user:Client___user:C1lient