vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Resource sharing across accounts](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-resource-sharing)Resource sharing across accounts

This tutorial walks you through different options on how to share cloud-based resources across accounts.

Virtual Private Cloud (VPC) Log Analysis

+6

Activity Tracker hosted event search,Secrets Manager,App ID,Key Protect,Hyper Protect Crypto Services,Object Storage



* 1 hour
* 2023-05-05



[Install software on virtual server instances in VPC](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-app-deploy)Install software on virtual server instances in VPC

This tutorial walks you through provisioning IBM Cloud® Virtual Private Cloud (VPC) infrastructure and installing software on virtual server instances (VSI) using Infrastructure as Code (IaC) tools like Terraform and Ansible.

Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-05



[Provision Bare Metal Servers for VPC for VMware deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-bms)Provision Bare Metal Servers for VPC for VMware deployment

This tutorial will show how to provision Bare Metal Servers for VPC into IBM Cloud VPC, and how to provision network interfaces for vSphere VMkernel adapters (VMK) adapters.

VMware Solutions Virtual Private Cloud (VPC)



* 1 hour
* 2023-05-05



[Provision IBM Cloud VPC Subnets and configure Distributed Virtual Switch Portgroups for VMs](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-newvm)Provision IBM Cloud VPC Subnets and configure Distributed Virtual Switch Portgroups for VMs
Figure 1. IBM Cloud VPC Subnets for VMware Deployment





 Before you begin 

This tutorial requires:



* Common [prereqs](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-prereqs) for VMware Deployment tutorials in IBM Cloud VPC



This tutorial is part of series, and it is required that you follow the [order](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmwarevpc-bm-vmware-objectives).

[Login](https://cloud.ibm.com/docs/cli?topic=cli-getting-started) with IBM Cloud CLI with username and password, or use the API key. Select your target region and your preferred resource group.





 Step 1: Create a IBM Cloud VPC 



1. Create a IBM Cloud VPC, and record its ID and CRN.

VMWARE_VPC=$(ibmcloud is vpcc vmw --output json | jq -r .id)

VMWARE_VPC_CRN=$(ibmcloud is vpc $VMWARE_VPC --output json | jq -r .crn)

You can use the commands directly e.g. ibmcloud is vpcc ic4v without using the json output format and store the required values into variables manually, if you prefer this way.

All local variables used in this tutorial start with VMWARE_ and they are present within the current instance of the shell. If you want to collect them after for future use, you can use the following command.

( set -o posix; set; set +o posix ) | grep VMWARE_







 Step 2: Provision a Prefix 



1. Provision a prefix for the IBM Cloud VPC. In this example 10.97.0.0/22 is used in Zone eu-de-1.
This tutorial walks you through creating your own IBM Cloud VPC with multiple subnets as required to support vSphere networking and the provisioning of IBM Cloud Bare Metal Servers for Virtual Private Cloud (BMS) for a basic VMware vSphere deployment. After the IBM Cloud VPC and Bare Metal Servers for VPC have been provisioned, the tutorial covers a manual deployment of the vCenter, creating VMware compute cluster with vSAN or NFS shared storage options. The tutorial also covers optional features, such as using IBM Cloud VPC network for VMware Virtual Machine networking.

VMware Solutions Virtual Private Cloud (VPC)



* 8 hours
* 2023-05-05



[Public frontend and private backend in a Virtual Private Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-public-app-private-backend)Public frontend and private backend in a Virtual Private Cloud

This tutorial walks you through creating your own IBM Cloud® Virtual Private Cloud (VPC) with multiple subnets and a virtual server instance (VSI) in each subnet. A VPC is your own, private cloud on shared cloud infrastructure with logical isolation from other virtual networks.

Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-05



[Scale workloads in shared and dedicated VPC environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-scaling-dedicated-compute)Scale workloads in shared and dedicated VPC environments

Isolate workloads by provisioning a dedicated host, attaching an encrypted data volume to a VSI, expanding the attached data volume, and resizing the VSI after the fact.

Virtual Private Cloud (VPC) Databases For PostgreSQL

+2

Schematics,Object Storage



* 2 hours
* 2023-05-05



[Securely access remote instances with a bastion host](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-secure-management-bastion-server)Securely access remote instances with a bastion host
* By default, PFS (Perfect Forward Secrecy) is disabled for IBM Cloud VPN for VPC. Some vendors require PFS enablement for Phase 2. Check your vendor instruction and use custom policies if PFS is required.
* IBM Cloud VPN for VPC supports only one route-based VPN per zone per VPC.







 Creating a VPN gateway in the UI 

To create a VPN gateway using the UI:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) on the upper left of the page, then click VPC Infrastructure > VPNs in the Network section.

