Map AWS Marketplace to ATUM

Edit online

If you consume services from the AWS Marketplace, you must ingest and model those bills the same as your AWS service bills. AWS creates a separate AWS Marketplace billing file for each billing report you configure to be created in your billing preferences.

As with typical AWS services bills, Apptio recommends using the AWS Marketplace Cost Allocation report that aggregates at a monthly level. For more information about AWS Marketplace services, visit https://aws.amazon.com/marketplace/.

Applies to: Apptio Costing Standard or Apptio Cloud Cost Management running on TBM Studio v12.3.3 or later.

Task 1: Set up a new DataLink connector to automate the ingestion of your Marketplace bill

Edit online

Procedure

  1. Create a new Datalink (Classic) AWS connector, or copy an existing AWS connector (Learn more).
  2. Configure the authentication.
    Note: When using delegation, if you copy an existing connector, this section will be populated already.
  3. Click Billing Report.
  4. In Report Type, select Advanced.
  5. In File Pattern, type the following pattern:“<your AWS account number>-aws-cost-allocation-AWSMarketplace-{CYYY}-{MM}.csv>”
  6. Configure the Apptio Destination, Notifications, and Scheduling based on your specific requirements.

Task 2: Append AWS Marketplace Data

Edit online

Procedure

  1. In Project Explorer, expand Tables, then expand Cloud Service Providers, and click AWS Marketplace Master Data.
  2. Append the data set that was just uploaded through DataLink.

Task 3: Create an ATUM mapping file for your AWS Marketplace billing line items

Edit online

This step ensures that the line items in your AWS Marketplace billing file are mapped to ATUM towers and subtowers and to Apptio’s normalized units of measure so they can be analyzed and modeled based on standard classifications.

The lookups in this mapping file are different from the Apptio AWS mapping file (the bill attributes will likely be different). For the AWS Marketplace bill, base the lookups on the ProductName or Seller of Record attributes, or both. For example, all line items for a security vendor could be mapped to the Security tower and subtower.

Procedure

  1. Create a new Microsoft Excel file based on an AWS Marketplace bill.
  2. 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 the sole attribute upon which the lookup is based. However, if you find the granularity of ProductName or potentially even UsageType are necessary, you can include them too.
  3. Modify the Excel file with the unique combination of values in the selected attributes.
  4. Add fields for Tower, Subtower, Unit, and Type, then fill in the values.
  5. For a discrete set of unit values to select from, refer to the <post> on TBM Connect.
  6. Upload the mapping file.
  7. Append the file into the Cloud Service Provider Lookup Master Data.
  8. Map a concatenation of your lookup fields into the Item field.
    For example, Item = Seller of Record&&ProductName . Make note of the details of this particular mapping step because you will do the same mapping when appending the AWS Marketplace billing file to the Cloud Service Provider Master Data