Update: 16-09-2024

Author: cldocid2

faqs/resource-groups-faq.md

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2020, 2023
-lastupdated: "2023-10-11"
+  years: 2020, 2023, 2024
+lastupdated: "2024-09-16"
 
 keywords: legacy access controls, api keys, enable iam, provisioning, how to choose between iam and legacy credentials, making requests, required client libraries, actions, endpoints, map actions to iam roles, manage credentials
 
@@ -76,8 +76,6 @@ Use only IAM
 When you use IAM roles other than `Manager`, such as `Reader`, `Writer`, `Monitor`, or `Checkpointer`, you **must** use *Use only IAM* to avoid supplying users with legacy credentials that include greater access permissions.
 {: important}
 
-{{site.data.keyword.cloudant_short_notm}} service instances that are provisioned previously in a Cloud Foundry org and space can be migrated to a Resource Group. After you migrate to a Resource Group, the instance is enabled with {{site.data.keyword.cloud_notm}} IAM. For more information, see the [Resource Groups FAQ](/docs/Cloudant?topic=Cloudant-faq-ibm-cloud-resource-groups) about how to migrate.
-
 ### {{site.data.keyword.cloudant_short_notm}} API keys and _Use only IAM_
 {: #ibm-cloudant-api-keys-and-use-only-iam_ai}
 
@@ -428,7 +426,7 @@ See the results in the following example:
 
 {{site.data.keyword.cloud_notm}} IAM is the recommended authentication model. For security purposes, you can request to remove the {{site.data.keyword.cloudant_short_notm}} legacy credentials so that only IAM authentication can be used for the instance. The correct process to remove legacy credentials is shown in the following steps:
 
-1. Ensure that the {{site.data.keyword.cloudant_short_notm}} instance has IAM authentication that is enabled. If the instance is deployed in a Cloud Foundry org and space, migrate it to a Resource Group by using the [Resource Groups FAQ](/docs/Cloudant?topic=Cloudant-faq-ibm-cloud-resource-groups).
+1. Ensure that the {{site.data.keyword.cloudant_short_notm}} instance has IAM authentication that is enabled.
 
 2. Update your application to use IAM authentication instead of {{site.data.keyword.cloudant_short_notm}} legacy authentication.
 

security/access-iam.md

@@ -218,7 +218,6 @@ toc:
           - faqs/model-data-faq.md
           - faqs/pricing-faq.md
           - faqs/provisioned-throughput-capacity-faq.md
-          - faqs/resource-groups-faq.md
           - faqs/changes-feed-faq.md
           - faqs/cloudant-query-faq.md
       - get-help.md

toc.yaml

@@ -1,8 +1,8 @@
 ---
 
 copyright:
-  years: 2017, 2023
-lastupdated: "2023-03-30"
+  years: 2017, 2023, 2024
+lastupdated: "2024-09-16"
 
 keywords: identify, api endpoints, log in, select ibm cloudant plan, create ibm cloudant service, create credentials, list service credentials, use ibm cloudant service instance, delete service credentials, delete service instance
 
@@ -106,7 +106,7 @@ The following example describes how to log in. If you use a federated user ID, i
 {: #creating-service-create-cli}
 {: step}
 
-{{site.data.keyword.cloudant_short_notm}} uses resource groups for provisioning new instances. For more information, see the [Resource Groups FAQ](/docs/Cloudant?topic=Cloudant-faq-ibm-cloud-resource-groups){: external}.
+{{site.data.keyword.cloudant_short_notm}} uses resource groups for provisioning new instances.
 
 In this example, you create a service instance within {{site.data.keyword.cloud_notm}} by running the following command.
 
@@ -304,8 +304,3 @@ Delete the `cs20170517a` instance of an {{site.data.keyword.cloudant_short_notm}
 ibmcloud resource service-instance-delete cs20170517a
 ```
 {: pre}
-
-
-
-
-