vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing multiple accounts with your IBMid 

As the owner or administrator of an IBM Cloud® account, you can create and manage multiple accounts that are associated with a single IBMid to access and manage details about each account from one email address. For example, you might be responsible for managing several departments in your company that have different billing requirements. By creating multiple accounts, you can switch between them without having to log in and out of the IBM Cloud console each time.

Only Pay-As-You-Go and Subscription accounts can create multiple accounts by using one email. Lite accounts can create only one account per email.

Managing multiple accounts with a single IBMid is different from using an enterprise account. With an enterprise account, you can have several child accounts attached to a parent account, and all associated charges roll up to the parent account in the enterprise. See [What is an enterprise?](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-what-is-enterprise) for more information.

To create multiple accounts associated with your IBMid, complete the following steps:



1.  In the console, go to the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Log out, and click Log out.
2.  From the login screen, click Create an account.
3.  From the registration page, enter your email address, complete the necessary information, and click Create account.



After you create the accounts, you can switch to a specific account from the console menu bar as shown in the following image.

Zoom

![A screen capture of the account selector in the console menu bar. The account selector displays the account name and account number, and you select the current account to display a list of other accounts that you can access.](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/account-faq.svg)

Figure 1. Using the account selector to switch accounts
Identity and access management (IAM) on IBM Cloud 

Identity and access management (IAM) enables you to securely authenticate users for platform services and control access to resources consistently across the IBM Cloud platform. For example, with only a single login to IBM Cloud with your IBMid, you have access to any of your service consoles and their applications without having to log in to each of them separately.

IAM is enabled for all Db2 on Cloud plans except for Lite plan instances.



 Features of IBM Cloud IAM 

The following IAM features are implemented for the Db2 on Cloud managed service with two types of supported identities:



 IBMid 

Users with an IBMid must be added to each database service instance by the database administrator through the console or REST API before these users can connect to the particular database service instance. Just like for a non-IBMid user, a user ID for the database service instance must be entered at the same time that the IBMid user is added. This user ID needs to be unique within the database service instance. This user ID is also the authorization (AUTH) ID within the database. The database administrator can grant and revoke permissions based on the AUTH ID.





 Service IDs 

