AWS Services Mapping

Hi ~ yes, I'm all set.  It says published on April 23, but the zip file stated v2.19.  I received notification from this page that it was updated evening of April 24 and I loaded it yesterday.  Thank you for checking!

Hmm, v2.20 was published on Apr 23rd. Can you recheck which version you see available to download?

I see "AWS_ATUM_Mappings-Apr2020.zip" and downloaded/unzipped to get "AWSServiceMappingv2_20.csv".

Let me know if you're still not getting the April update.

Thanks!

Appears the zip file is still January's v2.19, when will v2.20 be available?

Hey when is the next update to this file expected?

Apologies for missing a notification in this thread... ATUM 3.0 is available.  Please see this What's New post for more information: https://tbmcouncil.jiveon.com/docs/DOC-11662

@Randall Tennant any update as to when we can see an update for v3 service mapping?

Been a while since the last update.  Any news on delivery of the ATUM 3.0 mapping? Thanks!

Now that it's April 2nd, I can safely respond to Matt's comment... we are still planning to release support for cloud services mappings to ATUM v2.1 and 3.0 very soon.  We're currently integration testing and aim to release in the next couple of weeks.  Standby for more details.

It would have been so funny to see ATUM v3 included in the April 1 update with a single entry saying, "April Fools!" 

I just created a fresh Public Cloud project. Naturally, I'm now more eager to get my hands on the 3.0 services mapping. 

Hi John... v1.22 should have a large number of new services and new pricing schemes that AWS has introduced since the last update.

Hi Amanda... there are no plans to add the Services Hierarchy to ATUM v1.  That hierarchy was created as a part of ATUM v2.0 and, while we'll continue to update that hierarchy moving forward (as we have with v2.1 and 3.0 of ATUM), we do not plan to include it as part of v1.

Hey Matt... support for ATUM 3.0 is slotted to be available at the end of this month (end of Q1).

Looks like support for 3.0 will arrive EOQ1 or EOQ2.

Call me #eager! ;-)

Randy, @Randall Tennant

I am not sure why v1.22 has been marked as new when this was loaded last year. Have you made corrections or was a new version meant to be loaded, as I can't see any obvious differences to the v1.22 loaded last year and this update.

Thanks,

John Feore

@Brett Yates @Randall Tennant

Will the Platform, Service Type, Service Category and Service Name columns be added to the ATUM 1 version? Currently the out of the box logic does not work without them. @Randall Tennant @Andrew Lee

When will the mapping reflect TBMv3 taxonomy?

Thanks, Ankur... we will fix the problem and repost the mapping file.

@Randall Tennant I saw some typo for the word Containers. In the Service Mapping file in column "Type" , There are values with 1) Containeers and 2) Containers. I believe Containers is the correct value for AWS Type of Service in this column . Please check and update this in the Service Mapping file.

Will updates for ATUM v3 be published soon?

good information on this page. Thank you

TBM Connect keeps removing the word  in front of Storage

Randy - 

Can you fix the sub-towers you have listed in the V1 files?   With ATUM v1 there are no such sub-towers called "Security" or " Storage".    I had to put logic in Apptio to change those but would prefer to clean up the mapping file. 

- Craig

I take the following approach to lookup detail from the service mapping table:

1. In the "Cloud Service Provider Lookup" table I ensure the following fields are present with the following formulas:
   Lookup = Item && Procedure && ProductCode
   Lookup Alt = Item && Procedure
   
   Return Value = Tower & "|" & SubTower & "|" & If(Instance Type="","NA",Instance Type) & "|" & Type & "|" & Unit
   
   
2. In the "AWS Cost Allocation Bill Master Data" table...
   
   Instance Type Details Step 1 = Lookup(Lookup,Cloud Service Provider Lookup,Lookup,Return Value)
   Instance Type Details Step 2 = Lookup(Lookup Alt,Cloud Service Provider Lookup,Lookup Alt,Return Value)

Then, I analyze which of the Details returned (eg Step 1 vs Step 2) I want to use for values. For example...

Instance Type = If(Instance Type Details Step 1 IN ("","{Various}"),Split(Instance Type Details Step 2,3,"|"),Split(Instance Type Details Step 1,3,"|"))

Since I'm returning Tower, SubTower, Type, and Unit in the Return Value they, too, can be parsed to populate into the AWS (or Azure) tables appropriately.

I hope this helps other colleagues on their journey. :-)

I identified 175+ additions needed for the service mapping. I submitted ticket 117881 to Support for your Apptio's review and subsequent update to this mapping. :-)

Thank you, Dariusz... we have identified the issue of blank rows in the AWS Services Maping file and are currently fixing the issue.  We will publish a new version very soon, targeting the end of this week.

I have noticed that the Sept 8th 2017 AWS Services Mapping has rows missing tower/sub-tower.  Does anyone know when the next update will be?

Yes... the AWS mapping file was posted yesterday.  Please note that, for AWS, we have started posting an ATUM 2.0 mapping file as well - it includes updated mappings based on changes to IT Resource Towers and Subtowers as well as new ATUM Service Hierarchy attributes.  For more information on ATUM 1.0 vs. ATUM 2.0, please refer to the ATUM Knowledge Base on Community (ATUM Knowledge Base ).

Thanks!

-Randy

Hi Randall, is the mapping for AWS already released this quarter? Thank you

ATUM 2.0 services mapping for AWS will be released this quarter.  If you would like a preview of the AWS mapping, please respond to rtennant@apptio.com directly.  Thanks!

@Randall Tennant is there a 2.0 for this one, too?

Is there a mapping file reflective of ATUM v2?