vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Pricing 

Different service plans are available for IBM Cloud Security and Compliance Center Workload Protection.

The following service plans are available:



Table 1. Service plans

 Plans             Plan ID                                 Plan Name        

 Free Trial        0eae605c-7258-4bb7-8cb7-a4b96d5c94c3    lite             
 Graduated tier    00497f9a-f093-436b-98d7-c81845399516    graduated-tier   



A Free Trial IBM Cloud Security and Compliance Center Workload Protection instance expires after 30 days. In a Graduated tier plan, data is accessible and retained for 90 days.



  Estimating your cost 

Cost is $0.07639 for each node hour.

To estimate your approximate cost, use the following formula.

Number of agents x hours the agents run in a day x the number of days in a month x $0.07639

For example, if you are running one agent for 24 hours a day and the month has 30 days, the estimated cost is approximately $55.

1 x 24 x 30 x $0.07639
See this topic on [Billing](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-billing) for more details about how IBM Blockchain Platform billing works.







 Choose your deployment process 

From your IBM Cloud account, you can deploy the IBM Blockchain Platform service from either the IBM Cloud Catalog or the Red Hat Marketplace.



* IBM Cloud Catalog Use the IBM Cloud Catalog to deploy blockchain to an IBM Kubernetes service or OpenShift cluster in IBM Cloud. With thissoftware-as-a-serviceoption, IBM manages the maintenance and the updates to the console for you, but you can choose when to update your blockchain components.
* Red Hat Marketplace OpenShift customers who are already familiar with the OpenShift Container (OC)CLIand the Red Hat Marketplace may prefer to use this option. Note that with this option, you are responsible for the maintenance of your console and blockchain components.
* Multicloud Not running an OpenShift or Kubernetes cluster in IBM Cloud? The IBM Blockchain Platform 2.5.4 can be installed on your OpenShift or Kubernetes cluster in your cloud or on-prem. With this option as well, you are responsible for the maintenance of your console and blockchain components.
Enhance security of your deployed application 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

You already developed and deployed an application on IBM Cloud. You already followed the [introductory tutorial on how to apply end to end security to an application](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-cloud-e2e-security). Following "security by design", you now start to look into the design of a new application, or you need to adapt an older application to new security requirements. This tutorial walks you through options for applications with advanced security requirements. It looks into enhanced data encryption, isolation of compute runtimes and network traffic, and by using activity logs to look for suspicious activities.



 Objectives 



* Learn about enhanced data encryption options.
* Isolate your application runtimes for extended security.
* Evaluate your app to find and address security and compliance issues.



An existing solution with the application and connected (micro-) services is extended for enhanced security.

Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution51-extended-app-security/extended-app-security.svg)

Figure 1. Architecture diagram of the tutorial





 Assess your application 

You developed a solution and successfully deployed it to IBM Cloud. Now you want to look into how to harden the app environment. This can be part of the regular activities of (agile) development and the next steps towards a fully secure app or by increasing requirements for an app already in production.

If you tried the tutorial on how to [apply end to end security to a cloud application](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-cloud-e2e-security), you already know how to rotate service credentials.
Getting started with App Connect 

