vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To create an access group by using the CLI, you can use the [ibmcloud iam access-group-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_access_group_policy_create) command.

ibmcloud iam access-group-create GROUP_NAME [-d, --description DESCRIPTION]





 Step 2. Add permissions to manage events 

After you set up your group, you can assign a common access policy to the group.

Any policy that you set for an access group applies to all entities, users and service IDs, within the group.

You can assign the policy by using the UI or through the command line.

To create an access group policy by using the CLI, you can use the [ibmcloud iam access-group-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_access_group_policy_create) command.

ibmcloud iam access-group-policy-create GROUP_NAME {-f, --file @JSON_FILE | --roles ROLE_NAME1,ROLE_NAME2... [--service-name SERVICE_NAME] [--service-instance SERVICE_INSTANCE] [--region REGION] [--resource-type RESOURCE_TYPE] [--resource RESOURCE] [--resource-group-name RESOURCE_GROUP_NAME] [--resource-group-id RESOURCE_GROUP_ID]}

When you define the policy, you need to select a platform role and a service role:



* Platform management roles cover a range of actions, including the ability to create and delete instances, manage aliases, bindings, and credentials, and manage access. The platform roles are administrator, editor, operator, viewer. Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance.
ibmcloud iam access-group-create GROUP_NAME [-d, --description DESCRIPTION]





 Step 2. Add permissions to view events 

After you set up your group, you can assign a common access policy to the group.

Any policy that you set for an access group applies to all entities, users and service IDs, within the group.

You can assign the policy by using the UI or through the command line.

To create an access group policy by using the CLI, you can use the [ibmcloud iam access-group-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_access_group_policy_create) command.

ibmcloud iam access-group-policy-create GROUP_NAME {-f, --file @JSON_FILE | --roles ROLE_NAME1,ROLE_NAME2... [--service-name SERVICE_NAME] [--service-instance SERVICE_INSTANCE] [--region REGION] [--resource-type RESOURCE_TYPE] [--resource RESOURCE] [--resource-group-name RESOURCE_GROUP_NAME] [--resource-group-id RESOURCE_GROUP_ID]}

When you define the policy, you need to select a platform role and a service role:



* Platform management roles cover a range of actions, including the ability to create and delete instances, manage aliases, bindings, and credentials, and manage access. The platform roles are administrator, editor, operator, viewer. Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Log Analysis service, a user needs the following roles:



* Platform role: Viewer.
* Service role: Reader.
ibmcloud iam access-group-create GROUP_NAME [-d, --description DESCRIPTION]





 Step 2. Add permissions to view events 

After you set up your group, you can assign a common access policy to the group.

Any policy that you set for an access group applies to all entities, users and service IDs, within the group.

You can assign the policy by using the UI or through the command line.

To create an access group policy by using the CLI, you can use the [ibmcloud iam access-group-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_access_group_policy_create) command.

ibmcloud iam access-group-policy-create GROUP_NAME {-f, --file @JSON_FILE | --roles ROLE_NAME1,ROLE_NAME2... [--service-name SERVICE_NAME] [--service-instance SERVICE_INSTANCE] [--region REGION] [--resource-type RESOURCE_TYPE] [--resource RESOURCE] [--resource-group-name RESOURCE_GROUP_NAME] [--resource-group-id RESOURCE_GROUP_ID]}

When you define the policy, you need to select a platform role and a service role:



* Platform management roles cover a range of actions, including the ability to create and delete instances, manage aliases, bindings, and credentials, and manage access. The platform roles are administrator, editor, operator, viewer. Platform management roles also apply to account management services that enable users to invite users, manage service IDs, access policies, catalog entries, and track billing and usage depending on their assigned role on an account management service.
* Service access roles define a user or service’s ability to perform actions on a service instance. The service access roles are manager, writer, and reader.



To manage the IBM Cloud Activity Tracker service, a user needs the following roles:



* Platform role: Viewer.
* Service role: Reader.
* Pod Rightsizing & Workload Capacity Optimization
* Workload Status & Performance
* Deployment Overview
* Pod Overview
* Workloads CPU Usage and Allocation
* Workloads Memory Usage and Allocation



