Amazon Web Services configuration

Install the Cloud component the same way you install the other CTF components:

1. Open the Costing Standard project.
2. Click the Projects tab.
3. Click on Components.
4. Click the CTF - Cloud Service component.
5. Click Install.

Install the CTF - Amazon Web Services component the same way you install the other CTF components:

1. Open the Costing Standard project.
2. Click the Projects tab.
3. Click Components in the Ribbon.
4. Click the CTF - Amazon Web Services component.
5. Click Install.

Think of the Cloud Service Provider Master Data table as the central repository for all of the cloud data. As you bring data into the application each month, you will add it to this table by "appending" the data. If you are using a DataLink connector, the data automatically will be brought in each month.

1. To append a billing data table:
2. In the Project Explorer, click the Cloud Service Provider Master Data table.
3. Click the Append step in the pipeline.
4. Click Append Table in the Details area.
   The Append to... dialog is displayed as shown in the following image.
5. Select the transform data set and click Next.
   The application displays the following mapping dialog:
6. Map the columns as shown in the following tables in the mapping sections.
   If a field is not available from the drop-down list, type the value in the field. As you begin entering the text, matching column names will be displayed. Note when entering "& ", there is a space before and after the & . All of the fields listed below must be mapped.
7. Click Save.

   Table 1. Cloud service provider field descriptions

   Field	Short Description	Formula
   Item	The second level categorization of the service provided (e.g. for AWS, "Box Usage").
   Lookup	An autogenerated concatenation of the Item and Procedure columns; this is used for the service mapping lookup from the Cloud Service Provider Lookup that maps the specific provider service to the IT Resource Sub-Tower.	=Item && Procedure
   Procedure	The third level categorization of the service provided (e.g. for AWS, the operation the Type / usage is preforming -- RunInstances:0002)
   Type	The generic grouping for the item used by the application.
   Unit	The unit of measure for the service provided.
   Cost	The total, net cost of the service to the customer (inclusive of any tax, discounts or other factors).
   Description	The detailed description of the service provided.
   ITRT_Cloud_Key	A predefined key used to allocate costs from the Cloud Service Provider object to the IT Resource Towers object.	="Public_Cloud" && Subtower
   Product	Name of the cloud service provider. NOTE: For allocations to flow from the Vendor object, this name must match the company name in the Vendors list.
   Public Cloud Metadata 1	Additional information from the bill you would like to report on.
   Public Cloud Metadata 2	Additional information from the bill you would like to report on.
   Public Cloud Metadata 3	Additional information from the bill you would like to report on.
   Rate	The effective average unit cost (or rate) of the service consumed; calculated by dividing cost by quantity.	= Cost / Usage Qty
   Subtower	The mapped IT Resource Sub-Tower to which the service belongs (e.g. for AWS, "Box Usage" is mapped to Cloud Compute and, based on the Procedure, it is mapped to Cloud Compute Linux or Cloud Compute Windows).	=Lookup(Lookup,Cloud Service Provider Lookup,Lookup,SubTower)
   Type	The generic grouping for the item used by the application.
   UID Metafield	Prescriptive unique identifier used to determine the level of granularity of the line items in the provider bill.
   Unique ID	A unique identifier or generated concatenation of columns to establish the desired granularity of data for allocations and reporting.	=Customer Number && Provider && Product && Item && Procedure && UID Metafield
   Unit	The unit of measure for the service provided.	=Lookup(Lookup,Cloud Service Provider Lookup,Lookup,Unit)
   Usage Qty	The quantity or total amount of the service delivered.
   Vendor_CSP Key	A predefined key used to allocate costs from the Vendor object to the Cloud Service Provider object.	="vendor_cloud" && Provider
   Application	The application consuming the cloud service.
   Environment	The stage in the development lifecycle where the infrastructure is being used. Apptio Required values include: Production, Development, Test, DR
   Purpose	The general use for the cloud resource, such as Web Server, App Server, Database Server, Utility Server, etc.
   Consumer	The primary business consumer of the cloud service.
   Consumer ID	The ID of the primary business consumer of the cloud service.
   System Owner	The individual responsible for maintaining the cloud service.
   Project	The name or ID of the project for which the cloud service is used.
   Cost Center	The specific cost center responsible for budgeting and managing cloud service.

   Table 2. AWS mapping

   Cloud Service Provider Data	AWS Billing Transform
   Item	=UsageType
   Procedure	=Operation
   Cost	=TotalCost
   Description	=ItemDescription
   Product	=ProductName
   Provider	=”Amazon Web Services”
   Usage Qty	=UsageQuantity
   UID Metafield	Customer-specific. This field should include enough customer-specific data (e.g. tags) in order to ensure the Unique ID field is unique. See Unique ID Reference for more details.
   Application	Customer specific. Use account/subscription or tags to populate.
   Environment	Customer specific. Use account/subscription or tags to populate.
   Purpose	Customer specific. Use account/subscription or tags to populate.
   Consumer	Customer specific. Use account/subscription or tags to populate. A field that is often used is LinkedAccountName.
   Consumer ID	Customer specific. Use account/subscription or tags to populate. A field that is often used is LinkedAccountID.
   System Owner	Customer specific. Use account/subscription or tags to populate.
   Project	Customer specific. Use account/subscription or tags to populate.
   Cost Center	Customer specific. Use account/subscription or tags to populate.

   The AWS data includes totals rows and other non-data rows. After you import the report data into the Apptio application, you must remove these rows from the transform of the data set by specifying the filters shown below.

   

   To remove the rows:

   1. In the Apptio application, navigate to the Studio>Data tab.
   2. Select the AWS data file.
   3. From Quick Tasks, click Add Data Filters.
   4. Create the filter shown in the previous image.

