vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Support subscription credit is separate from any platform or service subscription credit in your account and can't be spent on resource usage. For more information, see [How subscription credit is spent](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscriptionssubscription-basics).





 Service bundle subscriptions 

Service bundle subscriptions give you access and credit toward a set of services within a particular domain that are targeted for popular use cases. You can choose from service bundles that span AI, analytics, IBM Blockchain, Internet of Things (IoT), and cloud-native services. If your needs cross multiple domains, you can purchase multiple service bundle subscriptions.

You can add services bundles to any type of existing account, including Lite accounts. Service bundle subscriptions are subject to the [IBM Cloud Terms of Use](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).

Service bundle subscriptions aren't available through the IBM Cloud console. To learn more and purchase a service bundle, contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule).

After you purchase a service bundle subscription, you'll receive an email with a subscription code that you apply to add the bundle to your account. For more information about how to apply subscription codes, see [Subscription credit](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscriptionssubscription-codes). When your service bundle expires or you use all of the credit, you can continue to use any of the services, with usage charged at the Pay-As-You Go rate.





 Expiring subscriptions 

When your subscription is about to expire, you are notified by email 60, 30, 14, and 1 day before the expiration date of the last subscription on the account. After your subscription expires, your account is converted to a Pay-As-You-Go account, which means you pay only for billable services that you use with no contracts or commitments.
The IBM Cloud push service has two components to pricing: a destination instance fee and a consumption price.

A pre-production destination instance fee is charged monthly. Every pre-production destination added to your Event Notifications instance incurs the fee.

Consumption: Only 500 devices or 5000 outbound digital messages is permitted per pre-production destination. If either the number of devices or the number of outbound digital messages exceeds the permitted limit, the permitted number of devices is moved by additional 500 devices or by additional 5000 messages and charged.

For example, if you tried to send 5001th message, the message cap automatically is raised to 10000 (another 5000 messages are added) for the month and the device cap is raised to 1000 (another 500 devices are added) per month. Notice that both limits are always raised even if only one cap has been exceeded.





 Push charges for changing from pre-production destination to production destination 

You can change a pre-production destination to a production destination at any particular time and the charges are calculated accordingly.

The push service has two components to pricing: a destination instance fee and a consumption price.

A pre-production destination instance fee is charged monthly. Every pre-production destination added to your Event Notifications instance incurs the fee.

A production destination instance fee is also charged monthly and allows unlimited devices and outbound messages.

If you change a pre-production destination to a production destination, the charges for the transition month would be the pre-producdtion fee + pro-rated charge for the production instance.

For example, assume the pre-production instance fee is $15 per month and the production instance fee is $50 per month.

These prices are assumed for this example only. Current pricing may be different from the amounts shown in the example. See the Event Notifications catalog page for current pricing.



