vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you already have a Lite plan instance created, you may create other Standard plan instances, but only one Lite plan instance is allowed.
* What happens if I exceed the maximum usage allowed for a Lite plan?

Once you exceed the allowed usage, the service instance associated with the Lite plan becomes inaccessible. You will receive a warning notification email with corrective steps. If you do not take action, the instance is removed.
* How can I find out the total size of my bucket by using the API?

You can use the [Resource Configuration API](https://cloud.ibm.com/apidocs/cos/cos-configurationreturns-metadata-for-the-specified-bucket) to get the bytes used for a given bucket.
* How can I view my buckets?

You can view and navigate your buckets using the console, CLI or the API.

For example, the CLI command ibmcloud cos buckets will list all buckets associated with the targeted service instance.
* Can I migrate data from AWS S3 into IBM Cloud Object Storage?

Yes, you can use your existing tools to read and write data into IBM Cloud Object Storage. You need to configure HMAC credentials allow your tools to authenticate. Not all S3-compatible tools are currently unsupported. For details, see [Using HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).
* Can I use AWS S3 SDKs with IBM Cloud Object Storage?

Yes, IBM COS SDKs are based on the official AWS S3 API SDKs, but are modified to use IBM Cloud features, such as IAM, Key Protect, Immutable Object Storage, and others. When using these SDKs, use HMAC authorization and an explicit endpoint. For details, see [About IBM COS SDKs](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-sdk-about).
* Is there a 100-bucket limit to an account?
Resource Groups FAQ 

You can migrate IBM® Cloudant® for IBM Cloud® resource instances into resource groups.

Since 16 July 2018, new IBM Cloudant resource instances are provisioned into resource groups, rather than Cloud Foundry spaces.



  How do I migrate an existing IBM Cloudant instance to a resource group? 

You can migrate IBM Cloudant instances on the following plans:



*  Lite
*  Standard
*  Dedicated Hardware



To migrate an IBM Cloudant instance from a Cloud Foundry space to a resource group, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).





  How much downtime occurs when you migrate an instance to a resource group? 

The migration process doesn't cause any downtime.





  Why do some instances have an organization and space and others don't? 

Since 16 July 2018, new instances are provisioned into resource groups rather than Cloud Foundry spaces. Resource instances created before this date have an associated Cloud Foundry organization and space. Instances created after this date are associated with a resource group instead.





  Why can't I create new Standard plan instances on my Dedicated Hardware instances? 

New Standard plan instances are provisioned into resource groups. In order to create these instances onto a Dedicated Hardware instance, the Dedicated Hardware instance must first be migrated into a resource group.

For more information about how to do this migration, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).

Once the Dedicated Hardware instance is migrated to a resource group, it appears in the Location drop-down menu when you create Standard plans.





  How can I migrate my Dedicated Hardware instances and the Standard plan instances that are hosted on them? 

In theory, instances can be migrated to resource groups in any order. The following order for Dedicated Hardware instances and the Standard plan instances that are hosted on them is recommended:



1.  Migrate Dedicated Hardware instances to a resource group. This migration allows new Standard plan instances to be created on the Dedicated Hardware.
2.  Migrate Standard instances.



Lite plan instances and Standard plan instances that are not hosted on Dedicated Hardware can be migrated at any time.
Pricing FAQs 

IBM Cloud