If starting from the VPC Infrastructure menu, click VPNs in the Network section to open the VPN for VPC page.
3. Ensure that the Site-to-site gateways > VPN gateways tabs are selected.
4. On the VPNs for VPC page, click Create and then select the Site-to-site gateway tile.
5. Specify the following information:



* VPN gateway name - Enter a name for the VPN gateway, such as my-vpn-gateway.
* Resource group - Select a resource group for the VPN gateway.
* Tags - Optionally, add tags to identify this VPN gateway.
* Access management tags - Optionally, add access management tags to resources to help organize access control relationships. The only supported format for access management tags is key:value. For more information, see [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial).
* Region - Shows the region where the VPC is located and where the VPN gateway will be provisioned.
* Virtual Private Cloud - Select the VPC for the VPN gateway.
* Subnet - Select the subnet in which to create the VPN gateway.
* ibmcloud is instance-template-create-override-source-template --source-template my-template --name my-instance --primary-network-interface '{"name": "primary-nic", "allow_ip_spoofing": true, "subnet": {"name":"my-subnet"}, "primary_ip": {"name": "my-reserved-ip"}, "security_groups": [{"name": "my-security-group-1"}, {"name": "my-security-group-2"}]}' Create instance template by overriding a source template with primary network interface configuration by using resource name.







 Command options 