A service ID identifies a service or application similar to how a user ID identifies a user. The service IDs are IDs that can be used by applications to authenticate with an IBM Cloud service. A service ID represents a separate entity from the owning IBMid. Therefore, different authorities and permissions can be granted specific to the service ID within the database. Service IDs do not have passwords. An API key must be created for each service ID for the service ID to connect to the database service instance. For more information about service IDs, see: [Introducing IBM Cloud IAM Service IDs and API Keys](https://www.ibm.com/blogs/bluemix/2017/10/introducing-ibm-cloud-iam-service-ids-api-keys/) and [Increase Information Security for Db2 on IBM Cloud](https://www.ibm.com/cloud/blog/increase-information-security-for-db2-on-ibm-cloud).







 Roles and actions
If you have a Lite account, you can have only one resource group, but with a a Pay-As-You-Go or Subscription account, you can create more than one resource group. If an account is suspended, the corresponding resource group is suspended as well, and all resources within the resource group are suspended.





 Managing Infrastructure as Code (IaC) deployments with projects 

IBM Cloud

projectsare a named collection of configurations that are used to manage related resources and Infrastructure as Code (IaC) deployments across accounts. They enable teams to configure, deploy, and monitor deployments by using DevOps best practices. If you select a deployable architecture from the catalog, you can add it to a project to configure and deploy it into your different environments. For more information, see [Learn about IaC deployments with projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects).





 Searching and tagging resources 

The search service is a global and shared resource properties repository that is integrated within the IBM Cloud platform. It is used for storing and searching a cloud resource's attributes, and it categorizes and classifies resources. Resources are uniquely identified by a [Cloud Resource Name (CRN)](https://cloud.ibm.com/docs/account?topic=account-crn) identifier. The properties of a resource include tags and system properties. Both properties are defined within an IBM Cloud billing account, and span across many regions.

This service also manages tags that are associated with a resource. You can create, delete, search, attach, or detach tags with the Tagging API. Tags are uniquely identified by a CRN identifier. Tags have a name, which must be unique within a billing account. You can create tags in key:value pairs or label format.





 Monitoring your resources 

Observability offers a single location where you can monitor and observe your applications and services in IBM Cloud.

With the IBM® Log Analysis service, you can add log management capabilities to your IBM Cloud architecture and you can manage system and application logs.
With IBM Cloud App ID, you can take cloud security one step further by adding authentication into your web and mobile apps. With just a few lines of code, you can easily secure your Cloud-native apps and services that run on IBM Cloud. Ready to get started? [Check out the docs](https://cloud.ibm.com/docs/services/appid?topic=appid-getting-startedgetting-started).
* Where do I manage a user's access to infrastructure?

Access for classic infrastructure starts with the user. For more information, see [Managing classic infrastructure access](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra).

If you need to assign access to IAM-enabled infrastructure services, such as IBM Cloud® Virtual Private Cloud, you assign access to a user by completing the following steps:



1. Click Manage > Access (IAM) > Users
2. Select the user.
3. Click Access.



* How do I manage access for users previously assigned billing and support permissions in my SoftLayer account?

All permissions that were previously assigned in your SoftLayer account can be managed in the IBM Cloud console. Account permissions for managing billing information and support cases are now available in [managing migrated SoftLayer account permissions](https://cloud.ibm.com/docs/account?topic=account-migrated_permissions). All users who were previously assigned these permissions in your SoftLayer account were migrated to these access groups, which are assigned the same level of access by using an IAM policy on the access group.
* How do I determine how many policies exist in my account?

You can [check the number of policies in an account](https://cloud.ibm.com/docs/account?topic=account-policy-limits) by using the CLI to ensure that you don't exceed the limit for your account.
* What are verification methods and what they are used for?

Verification methods are used to prove your identity and access the Verification methods and authentication factors page.
With IBM Cloud App ID, you can take cloud security one step further by adding authentication into your web and mobile apps. With just a few lines of code, you can easily secure your Cloud-native apps and services that run on IBM Cloud. Ready to get started? [Check out the docs](https://cloud.ibm.com/docs/services/appid?topic=appid-getting-startedgetting-started).





 Where do I manage a user's access to infrastructure? 

Access for classic infrastructure starts with the user. For more information, see [Managing classic infrastructure access](https://cloud.ibm.com/docs/account?topic=account-mngclassicinfra).

If you need to assign access to IAM-enabled infrastructure services, such as IBM Cloud® Virtual Private Cloud, you assign access to a user by completing the following steps:



1. Click Manage > Access (IAM) > Users
2. Select the user.
3. Click Access.







 How do I manage access for users previously assigned billing and support permissions in my SoftLayer account? 

All permissions that were previously assigned in your SoftLayer account can be managed in the IBM Cloud console. Account permissions for managing billing information and support cases are now available in [managing migrated SoftLayer account permissions](https://cloud.ibm.com/docs/account?topic=account-migrated_permissions). All users who were previously assigned these permissions in your SoftLayer account were migrated to these access groups, which are assigned the same level of access by using an IAM policy on the access group.





 How do I determine how many policies exist in my account? 

You can [check the number of policies in an account](https://cloud.ibm.com/docs/account?topic=account-policy-limits) by using the CLI to ensure that you don't exceed the limit for your account.





 What are verification methods and what they are used for? 

Verification methods are used to prove your identity and access the Verification methods and authentication factors page.
Volume Worker n/a n/a <br><br> * 1 IBM Cloud Databases for Redis with 2G RAM 4G of storage<br> * IBM Cloud Functions instance<br> * 1 Cloud Object Storage bucket<br><br><br> 



Lite is for testing and proof of concept, not production.

Citrix DaaS for IBM Cloud solutions on VPC do not require extra configuration for monitoring, storage, networking, or high availability.

All of the servers and virtual desktops are provisioned in the IBM® private network.

More technical information is available in the [readme file](https://github.com/IBM-Cloud/citrix-virtual-apps-and-desktopsreadme).





 Before you begin 

You can provision Citrix DaaS for IBM Cloud through the IBM Cloud catalog and then manage the workloads through the Citrix Cloud Management console.

Before you begin, review the following prerequisites.



1. Review and complete the prerequisites found in [Getting started with Citrix DaaS for IBM Cloud](https://cloud.ibm.com/docs/citrix-daas?topic=citrix-daas-getting-started-tutorial).
2. You must have either an active trial or paid subscription to Citrix Cloud. To learn more or to create an account, see [Citrix Cloud](https://onboarding.cloud.com/).
3. You must have a Citrix API client and password pair. Download the client ID and Secret. For more information about creating the key pair, see [Create an API client](https://developer.cloud.com/getting-started)
4. Log in to the [IBM Cloud catalog](https://cloud.ibm.com/catalog) by using your unique credentials.



1. Create an IBM Cloud [API key](https://cloud.ibm.com/iam/apikeys) in the IAM dashboard before you create an order. Retrieve and verify your credentials before proceeding.
2. In the Compute section, locate the Citrix Digital Workspace Solutions section and select Citrix DaaS.



5.
* UI
* CLI
* API
* Terraform







 Adding accounts to an enterprise 

You can build out your enterprise by adding more IBM Cloud® accounts to it. To add accounts, you can import existing accounts that aren't in another enterprise, or you can create new accounts within your enterprise.

After your enterprise has multiple accounts, you can organize related accounts by using account groups. For more information, see in [Organizing accounts in an enterprise](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-enterprise-organize).



 Importing existing accounts 

You can import existing accounts into an enterprise. After you import an account, it can't be removed, and each account can be a part of only one enterprise. If you import a Lite or trial account, it's automatically upgraded to a [Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-accounts).

Importing an account to the enterprise has the following impacts:



* Billing for the account transitions to being managed by the enterprise. After the transition, users in the account can't access billing and payment information, such as invoices, payments, or subscriptions, for future billing periods. To view or manage billing, users need to be invited to the enterprise account and be given access to the Billing service in that account. See [Centrally manage billing and usage with enterprises](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise) for more information.
* Users and access permissions within the account are not changed. Access within the account is separate from the enterprise, and users don't automatically get access within the enterprise when the account is imported.
* Resources within the account are not changed. Users with the correct access permissions can continue to view usage information for resources in the account.



To import existing accounts into an enterprise, the following access is required:



* Within the account to be imported, you must be the account owner or have the Administrator role on the Billing service within the account.
If you have a Lite account or 30-day trial, you can't create extra resource groups, but you can rename your default resource group.





 Creating a resource group in the console 



1. In the IBM Cloud console, go to Manage > Account > Account resources > Resource groups.
2. Click Create.
3. Enter a name for your resource group.
4. Click Create.







 Creating a resource group by using the CLI 

You can create and rename a resource group, or view a resource in one by using the IBM Cloud® Command Line Interface. For detailed information about working with resources, see [Working with resources and resource groups](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resource).



1. Log in, and select the account.

ibmcloud login
2. Create a new resource group by running [ibmcloud resource group-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_group_create) command. For example, the following command creates a resource group that is named group2:



ibmcloud resource group-create group2





 Creating a resource group by using the API 

If you have a Pay-As-You-Go or Subscription account, you can create multiple resource groups to easily manage quota and view billing usage for a set of resources. You can also group resources to make it easier for you to assign users access to more than one instance at a time.

You must be assigned an IAM policy with the Administrator role on All Account Management services to create additional resource groups. If you have a Lite account or 30-day trial, you can't create extra resource groups, but you can rename your default resource group.

To create a resource group, call the [IBM Cloud® Resource Manager API](https://cloud.ibm.com/apidocs/resource-controller/resource-manager?code=gocreate-resource-group) as shown in the following example:



* Curl
* Java
* Python
* Go
* Node
* IBMid account. This account is required to access the IBM Cloud for VMware Solutions console. The console is a stand-alone user interface that is separate from the IBM Cloud infrastructure customer portal. For more information, see [Getting started](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-getting-started).
* IBM Cloud account. This account is required for provisioning. You can sign up for an IBM Cloud account by using an existing IBMid or by creating a new IBMid.
* IBM Cloud infrastructure account. This account is used to log in to the IBM Cloud infrastructure customer portal that provides some additional function to manage infrastructure products and services. You can get an IBM Cloud infrastructure account by upgrading your IBM Cloud account to a billable account, or by linking your existing IBM Cloud infrastructure account with your IBM Cloud account. The IBM Cloud infrastructure account that you are using must meet certain requirements. For more information, see [Signing up for required accounts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accounts).







 How do I associate my IBM Cloud infrastructure credentials with the VMware Solutions console? 

When you order your instance for the first time, follow the instructions on the Settings page in the console. These instructions help you locate and copy the IBM Cloud infrastructure username and API key from the IBM Cloud infrastructure customer portal. The IBM Cloud infrastructure credentials are stored in the IBM Cloud for VMware Solutions console after the first order. Future orders automatically use the stored credentials.





 How do I connect my on-premises environment to VMware Shared? 

Each virtual data center has an Edge Services Gateway (ESG) which provides network connectivity to the virtual data center. On-premises connectivity to the customer virtual data center can be accomplished in the following ways:



* IPsec tunnel over the internet to the ESG
* SSL VPN tunnel over the internet to the ESG
* Direct internet access through the ESG to the VMs by using NAT or load balancing
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/icon_hamburger.svg) > Classic Infrastructure > Device List.
3. Identify the bare metal server that you want to monitor. Copy the Public IP.
4. Click the bare metal server device name.
5. Select Passwords. Copy the password for the root user.

Then, from a terminal, run the following command:

ssh <USER_ID>@<IP_ADDRESS>

Where:

<USER_ID> is the user ID that you use to log in to the bare metal server. For example, use root.

<IP_ADDRESS> is the public IP address of the bare metal server.

For example: ssh root@45.123.122.12









 Step 2: Provision an IBM Log Analysis instance 

To provision an instance of IBM Log Analysis through the IBM Cloud UI, complete the following steps:



1. Log in to your IBM Cloud account.

Click [Log in to IBM Cloud](https://cloud.ibm.com/login) to sign in to the IBM Cloud.

After you log in with your user ID and password, the IBM Cloud console opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, click Services and select the Logging and Monitoring category.
4. Click the IBM Log Analysis tile.
5. Select a region for the service instance.
6. Select the Lite service plan.

By default, the Lite plan is set.

For more information about other service plans, see [Pricing plans](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_plans).
7. Specify a Service name for your IBM Log Analysis service instance.
8. Select the Default resource group.
After you log in with your user ID and password, the IBM Cloud UI opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click the IBM Cloud Activity Tracker tile.
5. Enter a name for the service instance.
6. Select the location where you plan to provision the instance.

To get the latest list of locations that are available for the IBM Cloud Activity Tracker service, see [Locations](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-regions).
7. Select a resource group.

By default, the Default resource group is set.

Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
8. Select a service plan.

By default, the lite plan is set.
9. Click Create.



After you provision an instance, the Activity Tracker dashboard opens.

Next, go to the web UI to manage events in your account. [Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-launchlaunch).





 Configuring your instance to be accessible to private endpoints only 

After provisioning your instance through the Observability dashboard or catalog, you can configure the instance to be accessibile by private endpoints only.

If you configure your instance to use private endpoints only, this will block the public endpoints. All API usage that may be in progress on the public endpoints will be blocked when the configuration change is made.

Unless otherwise specified when provisioning an instance, the default is for the instance to be accessible by both public and private endpoints.



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud dashboard opens.
2. Click the Menu icon !
Pipeline Service ID <br><br> * can deploy/undeploy applications<br> * can view/set app and service configuration<br><br><br> <br><br> * can deploy/undeploy applications<br> * can view/set app and service configuration<br><br><br> <br><br> * can deploy/undeploy applications<br> * can view/set app and service configuration<br><br><br> 







 Identity and Access Management (IAM) 

Cloud Identity and Access Management (IAM) enables you to securely authenticate users for both platform and infrastructure services and control (authorize) access to resources consistently across the IBM Cloud platform. IBM Cloud services enabled to use Cloud IAM for access control are provisioned into [resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs) within your account. They allow you to give users, service IDs, and trusted profiles quick and easy access to more than one resource at a time. Cloud IAM access policies are used to assign users and service IDs access to the resources within your account.

This tutorial focuses on a single account. Multiple accounts can be grouped within an [enterprise account](https://cloud.ibm.com/docs/account?topic=account-what-is-enterprise) and organized in account groups to centrally manage billing and resource usage.

A policy assigns a user, service ID, or trusted profile one or more roles with a combination of attributes that define the scope of access. The policy can provide access to a single service down to the instance level, or the policy can apply to a set of resources organized together in a resource group. Depending on the user roles that you assign, the user, service ID, or trusted profile is allowed varying levels of access for completing platform management tasks or accessing a service by using the UI or performing specific types of API calls.

Zoom

!