* As of 31 July, you create a pre-production destination and does not register any devices or send messages, the charges for July will be $15.
* As of 1 August, you register 500 devices and 5001 messages sent. The charges for August will be $30 (This is due to the message threshold exceeds the permitted limit.)
* As of 5 August, you change from pre-production destination to production destination.
When you register with IBM Cloud, you get a Pay-As-You-Go account, and you receive a [$200 credit](https://cloud.ibm.com/docs/account?topic=account-upgrading-account) to help get you started. You can use the $200 credit on IBM Cloud products.

Your resource usage consists of recurring and fluctuating costs. If you purchase classic infrastructure services, you're billed on an hourly or monthly recurring basis in advance of use, like a rent bill. If you purchase platform services, your invoice fluctuates as your resource usage fluctuates, similar to a utility bill. You will receive invoices for recurring resources in your account until you cancel them. Turning a resource "off" does not cancel the resource in your account. See [Cancelling your billing items](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-cancel-billing-items) for more information.

You can create multiple resource groups to easily manage quota and view billing usage for a set of resources. Your charges are based on your use of IBM Cloud computing and services. If you use more than the free runtime and service allowances, you receive a monthly invoice that provides details about your resource charges. You can [set up spending notifications](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-spending) to get notified when your account or a particular service reaches a specific spending threshold that you set.

Basic support is included with your IBM Cloud Pay-As-You-Go. It is provided for non-production environments or workloads where traditional severities are not used and specific response times are not stipulated. Also, with a Pay-As-You-Go account, you can order Advanced or Premium support plans to get extra help with your production workloads. Learn more in [Basic, Advanced, and Premium Support plans](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans).

A subset of Pay-As-You-Go accounts are eligible for the new Enterprise Savings Plan billing model.
Using Cloud Functions 

With [IBM Cloud® Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-started), you can use your favorite programming language to write lightweight code that runs app logic in a scalable way. You can run code on-demand with HTTP-based API requests from applications or run code in response to IBM Cloud services and third-party events, like updates made to a bucket. The Function-as-a-Service (FaaS) programming platform is based on the open source project Apache OpenWhisk.

This feature is not currently supported in Object Storage for Satellite. [Learn more.](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-about-cos-satellite)



 Using Object Storage as an event source 

Cloud Functions is an event-driven compute platform (also referred to as Serverless computing). Actions (small bits of code) run in response to triggers (some category of event), and rules associate certain actions with certain triggers. Configure IBM Cloud® Object Storage to be an event source, and anytime an object in a particular bucket is written or deleted an action is triggered. You can further tailor the changes feed to only corral events for objects which match a particular prefix or suffix.



1. Set the option to allow Cloud Functions [access](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_ev) to listen for changes that are made to your bucket. This involves creating a service-to-service [authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauth), and uses the new [Notifications Manager](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_auth) IAM role.
2.
The detailed [pricing plan](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services) is available for your reference.

The following example shows a total charge of 30 days (720 hours). The user enables two operational crypto units in the service instance, and creates 22 internal keystores and 15 external keystores. The first 5 internal keystores and the first external keystore are free of charge.



Table 2. A Unified Key Orchestrator billing example of 30 days

 Pricing components Cost for 30 days (720 hours) 

 Operational crypto unit 1 $1533.6 (30x24x2.13) 
 Operational crypto unit 2 $1533.6 (30x24x2.13) 
 22 internal keystores $3795 (5x0+15x225+2x210) 
 15 external keystores $980 (1x0+14x70) 
 Unified Key Orchestrator connection $3600 (30x24x5.00) 
 Total charge $11442.2 



* Is there a free trial for Hyper Protect Crypto Services?

If you have a [promo code](https://www.ibm.com/cloud/hyper-protect-crypto), you can [apply your promo code](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-applying-promo-codes) and get two crypto units at no charge for 30 days.
* How can I manage user access to my service instances? Does IBM have access to my instances?

IBM or any third-party users do not have access to your service instances or your keys. By loading the master key to your service instance, you take the ownership of the cloud HSM and you have the exclusive control of your resources that are managed by Hyper Protect Crypto Services.

Hyper Protect Crypto Services follows the IBM Cloud Identity and Access Management (IAM) standard.
Getting started with IBM Cloud Functions 

With IBM Cloud® Functions, you can use your favorite programming language to write lightweight code that runs app logic in a scalable way. You can run code in response to HTTP-based API requests from applications or run code in response to IBM Cloud services and third-party events. The Function-as-a-Service (FaaS) programming platform is based on the open source project Apache OpenWhisk.



 Working with actions 

With IBM Cloud® Functions, you can create stateless code snippets, called actions, that are set to perform one specific task. To learn more about actions and other Functions terms, see [terminology](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-about).

Click an option to get started.



* [Create an action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgs_hello_world).
* [Set up the Cloud Functions CLI plug-in](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_install).
* [See the platform architecture](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-about).







 Creating an action in the console 

To get started with Cloud Functions, try creating the Hello World quick start template.



1. Create an [IBM Cloud](https://cloud.ibm.com/registration) account or log in to an existing account.
2. Navigate to the [Cloud Functions dashboard](https://cloud.ibm.com/functions).
3. Select a [namespace](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces).
4. Click Start Creating > Quickstart Templates and select the Hello World template.
5. Create a package for your action by entering a unique name in the Package Name field.
6. Select a runtime for your action.
* IBM Cloud Services Agreement (local country version*) for Lite accounts, non-US Dollar credit card billing, or if you select invoicing from IBM, available at [https://www.ibm.com/support/customer/csol/terms/](https://www.ibm.com/support/customer/csol/terms/) (select your country);
* SoftLayer Cloud Service Agreement for US Dollar credit card billing, available at

[https://www.ibm.com/support/customer/csol/terms/?cat=softlayer#detail-document](https://www.ibm.com/support/customer/csol/terms/?cat=softlayerdetail-document)
* IBM Passport Advantage Agreement you accepted upon registration and the General Terms for Cloud Offerings TOU for IBM Passport Advantage Clients, available at [http://www.ibm.com/terms/?id=i126-5948](http://www.ibm.com/terms/?id=i126-5948) ; or
* Cloud Trial Agreement for Proof of Concept (POC) Accounts available at [http://www.ibm.com/terms/?id=i126-5948](http://www.ibm.com/terms/?id=i126-5948) ; POC accounts may be provided for assessment of specific services, solutions or both. Use of services beyond the intended scope of POC might be possible, but might be subjected to additional charges.
* An equivalent cloud service base agreement terms signed between you and IBM



Applicable Additional SDs for any service ordered using your IBM Cloud account are available at [https://www.ibm.com/terms/?id=i126-6605](https://www.ibm.com/terms/?id=i126-6605) . The additional SDs contain links to the applicable Data Sheet for each service.





 Exchange Rate Policy 

Effective 1 February 2023, IBM Cloud will adjust the exchange rates used to provide pricing in non-US dollar currencies on a monthly basis. Charges for cloud services are based on US dollars.
Remember, if you don't need your app live on IBM Cloud, stop the app so you don't incur any unexpected charges.





 Next steps 

[Manage your Node.js app](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-nodejs_runtime). Some example tasks include configuring caching and integrating third-party services.

Check out the following resources:



* [Samples](https://ibm-cloud.github.io)
* [Architecture Center](https://www.ibm.com/cloud/architecture/architectures)
Getting started with IBM Cloud Functions 

With IBM Cloud® Functions, you can use your favorite programming language to write lightweight code that runs app logic in a scalable way. You can run code in response to HTTP-based API requests from applications or run code in response to IBM Cloud services and third-party events. The Function-as-a-Service (FaaS) programming platform is based on the open source project Apache OpenWhisk.



 Working with actions 

With IBM Cloud® Functions, you can create stateless code snippets, called actions, that are set to perform one specific task. To learn more about actions and other Functions terms, see [terminology](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-about).

Click an option to get started.



* [Create an action](https://cloud.ibm.com/docs/openwhiskgs_hello_world).
* [Set up the Cloud Functions CLI plug-in](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_install).
* [See the platform architecture](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-about).







 Creating an action in the console 

To get started with Cloud Functions, try creating the Hello World quick start template.



1. Create an [IBM Cloud](https://cloud.ibm.com/registration) account or log in to an existing account.
2. Navigate to the [Cloud Functions dashboard](https://cloud.ibm.com/functions).
3. Select a [namespace](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces).
4. Click Start Creating > Quickstart Templates and select the Hello World template.
5. Create a package for your action by entering a unique name in the Package Name field.
6. Select a runtime for your action.
IBM Cloud Functions 

A Cloud Functions represents a service destination, where an incoming notification can be consumed programmatically to actions.



 Generate IBM Cloud Functions endpoint 

To post a Cloud Functions notification, you need to generate an endpoint. To generate the endpoint, follow these steps:



1. Create a [IBM Cloud Functions](https://cloud.ibm.com/functions/create) instance. If you already have an Cloud Functions instance, go to step 3.
2. Create a Namespace. For more information, see [here](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespacescreate_iam_namespace).
3. Create an Action. For more information, see [here](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions).
4. Select Endpoints from the left menu.

Make sure to uncheck Enable as Web Action and Raw HTTP handling options in the Web Action section for an effective usage of Cloud Functions as a destination.
5. Copy the URL mentioned and use it in Destination Configuration in Event Notifications instance.







 Generate API key for your namespace 



1. From your IBM Cloud dashboard, go to Manage > Access (IAM).
2. Select Service IDs.
3. Select your namespace.
4. Select API keys.
5. Unlock if the API key is locked by going to Actions > Unlock.
6. Click Create and provide a Name. This gives you the apikey for the namespace you selected.
7. Copy api_key and use it in Destination Configuration in Event Notifications instance.



IBM Cloud Functions Cloud Foundary based namespace is not supported. Only IAM-based namespace is supported.





 Configuring a Cloud Functions destination 

You can configure a Cloud Functions destination in the Destinations tab.

To configure a Cloud Functions destination, do the following steps:



1. From your Event Notifications instance dashboard, click Destinations.
Migrate your apps from IBM® Push Notifications for IBM Cloud® service to IBM Cloud® Event Notifications 

You can migrate your mobile apps from the deprecated IBM Cloud Push Notifications service to Event Notifications to continue to use Push.



 Introduction 

Event Notifications is a routing service that tells you about critical events that occur in your IBM Cloud account. You can filter and route IBM Cloud® Event Notifications from IBM Cloud services like Monitoring, Security and Compliance Center, and Secrets Manager to communication channels like email, SMS, push notifications, and webhooks.

This guide outlines the steps to migrate your mobile apps and the backend to integrate with the Event Notifications service.

Take the following steps to migrate your mobile apps:



* Create and configure an instance of IBM Cloud® Event Notifications
* Modify your Android or iOS mobile app to work with the Event Notifications service
* Modify your backend to integrate with the new API of the Event Notifications service
* Release the new version of the mobile app







 Step 1: Create and configure an instance of the Event Notifications service 

Create an instance of the Event Notifications service. This procedure does not use any advanced capabilities of the Event Notifications service. Within the service, you create an API source, a topic, a subscription, and a destination as outlined in figure 1.

For a more detailed explanation of the concepts of Event Notifications, see [Getting started with IBM Cloud® Event Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-getting-started).

Zoom

![Push capability in Event Notifications](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-how-push-en.png)

Figure 1. Push capability in Event Notifications



 Create a source 

Create an API source. This source represents the backend from which you send the notifications.





 Create a topic 

Create a topic where all the events from the backend flow into.
: Server SDK: You can protect your back-end resources that are hosted on IBM Cloud and your web apps by using the server SDK. It extracts the access token from a request and validates it with App ID. Client SDK: You can protect your mobile apps with the Android or iOS client SDK. The client SDK communicates with your cloud resources to start the authentication process when it detects an authorization challenge.

IBM Cloud
: App ID: After successful authentication, App ID returns access and identity tokens to your app. Cloud Directory: Users can sign up for your service with their email and a password. You can then manage your users in a list view through the UI. With Cloud Directory, App ID functions as your identity provider.

External (third party)
: Social and enterprise identity providers: App ID supports Facebook, Google+, and SAML 2.0 Federation as identity provider options. The service arranges a redirect to the identity provider and verifies the returned authentication tokens. If the tokens are valid, the service grants access to your app.





 Integrations 

You can use App ID with other IBM Cloud offerings.

Kubernetes Service
: By configuring Ingress in a standard cluster you can secure your apps at the cluster level. Check out the [App ID authentication Ingress annotation](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsapp-id-authentication) or the [Announcing App ID integration to IBM Cloud Kubernetes Service](https://www.ibm.com/cloud/blog/announcing-app-id-integration-ibm-cloud-kubernetes-service) blog post to get started.

Cloud Functions and API Connect
: When you create your APIs with [Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-started) and [API Connect](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-getting-started), you can secure your applications at the gateway rather than in your app code.

Activity Tracker
Binding IBM Cloud services to Cloud Functions entities 

You can incorporate functionality from IBM Cloud services in your IBM Cloud® Functions app.

How do I add IBM Cloud services to my app?
: 

1. You can hardcode REST API calls into your app. This option might be the quickest way to communicate with an IBM Cloud service.
2. You can use a preinstalled or installable package to incorporate functionality. You can use the actions and feeds that are stored in the packages within your app code. This option might slim down your code a bit, which might be useful if your app is close to the system limits.



How do I set up parameters that must be accessed by my app?
: These parameters might include values that make your app reusable with different data or they might include values that are required by the service, such as credentials.
: 

1. You can hardcode parameters into your app. This option might not be the most secure way of storing confidential information such as credentials.
2. You can bind the parameters to your app by binding them to an action or package.



: Parameters for each package are available in the package descriptions, which you can find in the Integrating serverless apps section of the documentation.



 Binding a service to an action or package 

Bind any IBM Cloud service to any action. When a service is bound, a new parameter is created on your existing action that contains the service instance credentials.

You can bind only one instance of a service at a time and you cannot bind multiple instances of the same service to an action or package. You can bind a service to an individual action or you can bind a service to a package and then all actions that are contained in that package are bound to that service.

Before you begin, [create an action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actions) and [define credentials](https://cloud.ibm.com/docs/account?topic=account-externalappexternalapp) for the service that you want to bind to the action.



1. Get the list of available service keys of services that you want to bind to an action or package.