For more information on how to interpret this view, see [About Workloads Overview](https://docs.sysdig.com/en/docs/sysdig-monitor/advisor/overview/workloads-data/).





 Monitoring hosts 

When you choose to monitor by host, you can choose any of the following dashboards:



* Host Resource Usage
* File System Usage & Performance
* Memory Usage
* Network
* Sysdig Agent Health & Status









 Dashboards 

A dashboard is composed of a series of panels that are configured to display metrics that report on the health, performance, and state of your infrastructure, applications, and services for a single host or a group of hosts. Dashboards offer a specialized insight into network data, application data, topology, services, hosts, and containers. Use dashboards to monitor your infrastructure, applications, and services.

In the Dashboards section of the web UI, dashboards are organized in the following sections:



* My favorites: These section displays the top dashboards.
* My Dashboards: These section displays custom dashboards that you create.
* Shared By My Team: These dashboards displays custom dashboards that are shared by users within a team.
* Dashboard Templates: These section groups predefined dashboards by type. Predefined dashboards that are provided by IBM Cloud services are located in the IBM section.



You can use pre-defined dashboards. You can also create custom dashboards through the web UI or programmatically. You can back up and restore dashboards by using Python scripts or the IBM Cloud Monitoring REST API. You can also copy and share dashboards through the web UI.

For more information, see [Dashboards](https://docs.sysdig.com/en/docs/sysdig-monitor/dashboards/).





 Panels 

A panel displays a metric or group of metrics in a dashboard.

You can use any of the following panel types to visualize metrics:
You can configure access to Cloudant by manually injecting environment variables, but the typical process is through [service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-binding). The relationship between the app and its backing services is explicitly stated, so credentials are created and automatically injected into the runtime environment. Cloud Foundry provides the credentials as part of the VCAP_SERVICES object. Code Engine mimics this object through its [CE_SERVICES](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-bindingce-services) environment variable.

Both the Cloud Foundry and the Code Engine applications attach to the database service. The code deployed to Code Engine can be considered a different, newer version of the Cloud Foundry app. It continues to be bound to the same database service, but through other means.

To bind the Code Engine version of the app to a service,



1. Access your [Cloudant database instance](https://cloud.ibm.com/catalog/services/cloudant). If you do not have one, create one.
2. Create service credentials (IAM service key) for your Cloudant instance with a descriptive name. Specify the IAM role (Manager, Writer, or Reader) for your app. Pick a role with the least level of privilege required for your application.
3. Bind the service to the app by using the existing credential. Code Engine can create credentials for you when you bind a service. However, by creating your own credential, you can track and even change the privilege independently of Code Engine.



For this sample app with Cloudant as the database service, run the following commands to create the service key Cloudant-CF2CE-Manager with the Manager role and then use it to bind the service.

ibmcloud resource service-key-create Cloudant-CF2CE-Manager Manager --instance-name Cloudant-CF2CE

ibmcloud ce app bind --name cf2ce-app --service-instance Cloudant-CF2CE --service-credential Cloudant-CF2CE-Manager
[Why can't my PVC access an existing bucket?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_access_bucket_failscos_access_bucket_fails)

[Why does installing the Object storage Helm plug-in fail?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_helm_failscos_helm_fails)

[Why can't non-root users access files?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_nonroot_accesscos_nonroot_access)



* [Verifying that the permissions for your files are updated](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_nonroot_accessverifying_file_permission_update)



[Why does my app pod fail with an Operation not permitted error?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_operation_not_permittedcos_operation_not_permitted)

[Why can't the ownership of the mount path be changed?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_mountpath_errorcos_mountpath_error)

[Why does installing the IBM Cloud Object Storage plug-in fail?](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_failscos_plugin_fails)

[Why do I see wrong credentials or access denied messages when I create a PVC?](https://cloud.ibm.com/docs/openshift?topic=openshift-cred_failurecred_failure)

[Why do I see wrong s3fs or IAM API endpoints when I create a PVC?]
You must have an existing IAM ID of an enterprise primary contact in order to complete the task.

resource "ibm_enterprise" "enterprise" {
source_account_id = <source_account_id>
name = <name>
primary_contact_iam_id = <primary_contact_iam_id>
}

You can specify the ID of an account that is used to create the enterprise on the source_account_id option. For more information, see the argument reference details on the [Terraform Enterprise Management](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/enterprise) page.
2. After you finish building your configuration file, initialize the Terraform CLI. For more information, see [Initializing Working Directories](https://www.terraform.io/cli/init).

terraform init
3. Provision the resources from the main.tf file. For more information, see [Provisioning Infrastructure with Terraform](https://www.terraform.io/cli/run).



1. Run terraform plan to generate a Terraform execution plan to preview the proposed actions.

terraform plan
2. Run terraform apply to create the resources that are defined in the plan.

terraform apply









 Next steps 

Build out your enterprise structure by adding more existing accounts or creating new accounts within your enterprise. For more information, see [Adding accounts to your enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-enterprise-add).

You can also invite additional users to the enterprise account so that they can help manage the enterprise. For example, you might want to invite a financial officer to manage billing and track usage costs, and invite department leads to administer accounts. See [Inviting users](https://cloud.ibm.com/docs/account?topic=account-iamuserinv) for more information about how to invite users.
as a literal value by enclosing each within two sets of curly brackets {{}}. 







 Step 7: Set the license requirements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement. Or, if users can bring their own licenses, you can provide that URL as well.



1. Click Add license agreements > Add.
2. Enter the name and URL, and click Update.
3. Click Next.







 Step 8: Review your readme file 

The TGZ file that you imported to your private catalog includes a readme file that provides product information for the virtual server image. If you want to make updates to the readme file, you can edit it directly from your private catalog. For the purposes of this tutorial, the following steps describe how to edit the description of the readme file.



1. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg), and update the description with the following sentence:

Create and deploy a virtual server with ease by using a custom image.
2. Click Save > Next.







 Step 9: Validate the virtual server image 



1. From the Validate product tab, enter the name of your Schematics workspace, select a resource group, select a Schematics region, and click Next.

In the Tags field, you can enter a name of a specific tag to attach to your virtual server image. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
2. From the Deployment values section, review your parameter values, and click Next.
3. In the Validation product section, select I have read and agree to the following license agreements.
4. Click Validate.

To monitor the progress of the validation process, click View logs.







 Step 10: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements.
IBM Cloud services that generate events that are managed through Activity Tracker hosted event search 

List of IBM Cloud® services that generate auditing events in an IBM Cloud account that you can only manage through Activity Tracker hosted event search instances.

Activity Tracker hosted event search routes location-based auditing events to an Activity Tracker hosted event search instance in the region where they are generated and routes global auditing events to the Activity Tracker instance that is provisioned in Frankfurt. Some exceptions may apply, see [IBM Cloud services that generate Activity Tracker events by location](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-cloud_services_locations).



 Analytics services 

The following table lists analytics services that send auditing events:



Table 1. List of analytics services

 Service CRN service name Events 

 [IBM® Analytics Engine](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-getting-started) ibmanalyticsengine [Location-based events](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-at_events-serverless) 
 [IBM Cloud® Data Engine](https://cloud.ibm.com/docs/sql-query?topic=sql-query-overviewoverview) sql-query [Location-based events](https://cloud.ibm.com/docs/sql-query?topic=sql-query-activitytrackeractivitytracker) 
 [Watson Query](https://cloud.ibm.com/docs/data-virtualization?topic=data-virtualization-getting-started) data-virtualization [Location-based events](https://cloud.ibm.com/docs/data-virtualization?topic=data-virtualization-activity-tracker) 







 Compute serverless services 

The following table lists serverless compute services that send auditing events:



Table 2. List of serverless compute services

 Service CRN service name Events
IBM Analytics Engine CLI plug-in for serverless instances 

The IBM Analytics Engine v3 CLI provides command line options to interact with Standard Serverless Spark instances. You can manage instances and Spark applications with the CLI. For more information about serverless Analytics Engine instances, see [Architecture and concepts in serverless instances](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-serverless-architecture-concepts).

To run IBM Analytics Engine v3 CLI commands, use ibmcloud analytics-engine-v3 or ibmcloud ae-v3.



 Prerequisites 

Download and install the IBM Cloud CLI on your local system. See [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cloud-cli-install-ibmcloud-cli) to install the CLI.





 Install the IBM Analytics Engine v3 CLI 

Install the IBM Analytics Engine v3 CLI by running the following command:

ibmcloud plugin install analytics-engine-v3

The following help CLI command shows that the v3 CLI supports CLI commands for:



* [Setting a target instance](https://cloud.ibm.com/docs/analytics-engine-cli-plugin?topic=analytics-engine-cli-plugin-CLI_analytics_engineanalytics-engine-v3-target-cli)
* [Instance management](https://cloud.ibm.com/docs/analytics-engine-cli-plugin?topic=analytics-engine-cli-plugin-CLI_analytics_engineanalytics-engine-v3-instance-cli)
* [Spark application management](https://cloud.ibm.com/docs/analytics-engine-cli-plugin?topic=analytics-engine-cli-plugin-CLI_analytics_engineanalytics-engine-v3-spark-app-cli)
IBM Analytics Engine CLI plug-in for serverless instances 

The IBM Analytics Engine v3 CLI provides command line options to interact with Standard Serverless Spark instances. You can manage instances and Spark applications with the CLI. For more information about serverless Analytics Engine instances, see [Architecture and concepts in serverless instances](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-serverless-architecture-concepts).

To run IBM Analytics Engine v3 CLI commands, use ibmcloud analytics-engine-v3 or ibmcloud ae-v3.



 Prerequisites 

Download and install the IBM Cloud CLI on your local system. See [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cloud-cli-install-ibmcloud-cli) to install the CLI.





 Install the IBM Analytics Engine v3 CLI 

Install the IBM Analytics Engine v3 CLI by running the following command:

ibmcloud plugin install analytics-engine-v3

The following help CLI command shows that the v3 CLI supports CLI commands for:



* [Setting a target instance](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-CLI_analytics_engineanalytics-engine-v3-target-cli)
* [Instance management](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-CLI_analytics_engineanalytics-engine-v3-instance-cli)
* [Spark application management](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-CLI_analytics_engineanalytics-engine-v3-spark-app-cli)
* [Log forwarding configuration](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-CLI_analytics_engineanalytics-engine-v3-log-forwarding-config-cli)
IBM Analytics Engine CLI plug-in for serverless instances 

The IBM Analytics Engine v3 CLI provides command line options to interact with Standard Serverless Spark instances. You can manage instances and Spark applications with the CLI. For more information about serverless Analytics Engine instances, see [Architecture and concepts in serverless instances](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-serverless-architecture-concepts).

To run IBM Analytics Engine v3 CLI commands, use ibmcloud analytics-engine-v3 or ibmcloud ae-v3.



 Prerequisites 

Download and install the IBM Cloud CLI on your local system. See [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cloud-cli-install-ibmcloud-cli) to install the CLI.





 Install the IBM Analytics Engine v3 CLI 

Install the IBM Analytics Engine v3 CLI by running the following command:

ibmcloud plugin install analytics-engine-v3

The following help CLI command shows that the v3 CLI supports CLI commands for:



* [Setting a target instance](https://cloud.ibm.com/docs/cli?topic=cli-CLI_analytics_engineanalytics-engine-v3-target-cli)
* [Instance management](https://cloud.ibm.com/docs/cli?topic=cli-CLI_analytics_engineanalytics-engine-v3-instance-cli)
* [Spark application management](https://cloud.ibm.com/docs/cli?topic=cli-CLI_analytics_engineanalytics-engine-v3-spark-app-cli)
* [Log forwarding configuration](https://cloud.ibm.com/docs/cli?topic=cli-CLI_analytics_engineanalytics-engine-v3-log-forwarding-config-cli)
Services generating metrics by location 

List of locations where IBM Cloud services are enabled to send metrics to IBM Cloud Monitoring. You monitor these metrics through the monitoring instance that is configured to receive platform metrics. [Learn more about enabling platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).



 Compute services 



 Serverless 

Europe

America

Asia Pacific



Serverless integration in Europe locations

 Service Frankfurt (eu-de) London (eu-gb) 

 IBM Cloud Code Engine ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 IBM Cloud® Functions ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 







 VPC 

Europe

America

Asia Pacific



Infrastructure services integration in Europe locations

 Service Frankfurt (eu-de) London (eu-gb) 

 VPC virtual server instances ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) !
IBM Cloud services that generate events that are managed through Activity Tracker Event Routing 

List of IBM Cloud® services that generate auditing events that you can manage through IBM Cloud Activity Tracker Event Routing.

Activity Tracker Event Routing routes events based on the location that is specified in the logSourceCRN field included in the event. You can define a target, the resource where events are routed to, in any Activity Tracker Event Routing supported region. However, the target resource can be located in any region where that type of target is supported, in the same account or in a different account. You can define rules to determine where auditing events are to be routed by configuring 1 or more routes in the account. You can define rules for managing global events and location-based events that are generated in regions where Activity Tracker Event Routing is supported.



 Classic services 

The following table lists services that send auditing events:



Table 1. List of classic services

 Service CRN service name Events 

 [IBM Cloud® Virtual Servers (Classic)](https://cloud.ibm.com/docs/vsi?topic=virtual-servers-about-virtual-serversabout-virtual-servers) audit-log [Location-based events](https://cloud.ibm.com/docs/vsi?topic=virtual-servers-at_eventsat_events) 
 [IBM Cloud® Bare Metal Servers (Classic)](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-about-bmabout-bm) audit-log [Location-based events](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-at-eventsbm-at-events) 







 Compute serverless services 

The following table lists serverless compute services that send auditing events:



Table 2. List of serverless compute services

 Service CRN service name Events