• Bring in the RI purchase details.

  To get an accurate monthly cost for Reserved Instance purchases, you will need to upload RI purchases collected from AWS (either programmatically via an API or from the AWS console). This step should be repeated regularly (likely monthly) to account for ongoing RI purchases.

  For formulas (described in the next section) to work without modification, name the table “Reserved Instances”.

  Recommended columns include:

  • RI ID
  • Instance Type
  • Zone
  • Start
  • Expires
  • Term
  • Offering
  • Upfront Price
  • Usage Price
  • Instance Count
  • Recurring Charges
  • Platform
  • Tenancy
• Access RI purchase data in the AWS console

  To access RI purchase data from the AWS console, you will need to open either EC2 or RDS product pages and copy the data in the reserved instance purchase lists. The following screen shot highlights the reserved instance data in EC2. See the AWS documentation for more information on getting access to view RI purchase data in AWS.

  
• Access RI purchase data programmatically

  You can leverage the AWS APIs to access RI purchase data programmatically. The EC2 and RDS APIs are (respectively):

  • ec2-describe-reserved-instances
  • rds-describe-reserved-db-instances

  These APIs will return output equivalent to that shown in the AWS console screen shot above. For more information on accessing and executing AWS APIs, please refer to AWS documentation.

• Append the data.
  Using the same procedure outlined in Step 3, append the Reserved Instance data to the AWS RI Purchases Master Data data set.

The CTF application uses sub-towers to correctly allocate cost. The out-of-the-box web services data may not have contained enough information to assign a sub-tower to each entry in the file. If there are entries without assigned sub-towers, you must create an Excel file that provides the necessary sub-tower information. In later steps, you will upload the Excel file and map it to the Cloud Service Provider Lookup Master Data table.

1. Create an Excel file with a name that matches your work flow.
2. Add the following columns to the Excel file:
   • Item (usage type)
   • SubTower
   • Type (based on the billing data)
   • Unit
   • Procedure
3. Enter information in the columns for each line in the web services file that does not have an automatically assigned sub-tower.
4. Save the spreadsheet as a .csv file.

To bring the Excel file you created in the previous step into the Costing Standard application, upload the data into a new table.

1. On the Data tab, click the New icon and then click Upload on the menu.
2. Click the Home tab in the Ribbon.
3. Click the New menu and then click Table.
4. In the Create Table dialog, enter a name for the table.
   Use any name that fits with your workflow.
5. Enter a category. As you start typing, matching names of categories that already exist will be displayed.
   Also, you can enter a new category name. The categories are used to organize the tables in the Project Explorer.
6. Click OK.

   The application creates the table and displays the Source step in the transform pipeline as shown in the following image

   .
7. Click the File Upload option.
8. Do one of the following:
   • Click in the Details pane and browse to the file you want to upload.
   • Drag a file into the Details pane.
9. An Import step is added to the pipeline.

After uploading the sub-towers Excel data set, the next step is to append the data set to the Cloud Service Provider Lookup Master Data data set. After you append the data set, the entries in the billing transform data set that were missing a sub-tower entry should now have entries.

1. In the Project Explorer, click the Cloud Service Provider Master Data table.
2. Click the Append step in the pipeline.
3. Click Append Table in the Details area.

   The following Append to... dialog is displayed

   
4. Select the Excel data set and click Next.

   In the previous image, the Excel data set is named Missing Subtowers. The application displays the mapping dialog shown in the following image. If you named the columns correctly in the Excel file, the columns should match.

   
5. Click Save.

If you have not installed the Vendors component, you must manually configure the allocation from the Cost Source object to the Cloud Service provider object in the Cost model. After installing the Cloud Service Provider component, complete the following steps to configure the allocation.

1. In uploaded cost source data set, add a new column:
   • Name: Cost Source_Cloud Key
   • Type: Key
   • Value: ="Vendor_CSP"&&Vendor Name
2. Save the table.
3. In the Project Explorer, click the Cost Source Master Data table.
4. Click the Append step in the transform pipeline.
5. Edit the appended cost source table.
6. In the mapping table, click Select additional source columns.
7. Select your new column Cost Source_Cloud Key and click OK.
8. In the Project Explorer, click the Cloud Source model table.
9. Under Allocations, click Add Allocation.
10. Complete the fields to allocate value to the Cloud Service Provider object.