The IBM Watson® Speech to Text service is available at three pricing plans: Lite, Plus, and Premium. The following FAQs provide an overview of the pricing plans. For more information, see the Speech to Text service in the [IBM Cloud® Catalog](https://cloud.ibm.com/catalog/speech-to-text).

The Standard plan is no longer available for purchase by users. The Standard plan continues to be available to its existing users indefinitely. For more information, see [Can I continue to use the Speech to Text Standard plan?](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-faq-pricingfaq-pricing-standard) For new users, read about the new Plus and Premium plans below.



 What is the price for using the Speech to Text Lite plan? 

The Lite plan lets you get started with 500 minutes per month of speech recognition at no cost. You can use any available model for speech recognition. The Lite plan does not provide access to customization. You must use a paid plan to use customization.

The Lite plan is intended for any user who wants to try out the service before committing to a purchase. For more information, see the Speech to Text service in the [IBM Cloud® Catalog](https://cloud.ibm.com/catalog/speech-to-text). Services that are created with the Lite plan are deleted after 30 days of inactivity.





 What is the price for using the Speech to Text Plus plan? 

The Plus plan provides access to all of the service's features:



* Use of all available models (same as the Lite plan).
* Unlimited creation and use of custom language and custom acoustic models at no extra charge.
* A maximum of one hundred concurrent transcription requests from all interfaces, WebSocket and HTTP, combined.



The plan uses a simple tiered pricing model to give high-volume users further discounts as they use the service more heavily. Pricing is based on the aggregate number of minutes of audio that you recognize per month:
Transaction Engine notice 

The IBM® Cloudant® for IBM Cloud® on Transaction Engine service ends on 1 February 2023. You can no longer create new instances of IBM Cloudant on Transaction Engine. On 1 February 2023, all instances of IBM Cloudant on Transaction Engine will be permanently disabled and deprovisioned. Users of existing instances need to migrate from the service before the end of service date. You can find guidance on migrating from IBM Cloudant on Transaction Engine to IBM Cloudant Standard here: [Migrating from TXE](https://blog.cloudant.com/2022/01/14/Migrating-from-Cloudant-TXE-to-Standard).



  What is Transaction Engine? 

IBM Cloudant has an architecture option, which is underpinned by a Transaction Engine. This architecture aims to provide the best of both non-relational and relational data stores combining scale, fault tolerance, consistency, security, and speed at optimal cost. The Transaction Engine architecture is compared to the "Classic" architecture for clarity in the documentation. Instances that are provisioned with the Standard on Transaction Engine plan are deployed by using this architecture, while instances on the Lite and Standard plan are deployed on the "Classic" architecture.
FAQs for migrated products 

FAQs about products that are migrated from the Resource Management Console might include questions about Lite plans, changing pricing plans, and brokers connected to approved pricing plans.

To find all FAQs for IBM Cloud, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



 Why can't I add new block tier usage-based plans? 

Block tier pricing plans are not currently supported in Partner Center. If you set up a block tier pricing plan in the Resource Management Console and the plan was approved and published, no changes have been made and it was migrated as-is with your product. However, you can't edit the plan or set up a new block tier pricing plan. If you have any questions, open a support case. For information about opening a support case, see [Creating a Partner Center support case](https://cloud.ibm.com/docs/sell?topic=sell-get-pc-supportpc-support-case).





 What changed with Lite plan support? 

Lite plans are not supported in Partner Center. You can create a new free plan, and all users with Pay-As-You-Go and Subscription accounts can try out your product for free.

If you set up a Lite plan in the resource management console, and it was approved and published, no changes have been made and it was migrated as-is with your product. If you need to change a published pricing plan, open a support case. For information about opening a support case, see [Creating a Partner Center support case](https://cloud.ibm.com/docs/sell?topic=sell-get-pc-supportpc-support-case).





 Can I add a broker per location? 

No. Brokers are added per pricing plan, not per location. And, brokers can't be disconnected from already approved plans.





 Can I set different locations per plan for a single product? 

Yes. But, all plans for a single product must be set as either global or per location. Therefore, you can't have a plan that is set to global and then another plan set to be available for specific regions.
Select the "standard" plan and hit save.

In cases where the instance has been locked due to exceeding the maximum allowed size of a Lite instance it may be necessary to use the CLI. The plan ID for a standard Object Storage instance is 744bfc56-d12c-4866-88d5-dac9139e0e5d (if curious, this can be found by issuing the CLI command ic catalog service cloud-object-storage). You'll need to know the name of the instance you are trying to upgrade. For example, to upgrade the instance "My Object Storage", you can issue the command:

ic resource service-instance-update "My Object Storage" --service-plan-id 744bfc56-d12c-4866-88d5- dac9139e0e5d
* Are bucket names case-sensitive?

Bucket names are required to be DNS addressable and are not case-sensitive.
* What is the maximum number of characters that can be used in a key, or Object name?

Keys have a 1024-character limit.
* What are some tools unable to render object names?

Object names that contain unicode characters that are not allowed by the XML standard will result in "Malformed XML" messages. For more information, see [the XML reference documentation](https://www.w3.org/TR/xml/charsets).
* Can I create more than one Object Storage service with a Lite account?

If you already have a Lite plan instance created, you may create other Standard plan instances, but only one Lite plan instance is allowed.
* What happens if I exceed the maximum usage allowed for a Lite plan?

Once you exceed the allowed usage, the service instance associated with the Lite plan becomes inaccessible. You will receive a warning notification email with corrective steps. If you do not take action, the instance is removed.
* How can I find out the total size of my bucket by using the API?
: The default Liberty runtime version was updated to the 17.0.0.1 release.



* The default Liberty runtime also includes the PI75512 WebSockets interim fix.
* The monthly Liberty runtime version was updated to the [2017.2.0.0](https://developer.ibm.com/wasdev/blog/2017/02/17/beta-websphere-liberty-tools-february-2017/) release.
* The IBM JRE versions 8 and 7.1 were updated to SR4 FP1.
* The auto-configuration support was also extended to work with ibm-websphere-extreme-scale container.
* The auto-configuration support for [Cloudant NoSQL Database](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) was updated to provide the option of using the Cloudant Java Library instead of org.ektorp. To enable the use of the Cloudant Java Library you must set the following environment variable:

ibmcloud cf set-env <appName> LBP_SERVICE_CONFIG_CLOUDANTNOSQLDB 'type : cloudant'
* The buildpack also provides an updated version of the agent for the Auto-Scaling service and a number of app management enhancements.
* This buildpack also changes the way auto-configuration works for the Monitoring and Analytics service. Apps using the Free plan will no longer have the log capability added to their apps; it is being replaced by logmet.







 10 March 2017 

Updated Node.js buildpack v3.11
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.47, 0.10.48, 0.12.17, 0.12.18, 4.7.3, 4.8.0, 6.9.5, and 6.10.0. The default version now is 4.8.0.

In addition to the new runtimes, this release contains a fix for a bug encountered when enabling the shell app management handler using the devconsole UI. This buildpack also changes the way auto-configuration works for the Monitoring and Analytics service.
Currently, Dallas (us-south), Washington DC (us-east), London (eu-gb), and Sydney (au-syd) regions are supported.
4. Select a pricing plan - Based on your business requirements, select a pricing plan: Lite, Standard, and Enterprise.



* Lite - Includes all App Configuration capabilities for evaluation only. Not to be used for production. Lite plan services are deleted after 30 days of inactivity.
* Standard - The standard plan includes feature flags and property management capabilities. You can use simple and uniform REST APIs to configure, enable, segment, and monitor features to mobile devices and web applications.
* Enterprise - The enterprise plan includes targeting segment in addition to the property management and feature flags that are found in the Standard plan. The enterprise plan now supports by using private endpoints.



For more information about App Configuration usage and billing, see [Usage and billing](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-faqs-usage).
5. Configure your resource by providing a Service name for your instance, or use the preset name.
6. Select a resource group - The resource group selection helps how you want resources to be organized in your account. The resource group that you select cannot be changed after the service instance is created.
7. Optionally, define Tags to help you to identify and organize the instance in your account. If your tags are billing related, consider writing tags as key:value pairs to help group-related tags, such as costctr:124.
8. Optionally, define Access management tags that are needed to apply flexible access policies on specific resources. For example, access:dev, proj:version-1.
9. If you selected the Enterprise plan, then specify the Service endpoints. The following options are available:



* Public network - The public network service endpoints are accessible from anywhere on the internet.
* Both Public & Private network - use of both public and private service endpoint network access.



10. Accept the licensing agreements and terms by clicking the checkbox.
11.
Service Changes and Deprecations for IBM Cloudant 

You can see the deprecations for IBM® Cloudant® for IBM Cloud® here.



 IBM Cloudant Deprecation of Cloudant instances that are created as Cloud Foundry service instances 



 Details 

Due to the end of the Cloud Foundry service, IBM Cloudant instances that are created as Cloud Foundry service instances are being deprecated and must be migrated to an IBM Cloud [resource group](https://cloud.ibm.com/docs/account?topic=account-rgs&interface=ui).

Migration to a resource group provides the added capability to use [IBM Cloud IAM](https://cloud.ibm.com/docs/account?topic=account-iamoverview) to control access. When migrating the Cloudant instance, you can choose which of your IBM Cloud resource groups to migrate it to. For example, you might have one resource group for production and a different one for Dev/Test.

Standard Plan instances that are not migrated before 1 September 2023 will be migrated by IBM.

Should IBM be required to migrate a Cloudant instance to a resource group, it will be migrated to the default resource group for the IBM Cloud account. The assignment of the Cloudant instance to the default resource group cannot be changed later.

Lite plan instances that are not migrated before 1 August 2023 will be disabled for 30 days and deleted on 1 September 2023.





 How do I know if my instances use Cloud Foundry? 



* Display the list of Cloudant instances in the IBM Cloud GUI
* The presence of the migrate icon after the instance name identifies instances that need to be migrated







 How do I migrate the instance to an IBM Cloud resource group? 



* To complete the migration, follow these [IBM Cloudant instructions](https://cloud.ibm.com/docs/account?topic=account-migratemigrate_instances).





1. Open the More actions menu.
2. Select Migrate to a resource group to get started.
3. Select a resource group.
4. Click Migrate and the instance is migrated for you.
5. Since you can migrate only one instance at a time, you can continue migrating eligible instances after you migrate the first one.
Many other API methods changed and some are not available in v2. For a detailed comparison of the v1 and v2 API methods, see [API version comparison](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-to-v2-api).







 Picking a service plan 

Choose among the Plus, Enterprise, and Premium managed plans or opt for an on-premises installation by purchasing the Discovery Cartridge for IBM Cloud Pak for Data. Review the benefits and limits of each type of plan before you choose one.



* For more information about the plans, see [Discovery pricing plans](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-pricing-plans).
* For more information about artifact limits, see [Limit details](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-version-chooseplan-limit-links).



The following table shows plan types for managed deployments that are generally similar between v1 and v2.



Similar plans

 Current v1 plan Example v1 data usage Similar v2 plan 

 Lite Not applicable Plus Trial (no charge for 30 days only) 
 Advanced (low usage) 10,000 documents, 10,000 queries per month Plus 
 Advanced (high usage) 100,000 documents, 100,000 queries per month Enterprise 
 Premium Not applicable Enterprise or Premium 



To get information about the current storage, documents, and collections used, click the Environment details icon from the product user interface header.

You cannot do an in-place upgrade from a v1 plan, such as Lite or Advanced, to a v2 plan. You must create a new v2 plan, and then move your data to the new service instance. While you migrate your data from v1 to v2, you will likely have both a v1 and v2 instance deployed at the same time. Consider using the 30-day no charge trial that is available with your first Plus plan instance during this time.







 Collecting metrics 

Make a note of the following information so you can compare it to your service instance data after the migration:



* Number of collections
Instances created after this date are associated with a resource group instead.





New Standard plan instances are provisioned into resource groups. In order to create these instances onto a Dedicated Hardware instance, the Dedicated Hardware instance must first be migrated into a resource group.

For more information about how to do this migration, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).

Once the Dedicated Hardware instance is migrated to a resource group, it appears in the Location drop-down menu when you create Standard plans.





In theory, instances can be migrated to resource groups in any order. The following order for Dedicated Hardware instances and the Standard plan instances that are hosted on them is recommended:



1. Migrate Dedicated Hardware instances to a resource group. This migration allows new Standard plan instances to be created on the Dedicated Hardware.
2. Migrate Standard instances.



Lite plan instances and Standard plan instances that are not hosted on Dedicated Hardware can be migrated at any time.



* How do I migrate an existing IBM Cloudant instance to a resource group?

You can migrate IBM Cloudant instances on the following plans:



* Lite
* Standard
* Dedicated Hardware



To migrate an IBM Cloudant instance from a Cloud Foundry space to a resource group, see [Migrating Cloud Foundry service instances and apps to a resource group](https://cloud.ibm.com/docs/account?topic=account-migrate).
* How much downtime occurs when you migrate an instance to a resource group?

The migration process doesn't cause any downtime.
* Why do some instances have an organization and space and others don't?

Since 16 July 2018, new instances are provisioned into resource groups rather than Cloud Foundry spaces. Resource instances created before this date have an associated Cloud Foundry organization and space. Instances created after this date are associated with a resource group instead.
* Why can't I create new Standard plan instances on my Dedicated Hardware instances?

New Standard plan instances are provisioned into resource groups. In order to create these instances onto a Dedicated Hardware instance, the Dedicated Hardware instance must first be migrated into a resource group.
Service plans 

This topic includes information about the IBM Cloud Monitoring service plans.

When you provision an instance of the Monitoring service, you can choose any of the following service plans:



Table 1. Service plans

 Plans                                       Plan ID                                 Plan Name                                   

 Lite                                        367a3918-9efc-43c5-bef9-20553051b7af    lite                                        
 Graduated tier                              231bb072-1b2f-4d7e-ae9e-9574d382be32    graduated-tier                              
 Graduated Tier - Sysdig Secure + Monitor    35784193-e918-42d9-9598-4e842ed75192    graduated-tier-sysdig-secure-plus-monitor   



You can provision a Monitoring instance with the Lite service plan to try out the Monitoring service for free for 30 days.

The Graduated tier service plan includes features that you can use to gain operational visibility into the performance and health of your applications, services, and platforms. It offers administrators, DevOps teams and developers full-stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.

The Graduated Tier - Sysdig Secure + Monitor service plan includes the same features that are available through the Graduated tier service plan and the [IBM Cloud Security and Compliance Center Workload Protection](https://cloud.ibm.com/docs/workload-protection) service that you can use to protect, monitor, and enhance forensic analysis of your pipeline and runtime components. Combining the monitoring features and the security features, DevOps teams can quickly troubleshoot, analyze, and perform forensics on an incident.
You cannot use an instance on the Lite plan to receive streamed data. This plan has a 0-day retention period.



 Features by plan 

The following tables outline the different features that are included in each service plan:



Table 2. List of features available for each service plan

 Feature HIPAA 30 day log search plan 30 day log search plan 14 days log search plan 7 days log search plan Lite plan 

 Live streaming tail ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/checkmark-icon.svg) 
 Customizing the logging agent !