vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For information on end of service pack support (EoSPS) dates, see [AIX support lifecycle](https://www.ibm.com/support/pages/aix-support-lifecycle-information).

AIX stock images currently available when you create a VM are:



* AIX 7.3 TL1 SP1
* AIX 7.2 TL5 SP5
* AIX 7.1 TL5 SP9



IBM i - Power Systems Virtual Server supports IBM i 7.1, or later. Clients running IBM i 6.1 must first upgrade the OS to a current support level before migrating to the Power Systems Virtual Server. IBM i 7.2 supports direct [upgrades from IBM i 6.1 or 7.1 (N-2)](https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzahc/fastpathrzahc.htm).



* [S922 (9009-22A), E980 (9080-M9S) software maps](https://www-01.ibm.com/support/docview.wss?uid=ssm1platformibmi)
* [IBM i PTF minimum levels](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-minimum-levels)
* [IBM i release life cycle](https://www.ibm.com/support/pages/release-life-cycle)



IBM i stock images currently available when you create a VM are:



* IBM i 7.5 TR1
* IBM i 7.4 TR7
* IBM i 7.3 TR13
* IBM i 7.2 TR13
* IBM i 7.1 TR13



Linux - Power Systems Virtual Server supports Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise (SLES) distributions. The following Linux stock images are currently available when you select Full Linux Subscription (learn more about [Full Linux Subscription](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-set-full-Linux)):

Red Hat
To learn about opening an IBM support case, or about support levels and case severities, see [Contacting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
5. For the Problem type, search for or select Red Hat OpenShift on IBM Cloud.
6. For the Case details, provide a descriptive title and include the details that you previously gathered. From the Resources, you can also select the cluster that the issue is related to.







 Requesting access to allowlisted features 



1. [Create a ticket](https://cloud.ibm.com/unifiedsupport/cases/form).
2. On the Category tab, select Account
3. On the Topic tab, select the Other subtopic and click Next.
4. On the Details tab, in the Subject field, enter Allowlist request for <FEATURE> for account <ACCOUNTID> and include the feature name and your account ID.
5. In the Description field, include details about the feature that you want access to.
6. Click Next and review your selections ticket.
7. Click Submit case.
8. After support processes the ticket, you will receive a notification that your account is updated.
Typically, a performant and effective way to employ this feature is by using it only on specific databases or users that must have the highest degree of data durability available.





 Application-level High-Availability 

Applications that communicate over networks and cloud services are subject to transient connection failures. You want to design your applications to retry connections when errors are caused by a temporary loss in connectivity to your deployment or to IBM Cloud.

Because Databases for EnterpriseDB is a managed service, regular updates and database maintenance occurs as part of normal operations. This can occasionally cause short intervals where your database is unavailable. It can also cause the database to trigger a graceful fail-over, retry, and reconnect. It takes a short time for the database to determine which member is a replica and which is the leader, so you might also see a short connection interruption. Failovers generally take less than 30 seconds.

Your applications must be designed to handle temporary interruptions to the database, implement error handling for failed database commands, and implement retry logic to recover from a temporary interruption.

Several minutes of database unavailability or connection interruption are not expected. Open a [support ticket](https://cloud.ibm.com/unifiedsupport/cases/add) with details if you have time periods longer than a minute with no connectivity so we can investigate.





 Connection Limits 

Databases for EnterpriseDB sets the maximum number of connections to your database to 115. 15 connections are reserved for the superuser to maintain the state and integrity of your database, and 100 connections are available for you and your applications. After the connection limit is reached, any attempts at starting a new connection results in an error. To prevent overwhelming your deployment with connections, use connection pooling, or scale your deployment and increase its connection limit. For more information, see the [Managing Databases for EnterpriseDB Connections](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-managing-connections) page.





 High availability, disaster recovery, and SLA resources
Both members contain a copy of your data by using asynchronous replication, with a distributed consensus mechanism to maintain cluster state and handle failovers.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database member resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the members are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Databases for PostgreSQL. The reports evaluate IBM's operational controls according to the criteria set by the American Institute of Certified Public Accountants (AICPA) Trust Services Principles. The Trust Services Principles define adequate control systems and establish industry standards for service providers such as IBM Cloud to safeguard their customers' data and information.

You can request an SOC 2 Type 2 report from the customer portal or contact your sales representative. Alternatively, you can open a support ticket with [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter)





 ISO 27017, ISO 27018 

Databases for PostgreSQL conforms to the guidelines for information security controls applicable to the provision and use of cloud services as defined in [ISO 27017](https://www.iso.org/standard/43757.html) and [ISO 27018](https://www.iso.org/standard/76559.html).





 General Data Protection Regulation (GDPR) 

If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for PostgreSQL processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.
ibmcloud billing enterprise-usage [--account-group ACCOUNT_GROUP_NAME | --account-group-id ACCOUNT_GROUP_ID | --account ACCOUNT_NAME | --account-id ACCOUNT_ID] [--month MONTH] [--children] [--output FORMAT] [-q, --quiet]



 Command options 

--account ACCOUNT_NAME (optional)
: Name of target account.

--account-id ACCOUNT_ID (optional)
: ID of target account.

--account-group ACCOUNT_GROUP_NAME (optional)
: Name of target account group.

--account-group-id ACCOUNT_GROUP_ID (optional)
: ID of target account group.

--children (optional)
: Show children usage reports.

--month MONTH (optional)
: Target month. Default to current month.

--output FORMAT (optional)
: Specify output format. Only JSON is supported.

-q, --quiet (optional)
: Suppress verbose output.
Queues are mirrored on all three nodes.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database node resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the nodes are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Messages for RabbitMQ. The reports evaluate IBM's operational controls according to the criteria set by the American Institute of Certified Public Accountants (AICPA) Trust Services Principles. The Trust Services Principles define adequate control systems and establish industry standards for service providers such as IBM Cloud to safeguard their customers' data and information.

You can request an SOC 2 Type 2 report from the customer portal or contact your sales representative. Alternatively, you can open a support ticket with [IBM Cloud support](https://cloud.ibm.com/unifiedsupport/supportcenter)





 ISO 27017, ISO 27018 

Messages for RabbitMQ conforms to the guidelines for information security controls applicable to the provision and use of cloud services that are defined in [ISO 27017](https://www.iso.org/standard/43757.html) and [ISO 27018](https://www.iso.org/standard/76559.html).





 General Data Protection Regulation (GDPR) 

If you have an account with IBM Cloud, your personal data is held by IBM Cloud. The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client in order to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Messages for RabbitMQ processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.
The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 null null 
 null null 
 null null 







 ibm-cloud-for-education 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use education for the service name.

No supported roles.





 IBM Cloud Platform Enterprise Service 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use enterprise for the service name.

Platform roles

Service roles

Actions



Table 56. Platform roles - IBM Cloud Platform Enterprise Service
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator Administrators can update the enterprise, create accounts and account groups, move accounts between account groups, import existing accounts, and view usage reports. 
 Editor Editors can update the enterprise, create accounts and account groups, view usage reports, and import accounts. 
 Operator Operators can view the enterprise, account groups, and accounts. 
 Viewer Viewers can view the enterprise, account groups, and accounts. 







 License and Entitlement 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use entitlement for the service name.

Platform roles

Actions



Table 57. Platform roles - License and Entitlement
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 







 Event Notifications
* Public and Private Networking - Databases for EnterpriseDB is integrated with [Service Endpoints](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-service-endpoints). You can select whether to use connections over the public network, the IBM Cloud internal network, or both.
* Dedicated Cores - Allocating dedicated cores to your deployment introduces hypervisor-level isolation to your database instance, by using isolated virtual machines to ensure that your data processing remains separated from other customers. It also provides a guaranteed minimum number of CPUs to your deployment. Deployments with dedicated cores in the same Resource Group and IBM Cloud Region might share a virtual machine.







 Data Resilience 



* [Backups](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-dashboard-backups) are included in the service. Databases for EnterpriseDB backups reside in [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cloud-object-storage&cloud-object-storage-about-cloud-object-storage) and are also [encrypted](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-security).
* Databases for EnterpriseDB deployments are configured with replication. Deployments contain a cluster with two data members. Both members contain a copy of your data by using asynchronous replication, with a distributed consensus mechanism to maintain cluster state and handle failovers.
* If you deploy to an IBM Cloud Single-Zone Region (SZR), each database node resides on a different host in the data center.
* If you deploy to an IBM Cloud Multi-Zone Region (MZR), the nodes are spread over the region's availability zone locations.







 SOC 2 Type 2 Certification 

IBM provides a Service Organization Controls (SOC) 2 Type 2 report for Databases for EnterpriseDB. The reports evaluate IBM's operational controls according to the criteria set by the American Institute of Certified Public Accountants (AICPA) Trust Services Principles.
Users that are created directly from the API and CLI do not appear in Service Credentials, but you can [add them](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-connection-stringsadding-users-to-_service-credentials_) if you choose.





 The read-only user 

The ibm-cloud-base-user-ro manages privileges for users that are created to access read-only replicas. More information can be found on the [Configuring Read-only Replicas](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-read-only-replicas) page.





 Other ibm Users 

If you run the du command with your admin account, you might notice users that are named ibm, ibm-cloud-base-user, and ibm-replication.

The ibm-cloud-base-user is used as a template to manage group roles for other users. It is used to manage the users who are created through the CLI and API as well as enable the integration with the Service Credentials user creation on IBM Cloud. A user that is a member of ibm-cloud-base-user inherits the create role and create database attributes from ibm-cloud-base-user. The ibm-cloud-base-user is not able to log in.

The ibm and the ibm-replication accounts are the only superusers on your deployment. A superuser account is not available for you to use. These users are internal administrative accounts that manage replication, metrics, and other functions that ensure the stability of your deployment.





 Users created with psql 

You can bypass creating users through IBM Cloud entirely, and create users directly in Databases for EnterpriseDB with psql. This allows you to make use of PostgreSQL's native [role and user management](https://www.postgresql.org/docs/current/database-roles.html). Users and roles created in psql must have all of their privileges set manually, including privileges to the objects that they create.
[Enterprise account organization with Satellite reference architecture](https://cloud.ibm.com/docs-content/v1/content/9ac5c38b41e0aa1cb4ccc6cc7f547751ec805221/framework-financial-services/satellite/images/resource-organization/satellite-enterprise-account-organization-beta2.drawio.svg)

Figure 8. Enterprise account organization









 Related controls in IBM Cloud Framework for Financial Services 

The following [IBM Cloud Framework for Financial Services controls](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-aboutframework-control-requirements) are most related to this guidance. However, in addition to following the guidance here, do your own due diligence to ensure you meet the requirements.



Table 1. Related controls in IBM Cloud Framework for Financial Services

 Family Control 

 Access Control (AC) [AC-5 Separation of Duties](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-5) <br>[AC-6 Least Privilege](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ac-6) 







 Next steps 



* [Access management in IBM Cloud](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-access-management)
* [IBM Data Processing Addendum (DPA)](https://www.ibm.com/support/customer/csol/terms/?id=DPA-DPL)







 HIPAA support 

Hyper Protect Crypto Services meets controls for the US Health Insurance Portability and Accountability Act (HIPAA) to ensure safeguarding of protected health information (PHI).

If you or your company is a covered entity as defined by HIPAA, you can enable the HIPAA Supported setting for your IBM Cloud account. To find out more, see [Enabling the HIPAA Supported setting](https://cloud.ibm.com/docs/account?topic=account-eu-hipaa-supportedenabling-hipaa).





 IRAP support 

Hyper Protect Crypto Services meets the requirements of the Information Security Registered Assessors Program (IRAP) to provide high-quality information and communications technology services to government in support of Australia’s security.

For more information, see [IBM Cloud regional compliance programs](https://www.ibm.com/cloud/compliance/regional).





 ISO 27001, 27017, 27018 

Hyper Protect Crypto Services is ISO 27001, 27017, 27018 certified. You can view compliance certifications by visiting [IBM Cloud global compliance programs](https://www.ibm.com/cloud/compliance/global)





 SOC 2 Type 1 

Hyper Protect Crypto Services is SOC 2 Type 1 certified. For information about requesting an IBM Cloud SOC 2 report, see [IBM Cloud global compliance programs](https://www.ibm.com/cloud/compliance/global).
Central administration account 

This administrative account centralizes the management of the deployable architectures that are needed to provision the enterprise account structure, the Security and Compliance Center, and the tools account across both development and production.

Zoom

![Central administration diagram. All of the information is conveyed in the surrounding text](https://cloud.ibm.com/docs-content/v1/content/f18e964848e0337fedc42d43e246fa446f4b9646/enterprise-account-architecture/images/admin-hub.svg)

Figure 1. Central administration account

The central administration account contains a catalog of deployable architectures that are deployed through IBM Cloud projects to manage the top-level accounts in both development and production to ensure both enterprises have nearly the same configuration and to provide centralized management. This account also holds the schematics agent to enable custom deployable architectures stored in corporate Git.



Table 1. Components

 Component Quantity Description 

 Security and Compliance Project 1 Manages the infrastructure as code for deploying the Security and Compliance Center and its dependencies in the root account 
 Network and Services project 1 Manages the infrastructure as code for deploying centralized networking and other common services into the central administration account 
 Business unit project 1-25 Manages the infrastructure as code for deploying a business unit account group, a backup account, the business unit administration account, and the BU administration account contents 
 Central administration project 1 Manages the infrastructure as code for deploying the resources in the central administration account, creating and configuring the administration backup account 
 Private catalog 1 Used to host the approved deployable architectures for the projects in this account 
 Schematics agent 1 Used enable privately hosted custom deployable architectures in the private catalog for this account 



The schematics agent, catalog, projects, and schematics workspaces must co-reside in a single account.

Additional Components not shown in the diagram:



Table 2. Additional components

 Component Quantity Description 

 Activity Tracker 1 Provides an audit trail for activity within the account 
 IBM Cloud Logging 1 Provides log monitoring for the infrastructure hosting the Schematics Agent 
 IBM Cloud Monitoring 1 Provides performance and error monitoring for the Schematics Agent 
 Event Notifications 1 Provides notifications for Projects
With the tools available through IBM Cloud, you can start and stay compliant with automation and ensure that deployments are done by using a secure software supply chain, all while managing your resources at scale. Go to the [IBM Cloud catalog](https://cloud.ibm.com/catalog) to check out the deployable architectures and visit the [Security and Compliance Center](https://cloud.ibm.com/security-compliance/overview) today to start defining your goals for security and compliance.

For more information about setting up your enterprise, configuring automated deployments by using projects, customizing deployable architectures, and more, see the [Enterprise account architecture](https://cloud.ibm.com/docs/enterprise-account-architecture) white paper and [Running secure enterprise workloads](https://cloud.ibm.com/docs/secure-enterprise) documentation.
If it's not already federated, a manual process with the IBMid federation team is required to establish federation. During the federation setup process, the customer collaborates with the IBMid federation team to define which email pattern matches with the IdP users. The decision to federate to your company's own user directory needs to involve the person in your company that can make company-wide decisions when it comes to connecting to external parties for identity services. You need to ensure that this person is included in the process. Federating with IBMid can have an impact on non-IBM Cloud web services that your company already uses with IBM. This option requires the creation of an App ID instance. It is a self-service option with a low usage fee. Choosing this option requires a custom URL to log in to IBM Cloud. In addition, an App ID instance and configuration of the federation to your IdP is required for every IBM Cloud account. 
 Costs Customers do not need to pay to use IBMid with or without federation. IBM Cloud App ID instances have a low fee, with a free tier up to 1,000 users and 1,000 events (for example, logins). See the App ID page for more details. 
 Federation setup Customers need to open a support case with IBMid Enterprise Federation to start the onboarding process. This is a manual process. Customer creates an IBM Cloud App ID instance and configures it according to the documented steps. This process is self-service. 
 Federation maintenance (for example, certificate update) Requires a manual interaction with the IBMid federation team. The customer can update their IBM Cloud App ID instance on their own (for example, this step is self-service). 
 Federation scope IBMid federation applies to every service that uses IBMid. This means that if a customer onboards to IBMid federation, this applies to his employees when logging on to IBM Cloud, but also when using other IBM SaaS offerings that are using IBMid. The federation has impact only on the IBM Cloud account in which the IBM Cloud App ID instance is configured to allow logins. It also does not impact any other IBM Cloud accounts or IBM SaaS offerings. 
 Account member onboarding Users need to be invited by their email address.