Service plans for IBM® App Connect in IBM Cloud® have been deprecated, and any instances of App Connect plans that still exist on 30 November 2023 will be deleted. To continue using IBM App Connect, you should migrate to an alternative provision. For more information, see [Deprecation of IBM App Connect on IBM Cloud service plans](https://cloud.ibm.com/docs/AppConnect?topic=AppConnect-index).

In this getting started tutorial, we'll take you through how to use IBM® App Connect in IBM Cloud® to create an event driven flow that will take you about 10 minutes to implement. If you’re an existing IBM® App Connect in IBM Cloud® user, you can continue to use the service until it is no longer supported on 30 November 2023.

As the name suggests, an event-driven flow consists of an event in a source application, which triggers the flow, and one or more actions in target applications. So when something happens in the source application, an action is triggered in your target applications. To create an event-driven flow that connects your cloud-based applications, complete the following steps.



 Before you begin 

Create an instance of the IBM® App Connect service, to launch App Connect.





 Step 1: Create an event-driven flow 



1. On the App Connect dashboard, click New > Event-driven flow. App Connect saves your changes automatically as you go. If you navigate away from the flow at any stage, the flow is saved as a draft flow that you can complete at another time.
2. Enter a name for your flow.







 Step 2: Select a trigger 



1. Select the trigger event to start your flow by expanding an application and selecting an event.
2. If you're not already connected to your application, click Connect and enter your login details for the application. You might have to provide extra connection details for some applications; if you need help with finding credentials for a particular application, see the [How-to guides for apps !
[Enter the United Nations Standard Products and Services Code (UNSPSC)](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infoservice-unspsc)
4. [Add a paid pricing plan](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infoadd-plan-paid)
5. [Confirm the digital platform reseller agreement](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infodra)







 Adding metrics to your pricing plan 

If you offer a paid integrated product and add a paid pricing plan that requires customers to pay for their usage, you must add metrics to your pricing plan to aggregate your product's usage. After you add metrics to your plan, you must request an initial metering approval, so you can submit your resource usage and start reviewing your metrics.

To add metrics to your pricing plan, complete the following steps:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select the product that you're onboarding, and click Pricing.
3. Select a usage-based plan from the table and click Add metrics.
4. In the Usage metrics section, click Add metrics.
5. Complete the required fields.
6. Click Done.
7. To submit your pricing plan and metering for review, click Request approval in the Metering approval section.







 Submitting resource usage to the IBM Cloud Usage Metering API 

To review how customers understand and experience your pricing plan, and validate that your metered plans are correctly configured, you must submit your resource usage. Submitting your resource usage includes creating your metering JSON, calling the Usage Metering API, and providing the evidence of your testing.
Applying feature codes 

You can apply feature codes to take advantage of extra IBM Cloud® resources or capabilities. Feature codes are typically provided for online courses and certain events, such as educational sessions or conference workshops.

Are you looking for details about adding subscription credit to your account? See [Managing subscriptions](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-subscriptions) for more information.

You must have the Editor role or higher for all account management services to apply a feature code. The extra resources or capabilities that are provided vary depending on the particular code but include one or more of the following items in general:



*  Increase the memory quota to a number of GB that is specified by the code
*  Add one organization with a memory quota that is specified by the code
*  Add an unlimited number of organizations
*  Upload an extra number of SSL certificates, as specified by the code
*  Use premium service plans
*  Convert a Lite account to a trial account, which provides access to more services but only within a limited trial period



Complete the following steps to apply a feature code to your existing account:

If you don't have an account yet, you can add your feature code when you [register](https://cloud.ibm.com/registration) for a new account by clicking Register with a code instead of entering your credit card information.



1.  In the IBM Cloud console, go to Manage > Account, and select Account settings.
2.  Click Apply code.
3.  Enter the feature code, which is typically a random alphanumeric value such as a1b2c3def456.
4.  Click Apply.
For more information, see the [Cloud Functions CLI reference](https://cloud.ibm.com/docs/openwhisk?topic=cloud-functions-cli-plugin-functions-cli).





 API Authentication and Host 

With the Cloud Functions CLI plug-in, you don't need to explicitly configure the API key and API host. Instead, you can log in with the ibmcloud login command. You can target an IAM-enabled namespace by running ibmcloud fn property set --namespace <namespace_name_or_ID> or a Cloud Foundry-based namespace by running ibmcloud target --cf. After you log in, all commands begin with ibmcloud fn.

If you need to use the authentication API key for Cloud Functions in an external HTTP client such as cURL or Postman, you can retrieve it with the following commands.



* Get the current IAM tokens. You must pass the IAM token in the Authorization header.

ibmcloud iam oauth-tokens
* Get the current Cloud Foundry API key by running the following command.

ibmcloud fn property get --auth
* Get the current API host by running the following command.

ibmcloud fn property get --apihost



The API key is specific per region, organization, and space targeted by the Cloud Functions CLI plug-in. The IBM Cloud® Functions web actions API endpoint changed. To align with other customer services, a new functions.appdomain.cloud API endpoint is available for web actions. The API endpoint functions.cloud.ibm.com is still active, but now returns response data as content type text/plain instead of text/html. Other content types are not changing. Migrate your web actions to use the new API endpoint. The previous endpoints are deprecated and will be deactivated at some point.





 Migrating deployment scripts 

If you have scripts that use the OpenWhisk CLI with the wsk commands, all commands work the same way by using the command ibmcloud fn.
You can choose to receive email notifications about IBM Cloud platform-related items across your account. When you set IBM Cloud platform notifications, you receive email notifications that are associated with only the platform. You do not receive email notifications about events that are associated with IBM Cloud services.

Your platform email notifications settings are tied to your account.



* To stay up to date with changes to the IBM Cloud platform and products, go to Notification preferences > Announcements. To select a subcategory, set Emails to the on position.
* To receive notifications about invoices, payments, subscription and promo codes, or spending and usage warnings, see Billing and usage. Then, click Manage in the IBM Cloud console to set up spending notifications.
* To receive updates about the status of your infrastructure orders, select Ordering.
* To manage the notification distribution list in regard to your account, subscriptions, security and compliance alerts or marketing communications, click Additional notification preferences > Manage in the IBM Cloud console.
* By default, all IBM Cloud platform notifications are turned off.



To quickly turn off emails for the selected account or for all other accounts, click Actions, and select your preference.





 Setting resource notifications 

You can set your preferences to receive resource-related notifications for incidents, maintenance, security bulletins, and resource activity updates.



1. In the console, go to the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Profile.
2. Click Notification preferences > Resource.
3. Select from the following options:



* Receive notifications about events that can cause an outage or restrict functionality. You can receive notifications for all incident severity levels (1, 2, 3, 4) or just a subset.
* Receive notifications about any important maintenance that keeps the platform operating at optimal status. You can receive notifications for all impact levels (high, medium, low), or just a subset.
With the BYOL pricing model, IBM Cloud doesn't charge users for the usage of the software, and third-party providers are responsible for licensing entitlement and enforcement.

For the purposes of this tutorial, complete the following steps to add a BYOL pricing plan.



1. Click Pricing > Pricing plans.
2. Click Add plan > BYOL.
3. Enter the name, URL, and description of the license, for example:



* Name: BYOL for Example Corp Terraform template 1.0.0
* URL: byol.terraformtemplate.examplecorp.html
* Description: This BYOL license is required for the installation and use of the Example Corp Terraform template.









 Step 5: Define your support experience 

Provide details that help users understand how to get support if they encounter issues when they use the Operator bundle. For more information about providing support information, see [Defining your support experience](https://cloud.ibm.com/docs/sell?topic=sell-sw-support-details).

To define your product's support experience, use the following steps:



1. Click Support.
2. Select your product's support provider and complete the support statement field. For the support statement, describe the provided support for your product and add any additional support information that isn't provided in the other fields.



1. If you select Community for your support provider, provide the URL for the support community.
2. If you select Third-party for your support provider, use the following steps to complete the necessary fields.



3. Click Add support details and complete the necessary fields, then click Save to add each detail. You must add at least 1 support detail for your product.
4. After you add all of your product's support details, provide the required URLs for your product.
5. Add all locations where you provide support for your product.
6. Add your escalation information. Do not use a personal phone number or email.
7. Provide your support contact information. This information is for internal use only and is not displayed on the product details page.







 Next steps
The Premium plan offers developers and organizations all of the capabilities and features of the Plus plan. The plan also offers these additional features:



* The ability to use IBM Watson® services in the IBM Cloud® with data isolation and added security features such as IBM® Key Protect for IBM Cloud® (also referred to as Bring your own keys (BYOK)), Service Endpoints, Mutual Authentication, and US Health Insurance Portability and Accountability Act (HIPAA) readiness.
* Significantly greater capacity of up to 500 concurrent transcriptions with the option to add more, far above the limit of 100 concurrent transcriptions for the Plus plan.
* Your first 150,000 minutes of speech recognition each month at no charge.



To learn more or to make a purchase, [contact an IBM representative](https://ibm.biz/contact-wdc-premium).
* Can I provision a premium instance right now?

No, you must first contact your IBM sales representative to purchase an entitlement and share your requirements. To make a purchase, [contact an IBM representative](https://ibm.biz/contact-wdc-premium).
* How do I access my service credentials?

How you access your service credentials depends on whether you are using Speech to Text with IBM Cloud® or IBM Cloud Pak® for Data. For more information about obtaining your credentials for both versions, see [Before you begin](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-gettingStartedgetting-started-before-you-begin) in the getting started tutorial.

Once you have your service credentials, see the following topics for information about authenticating to the service:



* [Authenticating to IBM Cloud](https://cloud.ibm.com/docs/watson?topic=watson-iamgs-credential-cloud)
* [Authenticating to IBM Cloud Pak for Data](https://cloud.ibm.com/docs/watson?topic=watson-iamgs-credential-cpd)



* What languages does the service support?

The Speech to Text service supports both previous-generation and next-generation languages and models.
[Create a destination](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-destination) so that your alerts can be forwarded to the Cloud Functions webhook that you created the previous step.



1. From the navigation, click Destinations > Add.
2. Provide a name for your destination. For example, GitHub.
3. Select Webhook as the destination type.
4. Paste the URL that you copied from the Cloud Functions UI.
5. From the list of HTTP verbs, select POST.
6. Click Add.



After you create your destination, copy your destination ID. You use this value to prepare your Functions code in a later step.







 Enable webhook signing 

By default, the notification content that is delivered to a webhook URL arrives in raw JSON format. Event Notifications can optionally send notifications as signed JSON Web Tokens (JWT). In this step, you enable signing for the webhook subscription that you created in part 1.

With webhook signing, you verify that the notification payload is sent by Event Notifications and not by a third party. For more information, check out the [Event Notifications documentation](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-webhooken-webhook-sign).



1. [Create a subscription with signing enabled](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-subscription) between your existing Secrets Manager topic and your new Cloud Functions destination.



1. In the Event Notifications UI, click Subscriptions > Create.
2. Provide a name for your subscription. For example, GitHub.
3. Select the Secrets Manager topic that you created in part 1.
4. Select the destination that you created in the previous step.
5. In the Security section, select the Signing enabled option.
6.
Prepare Your IBM Cloud Account 



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/7f09c1b3f21dd05ddc2c4638a3dc66976ad73e53/vmware-classic-journey/images/solution-vmware-onboarding-hidden/prepare-account/journey-map.png)





 Enabling Virtual Routing and Forwarding with Service Endpoints 

The deployment of VMware on IBM Cloud requires Virtual Routing and Forwarding (VRF) to be enabled on your cloud account. VRF enables your account with the required routing tables and allows the use of IPs that normally would not be allowed. Additional details on VRF can be found within the [documentation](https://cloud.ibm.com/docs/direct-link?topic=direct-link-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud).

Enabling service endpoints allows your workload running on VMware to communicate with IBM Cloud Services over the IBM Cloud private network (i.e. VMware workload communicating with Redis, IBM Log Analysis, etc.) In addition, there is no billable or metered bandwidth charges on the private network. In order to benefit from service endpoints, VRF must first be enabled.

The steps you should follow are described in the following sections within the IBM Cloud Documentation:



* [Enabling VRF in the Console](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint&interface=uivrf)
* [Enabling Service Endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint&interface=uiservice-endpoint)



If you are working on a brand new IBM Cloud Account, you will most likely find this feature will need to be enabled. If you are working in a cloud account which has been established and running workload, it's common to find this feature has already been enabled.





 Configure IAM
* Who has access to my project?

Any user that is a member of your account that is assigned access to the IBM Cloud Projects service, Schematics, and the resource group for your project can access your project.



Selling on IBM Cloud



* What are the different metering options for plans?

IBM Cloud® supports multiple models for aggregating service usage. Service providers measure various metrics on the created instances and submit those measures to the metering service. The rating service aggregates the submitted usage into different buckets (instance, resource group, and account) based on the model that service providers choose. The aggregation and rating models for all the metrics in a plan are contained in the metering and rating definition documents for the plan.

You're required to automate hourly usage submission by using the metering service API if you offer a metered plan.

For more information on metering, see [Metering integration](https://cloud.ibm.com/docs/sell?topic=sell-meteringinterameteringintera). For more information about submitting metered usage, see [Submitting usage for metered plans](https://cloud.ibm.com/docs/sell?topic=sell-submitusagesubmitusage).
* How do I receive payments for my services?

Third-party services that offer paid usage-based pricing plans receive disbursements through an Electronic Funds Transfer (EFT). To set up this method to receive disbursements in IBM Cloud Partner Center Sell, you must submit the EFT form when you set up your first usage-based pricing plan. You can download the form from the Payments to me page.
* When are disbursements sent to me?

If any disbursements are due to a third-party provider, they are sent on the last business day of the second calendar month. For example, March activity would be paid on the last calendar day of May, unless the last day of the month falls on a weekend or holiday. In this case, disbursements are sent on the next business day. Disbursements are calculated from beginning of the month to the end of the month.
* What is the fee structure?