If you are consuming services from the AWS Marketplace, you will want to ingest and model those AWS Marketplace* bills just as you ingest and model normal AWS service bills.  AWS creates a separate AWS Marketplace billing file for those billing reports you have configured to be created in your billing preferences.  As with normal AWS services bills, Apptio recommends using the AWS Marketplace Cost Allocation report that aggregates at monthly level.

Step 1: Setup a new Datalink connector to automate the ingestion of your marketplace bill

This step will automate the ingestion of your AWS Marketplace billing file.

• Create a new Datalink AWS connector (or copy an existing AWS connector)
• Configure authentication
• Select Billing Report
• In Report Type, select Advanced
• In File Pattern, enter the following pattern: “<your AWS account number>-aws-cost-allocation-AWSMarketplace-{CYYY}-{MM}.csv”
• Configure the Apptio Destination, Notifications, and Scheduling based on your specific requirements

Step 2: Create an ATUM mapping file for your AWS Marketplace billing line items

This step will ensure that the line items in your AWS Marketplace billing file are mapped to ATUM towers/subtowers as well as Apptio’s normalized units of measure and can be analyzed and modeled based on these standard classifications.

The lookups in this mapping file will diverge a bit from how they are done for the Apptio AWS mapping file in that the bill attributes used to perform the lookup will likely be different.  With the AWS Marketplace bill, the attributes on which lookups should be based include ProductName and/or Seller of Record (for example, all line items for a security vendor could be mapped to the Security tower and subtower).

• Create a new excel file based on an AWS Marketplace bill.
• Determine which field or combination of fields makes the most sense as a lookup field.  For example, if Seller of Record is granular enough to derive subtower, Seller of Record can be sole attribute upon which the look up is based.  If, however, you find the granularity of ProductName or, potentially even, UsageType are necessary, you may include them as well.
• Modify the excel file with just the unique combination of values in the selected attributes.
• Add Tower, Subtower, Unit, and Type fields to the file and fill in the values
• For a discrete set of Unit values to select from, please refer to the <post> on TBMConnect
• Upload that mapping file to Apptio
• Append the file into the Cloud Service Provider Lookup Master Data
• Map a concatenation of your lookup fields into the Item field (e.g. Item = Seller of Record&&ProductName).  Keep the details of this particular mapping step in mind as you will have to do the same mapping when appending the AWS Marketplace billing file to the Cloud Service Provider Master Data in the next step.

Step 3: Append the AWS Marketplace billing file into the Cloud Service Provider Master Data

This step will append the AWS Marketplace billing file into the Cloud Service Provider Master Data and ensure that the marketplace costs are modeled alongside the standard AWS service costs. Similar to other data sources it is recommended that you transform the raw AWS Marketplace bill first and then append that transform into the Cloud Service Provider Master Data.

• Create a new transform of the AWS Marketplace billing file
• Ensure all the total and subtotal rows are filtered out (use the Record Type column and include only LinkedLineItem rows)
• Append the transform into the Cloud Service Provider Master Data
• Use mappings similar to those used when mapping the AWS Cost Allocation report
• Append the AWS Marketplace billing file to any additional consumptive based reporting files.

*For more details on AWS Marketplace services, please refer to content AWS’ website: https://aws.amazon.com/marketplace/