♦  Applies to: Cost Transparency on TBM Studio 12.0 to 12.5.x

For CBM and Cloud on Cost Transparency 12.6 and later, see Apptio for Cloud Knowledge Base .

Use the following instructions to ingest data from your AWS environment. Apptio Cloud on Cost Transparency (CCM) relies on the following data sets.

NOTE:  For information about deprecated billing formats, see AWS Deprecation of Billing Formats.

Steps

1. Go to your Cloud Cost Management Datalink instance.
2. Select the Default Agent.

Setup the current month daily billing ingestion (based on the Detailed Billing Report)

1. Create a new AWS connector, and name it "DBR – Current Month."
2. Select your preferred authentication method (Apptio recommends using Delegation for optimal security). 
   This step assumes you have already configured AWS to allow Datalink to authenticate and read data from your AWS environment. If not, see Complete AWS configuration dependencies.
3. Enter your AWS authentication credential details.
4. In Select data source, select Billing Report.
5. In Report Settings, enter the name of the S3 bucket in which your AWS bills are placed.
6. Leave the File Prefix blank.
7. Select the Account Id for your AWS payer account.
8. Select Detailed Billing Report with Resources and Tags (automatic transform).
9. Skip the Column Mapping section for now. This will be revisited when mapping your tags/accounts to the Apptio schema.
10. In AWS Time Period, select Current Month.
11. In Apptio Destination, select R12 with Front Door for Apptio Version.
12. In Apptio Instance, select Cost Transparency.
13. In Domain, select your Apptio domain. This should be <your company name>.com.
14. In Project, select Cost Transparency.
15. Enter "AWS Billing" into Category.
16. Enter "AWS" into Source System.
17. Select Current Month in Time Period.
18. In the Schedule section and select Enable Schedule.
19. From the Frequency dropdown, select Daily.
20. Select a Start Time that is early morning.
    This is a value that might need to be updated as you start to understand when your DBR values are updated.
21. Test the connector.
22. Save the connector.

Setup the prior month daily billing ingestion (this is to ensure you are getting the final bill for the previous month uploaded into the system)

1. From the Connector list, select Copy from the Action menu for the DBR – Current Month connector.
2. Change the name to "DBR – Prior Month."
3. Change the two Time Period fields to Previous Month.
4. Change the schedule to run a bit later in the day.
5. Test the connector.
6. Save the connector.

Setup the monthly billing ingestion (based on the Cost Allocation Report)

1. From the Connector list, select Copy from the Action menu for the DBR – Prior Month connector.
2. Change the name to "Cost Allocation Report."
3. In Report Settings, change the Report Type to Cost Allocation Report.
4. In Schedule, change the Frequency to Monthly value to a day close to the 5^th of the month.
   This value might need to be changed as you figure out when AWS finalizes your bill.
5. Test the connector.
6. Save the connector.

Setup the EC2 reserved instance purchase connector

1. From the Connector List, select Copy from the Action menu for the Cost Allocation Report connector
2. Change the name to Reserved Instances – EC2
3. In Select data source, change the selection to Reserved Instance Purchase Report
4. In Reserved Instance Settings, select EC2
5. Test the connector
6. Save the connector

Setup the RDS reserved instance purchase connector

1. From the Connector list, select Copy from the Action menu for the Reserved Instances – EC2 connector.
2. Change the name to "Reserved Instances – RDS."
3. In Reserved Instance Settings, select RDS.
4. Test the connector.
5. Save the connector.

Setup the Trusted Advisor connector

1. From the Connector list, select Copy from the Action menu for the Reserved Instances – RDS connector.
2. Change the name to "Trusted Advisor."
3. In Trusted Advisor Settings, select Cost Optimizing and leave the other categories unchecked.
4. Test the connector.
5. Save the connector.

Run all the connectors

1. Run each connector, leaving time for each to finish before running the next one.

(Back to top)