IBM Watson AI Services Enabling IAM and Resource Groups

Share this post:

IBM Watson AI Services is enabling IAM and Resource Groups in US-South (Dallas) and EU-DE (Frankfurt) data centers

The IBM Watson Group is aligning with the larger IBM Cloud strategy for account organization and access control to service instances. This involves enabling Identity and Access Management (IAM) and Resource Groups in US-South (Dallas) and EU-DE (Frankfurt) data centers.

Key Dates:

  • October 30, 2018: Watson AI Services will enable IAM and Resource Groups in US-South (Dallas) and EU-DE (Frankfurt) data centers
  • October 30, 2019: Watson AI Services will deprecate Cloud Foundry in ALL data centers

 What are the implications?

  • Will this immediately impact my current service instances? No, Customers can continue using Cloud Foundry service instances, but any new instances must be created using IAM and Resource Groups.
  • What are the long-term impacts to my current services? All customers must migrate existing services to IAM prior to the deprecation of Cloud Foundry (October 30, 2019).
  • Will the migration cause downtime? No, the migration will be seamless and behind the scenes.
  • What does this mean for how I organized my account and the access permissions?
    • Cloud Foundry “Spaces” are not supported in Resource Groups. Instances within your account will have to be organized with naming conventions. For example: If you have Watson Assistant Premium instances in Spaces Dev, Test, Prod, you can rename those instances with the drop-down menu to the right of the instance to “Watson Assistant Premium – Dev,” etc.
    • Customers will need to create new IAM credentials to support the new instances within Resource Groups and apply them to designated instances. Existing Cloud Foundry credentials should be deleted.

Where can I find more information?

Offering Management - Watson Platform

More Watson stories
January 2, 2019

Chatbots Orchestration and Multilingual Challenges – Part 1

Chatbots Orchestration and Multilingual Challenges Nowadays, conversational bots are created to meet the needs for users. However, if users need to actively switch between languages and conversations, or maintain a large conversational bot, it is also a tedious and difficult task, and it often causes bad experience. We propose a multilingual chatbot architecture to expand […]

Continue reading

December 24, 2018

Chatbots Orchestration and Multilingual Challenges – Part 2

Chatbots Orchestration and Multilingual Challenges This post is the part 2 of “Chatbots Orchestration and Multilingual Challenges” post. Please check Chatbots Orchestration, if you haven’t. Part 2. Multilingual Chatbots Challenges There are some challenges when creating multilingual chatbots. A common practice is to use a baseline language chatbot then translate it to other languages chatbots. […]

Continue reading

December 11, 2018

Announcing the GA Version of Watson Compare & Comply

Watson Compare & Comply has gone GA! Extract data from governing documents and other complex unstructured documents to power business processes with Watson.

Continue reading