vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This distribution allows for higher performance because it increases capacity by allowing more concurrent sessions. A load balancer also provides for a better user experience and availability by preventing a single server from getting overburdened.

IBM Cloud offers several load balancers, including IBM Cloud® Load Balancer and IBM Cloud® Internet Services for the classic infrastructure. For information on all load balancer options, see [IBM Cloud Load Balancers](https://www.ibm.com/cloud/load-balancer).



 IBM Cloud Load Balancer 

The IBM Cloud Load Balancer is an IaaS cloud load balancer that operates in a single data center. It supports both HTTP/HTTPS and TCP-based applications either as public, private load balancer, and public-to-public. It has on-demand scalability based on load: scaling up as load increases and down when load decreases.

Other key load-balancing features of Load Balancer include:



* Public (internet-facing) load balancer
* Internal (private) load balancer
* Traffic distribution based on Layer-4 port information and Layer-7 (HTTP/HTTPS)
* SSL offload
* Layer-4 health checks for TCP ports and Layer-7 health checks for HTTP



Additionally, when the load balancer is deployed in a data center that is part of an MZR and your account has VLAN spanning or is VRF-enabled, then a second load balancer is instantiated in another data center that is part of the same MZR in an active-active fashion. This configuration is visible to you and provides an extra layer protection against failure, increasing reliability and availability of your application on IBM Cloud.

Zoom

![IBM Cloud Load Balancer supporting either or both public and private.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/HA-load-balancer.svg)

Figure 5. IBM Cloud Load Balancer supporting either or both public and private (internal) deployment.





 IBM Cloud Internet Services
* [SAP Note 1409608 - Virtualization on Windows](http://launchpad.support.sap.com//notes/1409608)
* [SAP Note 1409604 - Virtualization on Windows: Enhanced Monitoring](http://launchpad.support.sap.com//notes/1409604)
* [SAP Note 2134316 - Can SAP ASE run in a cloud environment?](https://launchpad.support.sap.com//notes/2134316)
* [SAP Note 2923773 - Linux on IBM Cloud (IaaS): Adaption of your SAP License](https://launchpad.support.sap.com//notes/2923773)







 SAP Notes generic for IBM Cloud 



* [SAP Note 2588225 - SAP on IBM Cloud: Protect against speculative execution vulnerabilities](https://launchpad.support.sap.com//notes/2588225)
To create a new access key for an IBM Cloud Security and Compliance Center Workload Protection instance, complete the following steps:



1. Obtain the Workload Protection API token from the IBM Cloud Security and Compliance Center Workload Protection UI. [Learn more](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-api_tokenapi_token_get).
2. Issue a curl POST request against the endpoint to generate a new access key.

curl -XPOST -H 'Authorization: Bearer SYSDIG_API_TOKEN' -H 'IBMInstanceID: GUID' https:ENDPOINT/api/customer/accessKeys

Where



* ENDPOINT is the URL for the region where the instance is available. For more information, see [Endpoints](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-endpointsendpoints).
* SYSDIG_API_TOKEN is the API token that you get in step 1.
* GUID is the GUID of the instance that is associated with the access key.



For example, to create an access key, you can run the following:

curl -XPOST -H 'Authorization: Bearer xxxxxxx' https://us-east.security-compliance-secure.cloud.ibm.com/api/customer/accessKeys

The output will provide the newly generated access key in the response.

{"customerAccessKey":{"enabled":true,"accessKey":"b302311f-aa1c-4930-8726-59fb4ba0fe84","dateCreated":1683550580444,"dateDisabled":null,"limit":null,"reservation":null,"teamId":null}}
{
"customerAccessKey": {
"enabled": true,
"accessKey": "12345678-1234-1234-1234-123456789012",
"dateCreated": 1573852152224,
"dateDisabled": null,
"accessKey": "87654321-1234-1234-1234-123456789012",
"dateCreated": 1573849361000,
"dateDisabled": 1573849367000,
"limit": null,
"reservation": null,
"teamId": null
}
]
}







 Deleting access keys 

To delete an access keys for an IBM Cloud Security and Compliance Center Workload Protection instance, complete the following steps:



1. Obtain the API Token from the IBM Cloud Security and Compliance Center Workload Protection UI. [Learn more](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-api_tokenapi_token_get).
2. Issue a curl DELETE request against the regional endpoint to delete the access key.

curl -X DELETE -H 'Authorization: Bearer SYSDIG_API_TOKEN' -H 'IBMInstanceID: GUID' https://ENDPOINT/api/customer/accessKeys/ACCESS_KEY

Where



* ENDPOINT is the URL for the region where the monitoring instance is available. For more information, see [Endpoints](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-endpointsendpoints).
* SYSDIG_API_TOKEN is the API Token retrieved in Step 1.
* GUID is the GUID of the instance that is associated with the access key.
* ACCESS_KEY is the access key to be deleted. You can [view a list of all access keys](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-access_keyaccess_key_view) to obtain the access key values.
* GUID is the GUID of the instance that is associated with the access key.









 Hide the access key 

To hide the Access Key page for non-admin users in an Workload Protection instance through the IBM Cloud UI, complete the following steps:



1.
Keeping the management functions fully isolated from the workload cluster makes it impossible for a runaway workload VM to use resources that are dedicated to platform management. This way, administrators ensure that they can maintain full control of the environment.

vSAN is used to provide enhanced resiliency to the management stack. The use of shared storage provides rapid restoration of management components if an ESXi host is lost.

The management software stack includes the following components:



* vCenter Server, which manages all hosts in the entire IBM Cloud for VMware Regulated Workloads instance.
* Microsoft® AD/DNS servers, which provide DNS and authentication services.
* NSX-T management components to fully isolate the SDN control plane from the workload cluster.
* Security is further enhanced by IBM Hyper Protect Crypto Services (HPCS). HPCS uses a FIPS 140-2 Level 4 hardware security module (HSM) that gives access to the highest level of security for regulated data and digital assets. HPCS helps meet regulatory compliance requirements by providing complete control of data encryption keys, including the HSM primary key.
* Caveonix RiskForesight provides a common Risk Management Control Plane (RMCP) for continuous and proactive protection of management and edge workloads. It provides a comprehensive cloud workload protection platform for IBM Cloud for VMware Regulated Workloads. The IBM Cloud for VMware Regulated Workloads architecture is designed to enable compliance with NIST and other necessary certifications, as required for the SaaS provider and SaaS consumer.
* VMware Aria® Operations™ Manager, VMware Aria Operations™ for Logs, and the optional VMware Aria Operations™ for Networks. These components collectively provide a console for vSphere operations, the ability to automate management of the cloud platform, centralized log collection, and network visibility, analysis, and optimization.
* Veeam provides continuous backup of the management stack for protection against disasters and rapid restoration to known good states if corruption of any management stack component were to occur. Veeam can also provide backup services for the workload cluster. The single site deployment can use the Veeam bare metal option to provide a suitable backup repository.







 Gateway cluster
[Building resilient and cost-effective infrastructure](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/ha-building-resilient-infra.svg)

Figure 1. Building Resilient and Cost-Effective Infrastructure



 IBM Cloud VPC infrastructure provides by design Customer Selects 

 <br><br> * Protection against a single-point-of-failure<br> * Redundant power and high-speed connections<br> * Dual fans and network connections<br><br><br> <br><br> * More features, such as anti-affinity and Auto scale<br> * Service offerings, such as LBaaS or VPN Gateways<br><br><br> 



With IBM Cloud, you have several methods to build resilient architectures to choose from:



* Standardized user interface that makes building custom infrastructures as simple as provisioning a server.
* Terraform scripts that provide a CLI to automate your deployment consistently across different projects or locations.
* Schematics workspaces that provide a user interface to customize and automate your deployment.







 Regions and availability zones 

IBM Cloud data centers are in different geographical areas, countries, and regions. Each region has one or more availability zones, which are specific physical locations. Data centers can be single-zone, multi-zone region, or cross-multi-zone region.



 Single-zone 

A singl availability zone (SAZ) provides redundant resources with low to medium cost. Use an SAZ for medium level applications with less stringent resiliency requirements.

Zoom

![Single zone with Placement Groups](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/ha-single-zone.svg)

Figure 2. Single-zone

The single zone provides multiple VSIs for web, app, and db tiers in a single zone.
Auto-pausing and Auto-resuming 

IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service offers a feature called auto-pause and resume where the system automatically detects inactivity and pauses its operations along with the customer billing. As soon as an activity (queries against the catalog are not considered activities) is detected on the system, it automatically resumes the operations and starts customer billing again.

You can perform an on demand (ad hoc) or scheduled resume while the system is in the auto-paused state.



  Auto-pausing and Auto-resuming with the web console 

For more information, see [Auto-pausing and auto-resuming](https://cloud.ibm.com/docs/netezza?topic=netezza-patterns&interface=uiautopnr-console).
IBM Cloud Data Security Broker docs 

Explore the data protection services that Data Security Broker offers and the ways to install, configure, and login to Data Security Broker Manager and perform data encryption.

  Recommended content 

[Install Data Security Broker Installing Data Security Broker Manager and Data Security Broker Shield from IBM Cloud Catalog ](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_install_catalog)[Configure Data Security Broker Manager You can find details on configuring the Data Security Broker Manager console in this section.](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_configure)[Login to Data Security Broker Manager This section details the steps to log into the Data Security Broker Manager console.](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_login)[Data Protection Services You can find the details on the types of data protection services offered by Data Security Broker.](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_encrypt_postgress)[Configure IBM Key Protect and IBM Cloud Hyper Protect Crypto Services (HPCS) In this section, you can find details on how to configure IBM Key Protect and IBM Cloud Hyper Protect Crypto Services (HPCS) and add it as a keystore in Data Security Broker Manager.](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_configure_keyprotect)[FAQs This section provides answers to frequently asked questions about the Data Security Broker software.](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_faqs)
High-Availability 

IBM Cloud® Databases for EnterpriseDB is a managed cloud database service that is fully integrated into the IBM Cloud environment. The database, storage, and supporting infrastructure all run in IBM Cloud.

Databases for EnterpriseDB provides replication, fail-over, and high-availability features to protect your databases and data from infrastructure maintenance, upgrades, and failures. Deployments typically contain a cluster with three data members: a leader and two replicas. The replica members contain a copy of your data from the leader by using asynchronous replication, with a distributed consensus mechanism to maintain cluster state and handle failovers. If the leader becomes unreachable, the cluster initiates a failover and a replica is selected and promoted to leader. The replica rejoins the cluster and your cluster continues to operate normally, but with reduced capacity.

With three members, Databases for EnterpriseDB provides more protection against zonal outages and improves the safety of synchronous transactions.

Databases for EnterpriseDB will, at times, do controlled switchovers under normal operation. These switchovers are no-data-loss events that result in resets of active connections. There is a period of up to 15 seconds where reconnections can fail. At times, unplanned failovers might occur due to unforeseen events on the operating environment. These can take up to 45 seconds, but can be less. In both cases, potential exists for the downtime to be longer.

You can extend high-availability to more regions and spread to more replicas by adding [read-only replicas](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-for-enterprisedb-read-only-replicas).



 Synchronous replication 

By default, streaming replication is asynchronous. If the primary server crashes then some transactions that were committed may not have been replicated to the standby server, causing data loss. Cloud Databases ensures data loss is kept to a minimum substantial data loss; however, synchronous replication offers the ability to confirm that all changes made by a transaction have been transferred to a synchronous member, ensuring consistency across a cluster.
About FortiGate Security Appliance 1 Gbps 

A FortiGate Security Appliance 1 Gbps (FSA) is a dedicated single-tenant network device that is connected upstream from a server that protects any or all servers on a public VLAN. It is purchased separate from a server and can be added to a VLAN at any time. IBM© Cloud deploys the FortiGate 1 Gbps within a Virtual Domain (VDOM) on the dedicated appliance. You have full access to that virtual domain without compromising the integrity of the device.

All instances of this service are deprecated. Existing instances can be used until it is no longer supported after 21 July 2021. Use one of the other available [firewall options](https://cloud.ibm.com/docs/fortigate-1g?topic=fortigate-10g-exploring-firewalls) to get our latest security capabilities on IBM Cloud. For migration information, see [Migrating FortiGate Security Appliance 1Gbps](https://cloud.ibm.com/docs/fortigate-1g?topic=fortigate-1g-migration-overview)

With FSA 1 Gbps, you have advanced features and the ability to fine-tune the device to a much higher degree than other products. The firewall blocks or shapes traffic before the traffic ever reaches the server. The main advantages are that a server handles 'good' traffic exclusively and that bandwidth can be constrained for less critical communications.

You can manage the FSA either through the web-based FortiOS GUI or the CLI (Command Line Interface) by using SSH. High availability can also be ordered, which provides two appliances in active-passive deployment with synchronized configurations.

Since monthly server bandwidth is recorded at the server switch port, traffic that is blocked by the FSA 1 Gbps is not counted against your monthly allotments. As a result, the need to pay for unwanted traffic is eliminated.



  Overview and features 

Intended Use: Single Public VLAN Protection

User Interface: FortiGate GUI and Command Line Interface

Features: Stateful Packet Inspection, VLAN Protection, Ingress Firewall Rules, Egress Firewall Rules, NAT, SSL VPN Termination, IPsec VPN Termination, Advanced Logging, High Availability (Optional)

Throughput: 1 Gbps (2 Gbps Aggregated)
24 June 2021 

New version of the IBM Cloud for Financial Services profile
: Version 0.1.1 of the IBM Cloud for Financial Services profile is now available with new goals and controls. For more information, see the [IBM Cloud for Financial Services profile change log](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-fs-change-log).





 22 June 2021 

Tanium integration
: Now, you can configure [Tanium Comply](https://docs.tanium.com/comply/comply/index.html) to forward your compliance data. With Tanium Comply, you can evaluate your organizations endpoints for potential vulnerabilities and misconfigurations against industry security standards, vulnerability definitions, and custom compliance checks. When you integrate Tanium with the Security and Compliance Center, you can view all your compliance data in one location in the same format.





 14 June 2021 

IBM-managed collector
: A collector is used to gather the configuration information about your resources and then validate it against a specified standard. Previously, you were responsible for the installation and lifecycle management of the collector. Now, you can get a proof of concept up and running quickly by configuring an IBM-managed collector.

New goals
: You might notice that your compliance score changed even though you didn't update any of your configurations. New goals were added to the Security and Compliance Center profiles that your resources are automatically scanned for. For detailed descriptions of the new goals, you can review the IBM Best Practices Controls 1.0 profile. All the goals with ID's in the following ranges are new.



* Goal ID's: 3000901 - 3000907







 5 April 2021 

Initial Posture Management API support
: As part of this release, the Posture Management component of the service provides three external APIs that you can use as part of your security and compliance automation. For more information, see the [Posture Management API docs](https://cloud.ibm.com/apidocs/security-compliance/posture).

Proxy support for discovery and fact collection
select P.number as number
from PhoneNum P
where ContainsDict('EmployeePhoneDict',P.number);
Show more

Dictionaries are always evaluated on token boundaries. For example, if a dictionary consists of the term fish, no match exists in the text Let's go fishing!.





 ContainsDicts 

The ContainsDicts function checks if the text of a span contains any entry from any given dictionaries. This function accepts as input arguments two or more dictionaries, an optional flag specification, and a span to evaluate.

ContainsDicts('<dictionary>','<dictionary>','<dictionary>', ['<flags>', ]<span>)

The ContainsDicts function returns TRUE if the span contains one or more matches from at least one of the specified dictionaries. The flags can be Exact or IgnoreCase.



* If Exact is used, a case-sensitive match is performed against each of the terms in the dictionaries.
* If IgnoreCase is used, the match that is performed against each of the terms in the dictionaries is not case-sensitive.
* If no flag is specified, the dictionary matches based on any flag that was specified when it was created. If no flag was specified during creation, it matches by using the IgnoreCase flag.



If either or both arguments are null, then the function returns null.

The following example illustrates the use of the ContainsDicts function with the Exact flag:

create view PersonWithFirstName as
select P.reference as reference
from Person P
where ContainsDicts(
'FirstNamesUsedGlobally',
'FirstNamesUsedInGermanyLong',
'NickNamesUsedGlobally',
'FirstNamesUsedInGermanyShort',
'FirstNamesUsedInItaly',
'FirstNamesUsedInFrance',
'Exact',
P.reference);





 ContainsRegex 

The ContainsRegex function checks whether the text of a span matches a given regular expression. This function accepts a regular expression with which to match, an optional flag specification, and the input span against which to match.
As a user of Hyper Protect Crypto Services, you get your own dedicated slot that you set up on your own to ensure that no body else can access. Because Hyper Protect Crypto Services and VMware do not contact the same interfaces, the Key Management Interoperability Protocol for VMware component acts as an intermediary to allow the VMware environment to store and use keys from Hyper Protect Crypto Services.

As a single-tenant service, Hyper Protect Crypto Services offers dedicated control of the Hardware Security Module for VMware images for each customer. Hyper Protect Crypto Services extends the family of key management services in the IBM Cloud toward single-tenant instances with dedicated hardware secret control.

Check out the [overview video on IBM Cloud Hyper Protect Crypto Services and VMware on IBM Cloud solutions](https://mediacenter.ibm.com/id/0_4wm4bq4s) for more information. For a step-to-step tutorial, see [Configuring KMIP in Hyper Protect Crypto Services for key management and distribution](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-tutorial-kmip-vmware) and the [demo video](https://mediacenter.ibm.com/media/1_e5gk6ktn).

Zoom

![VMware image protection and vSAN encryption with KYOK](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/byok-vm.svg)

Figure 2. VMware image protection with KYOK







 Using Unified Key Orchestrator for multicloud key orchestration 

You can use Unified Key Orchestrator to securely create and manage your keys and internal keystores across multiple clouds.

Zoom

!
4. Select one instance. Then, click Open dashboard.

The Monitoring UI opens.







 Launch the Workload Protection UI 

The Workload Protection UI is only available for instances using the [Graduated Tier - Sysdig Secure + Monitor service plan](https://cloud.ibm.com/docs/monitoring?topic=monitoring-service_plans).

To access the Workload Protection UI, complete the following steps:



1. Log in to your IBM Cloud account.

Click [IBM Cloud dashboard](https://cloud.ibm.com/login) to launch the IBM Cloud dashboard.

After you log in with your user ID and password, the IBM Cloud Dashboard opens.
2. In the navigation menu, select Observability.
3. Select Monitoring.

The list of instances that are available on IBM Cloud is displayed.
4. Select an instance with the Graduated Tier - Sysdig Secure + Monitor service plan. Then, click Open dashboard.

The Monitoring UI opens by default.
5. Click the Monitor icon.

Zoom

![Monitor icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/monitor.png)

Monitor icon

The Switch Products selection box opens.

Zoom

![Switch products](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/platform.png)

Switch products
6. Select Workload Protection to launch the Workload Protection UI.



For more information on using Workload Protection, see the [IBM Cloud Security and Compliance Center Workload Protection documentation.](https://cloud.ibm.com/docs/workload-protection)