* --source-template: ID or name of the template.
* --name: Name of instance template.
* --profile: Name of the instance profile.
* --zone: Name of the zone.
* --vpc: The ID or name of the VPC. It is only required to specify the unique resource by name that is inside this VPC or to override the VPC value in the template.
* --image: ID or name of the image.
* --catalog-offering: The CRN for the IBM Cloud catalog offering. If specified, the latest version of that offering is used. For more information about creating a catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --catalog-offering-version: The CRN for the version of a IBM Cloud catalog offering. For more information about creating a version for the catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --total-volume-bandwidth: The amount of bandwidth (in megabits per second) that is allocated exclusively to instance storage volumes. An increase in this value results in a corresponding decrease to total network bandwidth.
You can create a [classic VSI](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-getting-started-tutorial) or [VPC VSI](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
2. After you are connected to the VSI, target the private service endpoint when you send API requests to the Schematics API server. The following example shows the supported Terraform and Helm versions of the Schematics engine.

curl -X GET https://private-us-south.schematics.cloud.ibm.com/v1/version









 Virtual Private Endpoints Gateways for Schematics 

A service instance can have a private network endpoint, a public network endpoint, or both. After your account is enabled for VPC and you connect Schematics service on the private network from Virtual Private Endpoint Gateways.

- Public: A service endpoint on the IBM Cloud public network.
- Private: A service endpoint that is accessible only on the IBM Cloud private network with no access from the public internet.
- Both public and private: Service endpoints that allow access over both networks.

Virtual Private Endpoint Gateways is only supported for the VPC Generation 2.



 Before you begin 

Before you begin, to access the Schematics service through the Virtual Private Endpoint Gateways, ensure that you meet the following criteria:



* Make sure that you have the required [permissions](https://cloud.ibm.com/docs/schematics?topic=schematics-accessaccess-setup) to [create VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started), to create an endpoint gateway, to create or bind a reserved IP from the subnet, and [account limits for VSI creation](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasvpcquotas) for concurrent instances.
* A VPC Generation 2 instance and a subnet zones to bind an IP address at the same time you provision the endpoint gateway.
VPC: Why is no VPC available when I create a cluster in the console? 

Infrastructure provider: VPC

  What’s happening 

You try to create a VPC cluster by using the [Red Hat OpenShift on IBM Cloud console](https://cloud.ibm.com/kubernetes/catalog/create).

You have an existing [VPC](https://cloud.ibm.com/vpc) in your account, but when you try to select an existing Virtual Private Cloud to create the cluster in, you see the following error message:

No VPC is available. Create a VPC.

  Why it’s happening 

During cluster creation, the Red Hat OpenShift on IBM Cloud console uses the API key that is set for the default resource group to list the VPCs that are available in your IBM Cloud account.

If no API key is set for the default resource group, no VPCs are listed in the Red Hat OpenShift on IBM Cloud console, even if your VPC exists in a different resource group and an API key is set for that resource group.

  How to fix it 

To set an API key for the default resource group, use the Red Hat OpenShift on IBM Cloud CLI.



1.  Log in to the command line as the account owner. If you want a different user than the account owner to set the API key, first [ensure that the API key owner has the correct permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsowner_permissions).

ibmcloud login [--sso]
2.  Target the default resource group.

ibmcloud target -g default
3.  Set the API key for the region and resource group.

ibmcloud oc api-key reset --region <region>
4.  In the [Red Hat OpenShift on IBM Cloud console](https://cloud.ibm.com/kubernetes/catalog/create), click Refresh VPCs. Your available VPCs are now listed in a drop-down menu.
Hosting web applications from a secure private network 

This tutorial describes the use of Classic Infrastructure. Most workloads can be implemented using [IBM Cloud® Virtual Private Cloud](https://cloud.ibm.com/docs/vpc) resources. Use IBM Cloud VPC to create your own private cloud-like computing environment on shared public cloud infrastructure. A VPC gives an enterprise the ability to define and control a virtual network that is logically isolated from all other public cloud tenants, creating a private, secure place on the public cloud. Specifically, [vpc network load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb), [virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_best_practices), [security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups), [network ACLs](https://cloud.ibm.com/docs/vpc?topic=vpc-using-acls) and [public gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-networking-for-vpcexternal-connectivity).

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.

Hosting web applications is a common deployment pattern for public cloud, where resources can be scaled on demand to meet short term and long term usage demands. Security for the application workloads is a fundamental prerequisite, to complement the resilience and scalability afforded by public cloud.

This tutorial takes you through the creation of a scalable and secure Internet facing web application hosted in private network secured using a virtual router appliance (VRA), VLANs, NAT and firewalls. The application comprises a load balancer, two web application servers and a MySQL database server.
Free level of service [Yes, free tier available, that re-sets every month](https://www.ibm.com/cloud/code-engine/pricing) [Yes, free limited cluster](https://cloud.ibm.com/docs/containers?topic=containers-cs_ov) No 
 Latest community Kubernetes distribution Yes. IBM Cloud Code Engine is built on IBM Cloud Kubernetes Service. Yes Partially. Support is as close as possible to the latest major version.For example, right now OpenShift 4.10 is on Kubernetes 1.23, but we offer OpenShift 4.9 right now, which is on Kubernetes 1.22. Support is typically offered on the Kubernetes N-1 version. 
 Scope IBM Cloud IAM access policies to access groups for service access roles that sync to cluster RBAC Yes Yes No 
 Classic infrastructure cluster on only the private network Not applicable, built on Gen2 infrastructure. Yes No 
 GPU bare metal worker nodes No Yes (but only for Classic, not for VPC) Yes (but only for Classic, not for VPC) 
 Integrated IBM Cloud Paks and middleware Not applicable Not applicable Yes 
 Built-in containers, builds, and tooling Yes No Yes 
 Integrated CI/CD Yes (with IBM Cloud Toolchain) No Yes (with Jenkins) 
 Stricter app security context set up by default Yes No Yes 
 Simplified Kubernetes developer experience, with an app console that is suited for beginners Yes No Yes 
 Supported operating system Worker node OS same as IKS Container level OS (if using Docker) is what is supplied in the dockerfile Container level OS (if using buildpack) supports all runtimes available on paketo.io Ubuntu 18.04 x86_64, 16.04 x86_64 (deprecated) Red Hat Enterprise Linux 7 (RHEL); however, as of 4.9, it will be CoreOS (RHCOS) 
 Secured routes encrypted with Hyper Protect Crypto Services No No Yes 
 Subscribe to event producers, such as Cloud Object Storage and Cron Yes Yes Yes
In short, using VPC you can:



* create a software-defined network (SDN),
* isolate workloads,
* have fine control of inbound and outbound traffic.





 Objectives 



* Understand the infrastructure objects available for virtual private clouds
* Learn how to create a virtual private cloud, subnets and server instances
* Know how to apply security groups to secure access to the servers



Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/includes/solution-tutorials/includes/solution-tutorials/images/solution40-vpc-public-app-private-backend/Architecture.svg)

Figure 1. Architecture diagram of the tutorial



1. The admin (DevOps) sets up the required infrastructure (VPC, subnets, security groups with rules, VSIs) on the cloud.
2. The internet user makes an HTTP/HTTPS request to the web server on the frontend.
3. The frontend requests private resources from the secured backend and serves results to the user.







 Before you begin 



* Check for user permissions. Be sure that your user account has sufficient permissions to create and manage VPC resources. See the list of [required permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources) for VPC.
* You need an SSH key to connect to the virtual servers. If you don't have an SSH key, see [the instructions](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys) for creating a key for VPC.







 Step 1: Create a Virtual Private Cloud and subnets 

To tighten the security of your servers, it is recommended to only allow connections to the ports required by the applications deployed on the servers.
In this tutorial, you will deploy a vCenter for a VMware Deployment in IBM Cloud VPC and a floating VLAN interface for it.

VMware Solutions Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-05



[Provision IBM Cloud VPC for a VMware Deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vpc)Provision IBM Cloud VPC for a VMware Deployment

In this tutorial, you will deploy a IBM Cloud VPC for a VMware Deployment and a jump machine for configuration tasks.

VMware Solutions Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-05



[Provision vSAN storage cluster](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vsan)Provision vSAN storage cluster

In this tutorial, a vSAN cluster is created using the local disks attached the Bare Metal Servers for VPC. This phase is optional, if you use NFS.

VMware Solutions Virtual Private Cloud (VPC)



* 1 hour
* 2023-05-05



[Deploying Roll Your Own VMware on IBM Cloud Bare Metal Servers for Virtual Private Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware)Deploying Roll Your Own VMware on IBM Cloud Bare Metal Servers for Virtual Private Cloud

This tutorial walks you through creating your own IBM Cloud VPC with multiple subnets as required to support vSphere networking and the provisioning of IBM Cloud Bare Metal Servers for Virtual Private Cloud (BMS) for a basic VMware vSphere deployment. After the IBM Cloud VPC and Bare Metal Servers for VPC have been provisioned, the tutorial covers a manual deployment of the vCenter, creating VMware compute cluster with vSAN or NFS shared storage options. The tutorial also covers optional features, such as using IBM Cloud VPC network for VMware Virtual Machine networking.
Since the beta release, by default, only a boot volume created as part of provisioning a virtual server instance will be deleted when the instance is deleted. See the [VPC API change log](https://cloud.ibm.com/docs/vpc?topic=vpc-api-change-log21-march-2023).







 16 August 2022 



 For all version dates 

Sharing images across an enterprise account. Accounts that have been granted special approval to preview this feature can now use a [catalog to share custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-imagescustom-image-cloud-private-catalog) with users in other accounts within the same enterprise. When you [create an image](https://cloud.ibm.com/apidocs/vpc/latestcreate-image), a new catalog_offering property includes a published sub-property that is set to false by default. When the custom image is imported to a catalog the published sub-property is set to true, indicating that the image is added to a catalog offering version and is managed from a catalog. If you are authorized to the catalog offering version, you can [provision virtual server instances](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) using that custom image by specifying its catalog_offering.version.crn. To use the custom image associated with the latest version in the offering, specify catalog_offering.offering.crn instead. The image may not be deleted from your IBM Virtual Private Cloud while it is managed from a catalog.

For more information, see the tutorial [Onboarding a virtual server image for VPC](https://cloud.ibm.com/docs/account?topic=account-catalog-vsivpc-tutorial) and the [Import offering](https://cloud.ibm.com/apidocs/resource-catalog/private-catalogimport-offering) method in the Catalog Management API.

This feature is now generally available. The catalog_offering.published property in the beta API definition has been renamed to catalog_offering.managed.
Use [virtual private endpoint gateways](https://cloud.ibm.com/apidocs/vpclist-endpoint-gateways) to connect to supported IBM Cloud services from your VPC network by using the IP addresses of your choice, which is allocated from a subnet within your VPC. For more information, see [About virtual private endpoint gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe).
* VPC network interfaces. IP anti-spoofing checks had already been provided for enhanced security. However, certain use cases, such as having a virtual server instance act as a network gateway, require selective disabling of these checks. To accommodate these use cases, if you have the is.instance.instance.ip-spoofing IAM action, you can now enable the allow_ip_spoofing property when you [create a network interface](https://cloud.ibm.com/apidocs/vpccreate-instance-network-interface). Alternatively, toggle the property when you [update an existing network interface](https://cloud.ibm.com/apidocs/vpcupdate-instance-network-interface). See also [About IP spoofing checks](https://cloud.ibm.com/docs/vpc?topic=vpc-ip-spoofing-about).
* Proxy protocol for application load balancers for VPC. When you configure a load balancer [pool](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-pool) to use proxy protocol, the pool will pass information about the client to a back-end pool member when a connection is opened.

You can also configure a load balancer [listener](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-listener) to accept proxy protocol information. This feature is useful when the client is, itself, a proxy (which, in turn, was connected to by the actual client) that supports the proxy protocol.