SAP Community - SAP BTP, Kyma runtime

How to perform Remote Table Replication if the HDI Container is created from Kyma Environment?

2025-01-17T17:45:18.820000+01:00

Hi,

I want to perform Remote Table Replication and have successfully achieved this in the Cloud Foundry environment. However, my main goal is to perform the same for an HDI Container created in the Kyma environment.

The challenge I’m facing is that in the SAP HANA Cloud Database, when I navigate to Add Instance > HDI Container, I can only see containers created in the Cloud Foundry environment. The containers created in the Kyma environment are not visible, which eventually prevents me from setting up Virtual Tables and Remote Subscriptions.

Could you please guide me on how to achieve this?

Thanks,
Abhinav

SAP BTP Cloud foundry Java Heap dumps to SAP Object Store

2025-01-23T18:02:31.248000+01:00

Hi,

I am attempting to push Java heap and thread dumps to a persistent location for further analysis. Persistent storage is required if a container goes down and the Java Heap or thread dumps taken can be lost if container goes down. Following the steps provided in the blog below java heap and thread dumps are able to be taken but are stored locally within the container. It can be exported to a local machine but the files can be very large in GBs.

https://community.sap.com/t5/technology-blogs-by-sap/java-heap-and-thread-dumps-on-sap-btp-cloud-foundry/ba-p/13514382

Is there a known solution around sending these files to SAP object store or another persistent storage location?

Thanks,

Rishi

Kyma APIRule v2alpha1: MaxAge default causing an error in Terraform

2025-01-27T17:21:35.941000+01:00

Hi all,

I'm working to migrate my existing entries for APIRule v1beta1 to v2alpha1, and I've hit upon something that I think might be an issue with the default manifest coming from Terraform.

Below is my original version of the v1beta1 rule in our Terraform (since it's just a manifest it should map to the YAML directly):

resource "kubernetes_manifest" "api_gateway_seq" {
  depends_on = [
    kubernetes_namespace_v1.o11y, data.kubernetes_service_v1.grafana_service, kubernetes_namespace_v1.dns_management,
    kubernetes_manifest.istio_gateway
  ]
  for_each = local.gateways

  manifest = {
    apiVersion = "gateway.kyma-project.io/v1beta1"
    kind       = "APIRule"
    metadata = {
      name      = "seq-apigateway-https-${each.value.suffix}"
      namespace = kubernetes_namespace_v1.o11y.metadata[0].name
    }
    spec = {
      gateway = each.value.gateway
      host = "seq.${each.value.host}"
      service = {
        name = data.kubernetes_service_v1.seq.metadata[0].name
        port = 80
      }

      rules = [{
        path    = "/.*"
        methods = ["GET", "POST", "PUT", "DELETE"]
        accessStrategies = [{
          handler = "allow"
          config  = {}
        }]
      }]
    }
  }
}

And below are the modifications I've made to support v2alpha1 --

Updated "host" to "hosts" with an array of 1
Added namespace to service
Added noAuth = true

resource "kubernetes_manifest" "api_gateway_seq" {
  depends_on = [
    kubernetes_namespace_v1.o11y, data.kubernetes_service_v1.grafana_service, kubernetes_namespace_v1.dns_management,
    kubernetes_manifest.istio_gateway
  ]
  for_each = local.gateways # we have multiple gateways

  manifest = {
    apiVersion = "gateway.kyma-project.io/v2alpha1"
    kind       = "APIRule"
    metadata = {
      name      = "seq-apigateway-https-${each.value.suffix}"
      namespace = kubernetes_namespace_v1.o11y.metadata[0].name
    }
    spec = {
      gateway = each.value.gateway

      hosts = ["seq.${each.value.host}"]

      service = {
        name      = data.kubernetes_service_v1.seq.metadata[0].name
        namespace = data.kubernetes_service_v1.seq.metadata[0].namespace
        port      = 80
      }

      rules = [{
        path    = "/.*"
        methods = ["GET", "POST", "PUT", "DELETE"]
        noAuth  = true
      }]
    }
  }
}

However, when I attempt to apply the Terraform, I see:

> AttributeName("maxAge"): can't use tftypes.String as tftypes.Number

I can't find any reference to maxAge in any default YAML files I've seen, but it does seem like it factors into corsPolicy.

Is there an appropriate default I should be moving to here? Or is this an issue with the standard resource definition?

Unable to open Trail Tenant

2025-02-02T11:32:50.590000+01:00

Hi Experts,

I have been using the Trial Tenants for over a month now. However, when I tried to open the tenant recently, I encountered the following error:

No Client with request id: sb-it-prov!t196

Authorization Request Error: The request for authorization was invalid.

Enclosed screen shot for your reference.

Thanks,

Vinay Chonale

How to enable Cloud Identity Services for Kyma runtime

2025-02-18T10:48:23.134000+01:00

Hi experts,

I try to update an existing Kyma runtime using the SAP Cloud Identity Services as Custom Identity Provider.
I followed the blog Configure Custom SAP IAS tenant with SAP BTP Kyma runtime environment

So, I created a new namespace in my Kyma environment. Here I created a service instance using offering name "identity" and plan name "application" setting following parameters:

assertion-attributes:
  email: mail
  first_name: firstName
  groups: companyGroups
  last_name: lastName
  locale: language
  login_name: loginName
  mail: mail
  scope: companyGroups
  user_uuid: userUuid
default-attributes: {}
display-name: Kyma runtime
home-url: https://api.#######.kyma.ondemand.com
name: ias-kyma-#######
oauth2-configuration:
  grant-types:
    - authorization_code
    - authorization_code_pkce_s256
  public-client: true
  redirect-uris:
    - https://dashboard.kyma.cloud.sap
    - http://localhost:8000
  token-policy:
    access-token-format: default
    refresh-parallel: 3
    token-validity: 3600
subject-name-identifier:
  attribute: mail
  fallback-attribute: none
user-access: internal

Based on this service instance I created a service binding called "skr-ias-binding" with secret name "skr-ias-binding-secret" and following parameters:

{
  "credential-type": "NONE"
}

Once the service binding was provisioned I copied the ClientId and Url from the secret and updated the Kyma runtime using following JSON:

{
    "oidc": {
        "issuerURL": "https://ouriastenant.accounts.ondemand.com",
        "clientID": "########-####-####-####-############",
        "usernameClaim": "sub",
        "groupsClaim": "groups",
        "signingAlgs": [
			"RS256"
		],
        "usernamePrefix": "-"
    },
    "administrators": [
        "user1@mycompany.com",
        "user2@mycompany.com"
    ]
}

The Kyma runtime was updated successfully. And when I launch the dashboard I'm also asked to log in with my IAS user.

However, after login I see following error:

When I check the network trace within the developer tools of the browser I see lot of HTTP 401 errors telling me I'm not authorized. But when I decode the Bearer token attached to the requests I can see all my users details. The "sub" attribute of the Bearer token contains my email which is also configured to be an administrator of the Kyma environment.

Within the IAS admin console I can see the new application. From the configuration it looks good as also described in SAP Help:

Redirect URIs are set to "https://dashboard.kyma.cloud.sap" and "http://localhost:8000"
The grant types "Authorization code" and "Enforce PKCE" are checked (but no other grant type)
The Public Client is enabled

Did I miss a step?

regards

René

In Calls Pallet - Externals - Request Reply - Processing Option not showing.

2025-03-15T07:23:47.855000+01:00

IN SAP CPI Trail Account - In Calls Pallet - Externals - Request Reply - Processing Option not showing. nis there any this issue, it shouldnot wprk in trail versions.

where can i get training for SAP certification exam C_CPE_2409

2025-05-02T19:39:02.548000+02:00

"Could you provide information on where to find documentation or tutorials that outline the prerequisites for:

Building side-by-side extensions
Developing applications in SAP BTP, Kyma Runtime
Developing applications in SAP BTP, Cloud Foundry runtime
Developing advanced extensions with SAP Cloud SDK on SAP BTP?"

"An example screenshot related to building side-by-side extensions on SAP BTP is referenced in this context."

Helm install issue when following tutorial for CDM to integrate application with SAP Build workzone

2025-07-10T10:30:07.904000+02:00

I am following the tutorial https://developers.sap.com/tutorials/integrate-with-work-zone-kymaruntime.html with respect to CDM for deploying application to kyma.
Tutorial mentions to delete the destination configuration in chart/values.yaml. However after doing the step when one does the helm install command, it throws an exception saying no value for destination service instance and plan found

I reckon this is because destination has also been bound in the srv configuration

Tutorial only says to delete destination binding in the html5-deployer section.

Should one also go ahead and delete the destination binding for srv as well

APIRule not working on kyma

2025-07-22T15:57:28.731000+02:00

API rules not working on this cluster : https://api.bc6186c.kyma.ondemand.com/

While exposing I used {APP}.c-{CLUSTER_DOMAIN} which used to work but not working anymore.

Can't open the Commerce Mock Application.

2025-08-14T09:39:58.972000+02:00

https://developers.sap.com/tutorials/cp-kyma-mocks.html#bfee5f18-44f6-46b4-921a-4c1964e60f14 Deploy Commerce Mock Application in SAP BTP, Kyma Runtime In the step4,I can't open the Commerce Mock Application in website.why?

Deploy an application as container on SAP BTP Kyma runtime

2025-09-19T09:10:26.183000+02:00

Disclaimer: The insights shared in this blog are based on my personal observations and learning. They may not apply universally, and I encourage readers to conduct their own research and make an informed decision before using this content for productive use.

We are excited to launch a new series of blogs that will guide you through deploying container-based applications on the SAP BTP Kyma Runtime environment. This series will not only cover the fundamentals of containerization but also provide hands-on insights, best practices, and real-world examples to help you harness the full potential of Kyma for scalable, cloud-native application deployment.

Steps to Enable the Kyma Runtime Environment

Access Your Trial Account
- Log in to your SAP BTP Trial account.
Create or Open a Subaccount
- Navigate to your global account.
- Either open an existing subaccount or create a new subaccount dedicated for Kyma Runtime.
Enable Kyma Runtime
- In the subaccount, go to the Entitlements section and make sure Kyma Runtime is assigned.
- Navigate to Kyma Environment and enable the runtime.
- The setup process may take a few minutes while the environment is being provisioned.
Download the Kubeconfig File
- Once Kyma is active, download the Kubeconfig URL file.
- Store it securely and add it to your kyma folder (this will be used to authenticate your local CLI with the Kyma cluster).

Introduction

Looking to take your Spring Boot Eureka application to the next level by deploying it securely and reliably on the Kyma Runtime within SAP Business Technology Platform (BTP)? This guide provides a step-by-step walkthrough of the entire lifecycle: from packaging your application as an OCI-compliant container image, pushing it to a trusted container registry, and defining Kubernetes manifests, all the way to deploying it on Kyma. By the end, your Eureka service will be running in a scalable, cloud-native environment, fully integrated with the capabilities of SAP BTP.

Kyma bridges the gap between cloud-native technologies and SAP’s enterprise cloud infrastructure—so mastering these steps will help you build robust solutions that integrate well with SAP BTP.

Prerequisites

Before you start, make sure you have the following in place:

An SAP BTP subaccount with the Kyma Runtime enabled.
The Kubernetes command-line tool (kubectl) configured with your Kyma cluster (kubeconfig).
Docker installed locally.
A Docker Hub account (or equivalent OCI registry).
A simple SpringBoot eureka app ready (for example, created via the Express generator tutorial).

Step 1: Identify Key Domains and Subdomains

From your SAP BTP Cockpit, note down the Subaccount subdomain. This is used later for routing, hostnames, etc.
From your kubeconfig.yml file, find the Kyma cluster domain, for example something like *.kyma.shoot.live.k8s-hana.ondemand.com.

These values are needed when you later define the Kubernetes and API routing resources.

Step 2: Build Your App into an OCI Image or using docker

You can build Docker-images in many ways, but one of the recommended approaches is to use Cloud Native Buildpacks (CNB), for example via the Paketo Buildpacks.

Install the pack CLI tool.

brew install buildpacks/tap/pack

From your application directory, build the image with a command like:

pack build <your-dockerhub-account>/my-kyma-app:v1 \ --builder paketobuildpacks/builder-jammy-full

This takes your source code, applies buildpacks, sets up the runtime image without needing a Dockerfile (unless you need custom behavior).

Using docker, we can use the below command to build an image

docker build -t <repository_name>/<image_name>:<tag> <path_to_dockerfile_context>

Step 3: Push the Image to Docker Hub

Once built, you need to get the image into a container registry that your Kyma cluster can pull from.

Log into Docker:

docker login -u <your-Docker-ID> -p <password>

Push the image:

docker push <your-dockerhub-account>/<IMAGE_NAME>:<TAG_NAME>

Step 4: Prepare the Deployment Namespace

In your Kyma cluster, it's best to isolate your application in its own namespace (or use existing ones as per your organizational setup).

kubectl create namespace my-namespace

Alternatively, this can be done via the Kyma dashboard UI.

Step 5: Allow Kyma to Pull Your Image Securely

If your image is in a private registry (or even if public but you want more control), create a Kubernetes secret of type docker-registry. This allows your cluster's nodes / pods to authenticate with Docker Hub.

kubectl -n multitenancy-ns create secret docker-registry registry-secret --docker-server=https://index.docker.io/v1/  --docker-username=<docker-id> --docker-password=<password> --docker-email=<email>

or use can use you own docker credential's to pull the image and deploy it on kyma cluster.

docker pull [IMAGE_NAME]:[TAG]

In your Kubernetes deployment manifests, refer to this secret under imagePullSecrets.

Step 6: Define Kubernetes and Kyma Manifests

You’ll need YAML manifest files to define:

Deployment: Defines your app pods, container image, resource limits, probes (liveness/readiness), etc.
Service: Exposes your pod(s) internally on Kubernetes.
APIRule (Kyma Gateway object): Exposes the service externally via the Kyma gateway, defines host, route, and allowed HTTP methods (GET, POST, etc.).
NetworkPolicy: (Optional / depending on your security posture) To restrict access, allow only certain ingress, etc.

Here’s a simplified structure of what goes into the k8s-deployment-backend.yaml manifest:

a. Define an APIRule to securely expose your application endpoint to external users.

apiVersion: gateway.kyma-project.io/v2
kind: APIRule
metadata:
  labels:
    app: euraka-application
  name: euraka-application
spec:
  gateway: kyma-system/kyma-gateway
  hosts: 
    - euraka-application
  rules:
    - path: /*
      methods: ["GET", "POST", "PUT", "PATCH"]
      noAuth: true
  service:
    name: euraka-application
    port: 80

b. Create a Deployment resource that will orchestrate the rollout and scaling of your application.

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: euraka-application
  name: euraka-application
spec:
  replicas: 1
  selector:
    matchLabels:
      app: euraka-application
  template:
    metadata:
      labels:
        app: euraka-application
        sidecar.istio.io/inject: "true"
    spec:
      imagePullSecrets:
        - name: euraka-application-secret
      containers:
      - env:
        image: <IMAGE_NAME>:<TAG_NUMBER>
        name: euraka-application
        ports:
        - name: http
          containerPort: 8761
          protocol: TCP

c. Create a Service resource that routes traffic to your application’s pods and makes it discoverable.

apiVersion: v1
kind: Service
metadata:
  labels:
    app: euraka-application
  name: euraka-application
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 8761
  selector:
    app: euraka-application

Make sure you replace placeholders (account names, namespace, hostnames) with your actual values.

d. Create a NetworkPolicy to manage how your application is exposed and which traffic is allowed.

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: multitenancy
spec:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          kubernetes.io/metadata.name: istio-system
      podSelector:
        matchLabels:
          app: istio-ingressgateway
  podSelector:
    matchLabels:
      release: multitenancy
  policyTypes:
  - Ingress

Step 7: Deploy to Kyma Runtime

Once your manifest YAML is ready:

kubectl -n my-namespace apply -f deployment.yaml
kubectl -n my-namespace apply -f service.yaml
kubectl -n my-namespace apply -f rule.yaml
kubectl -n my-namespace apply -f network.yaml

This will create the Service, Deployment, APIRule (gateway), etc.

Step 8: Access Your Application

In the Kyma Dashboard, navigate to Namespaces → your namespace → find the APIRule or associated Host URL.
Copy the external URL enabled by the APIRule’s host field and open it in your browser.

If everything went well, you should see the response your Spring Boot Eureka app sends (could be a "Home Page" or whatever default you configured).

Summary

Deploying a Spring Boot Eureka application to Kyma involves a series of well-defined steps that ensure your app is containerized, securely stored, properly exposed, and seamlessly running in a scalable, cloud-native environment. While the process may seem detailed at first, once you’ve gone through it a few times, it becomes a repeatable pattern you can apply with confidence.

By following this flow, you’ll be able to:**

Accelerate delivery — move quickly from code to deployment.
Ensure consistency — maintain reliable behavior across development, staging, and production environments.
Leverage Kyma’s strengths — tap into Kubernetes-native features like autoscaling, intelligent routing, and network/security policies.”**

Kyma Application Cannot Send Traces to the Telemetry Module (RBAC: Access Denied)

2025-10-06T18:55:18.575000+02:00

Hi everyone,

We wanted to perform some tracing tests on our Kyma cluster with the Telemetry module enabled.
For this purpose, we deployed the OpenTelemetry Demo application in our custom namespace, following the guide:

Kyma OpenTelemetry Demo Integration

All prerequisites were completed successfully. Our telemetry backend is an ELK stack instance — the connection to it works, and we can see logs arriving there. However, the demo application is not able to send traces and logs to the dedicated Telemetry gateways.
We see the following errors in the application logs:

[Error] File: /opentelemetry-cpp/exporters/otlp/src/otlp_grpc_log_record_exporter.cc:173
[OTLP LOG GRPC Exporter] Export() failed: RBAC: access denied

[Error] File: /opentelemetry-cpp/exporters/otlp/src/otlp_grpc_exporter.cc:159
[OTLP TRACE GRPC Exporter] Export() failed with status_code: "PERMISSION_DENIED" error_message: "RBAC: access denied"

The logs are visible in Kibana, so they are probably being collected by the log agent(s). Do we need any additional configuration (e.g., custom Roles or Istio AuthorizationPolicies), or is the demo app expected to work out of the box?

Thanks in advance for your help!

Lozan

Preparing for SAP C_CPE? Here’s How I’m Studying Each Section Without Feeling Overwhelmed

2025-11-03T19:56:45.656000+01:00

Whenever I start learning something new, I like to have everything in order.
Before I even open the first tutorial, I plan what I’ll study first, what comes next, and how I’ll track it.

Recently, I started preparing for the SAP C_CPE (SAP Certified Associate - Backend Developer - SAP Cloud Application Programming Model) certification. Since this exam covers a mix of BTP architecture, SAP BAS, CAP, Side by side extensions, Cloud Foundry & Kyma Runtime it can easily feel like too much at once. So I created a simple structure to move step by step without feeling lost.

I began with the learning about BTP, and doing hands on by following SAP Learning Journeys, creating subaccount and adding entitlements and services (It gave me a very clear understanding of BTP architecture) and then Developing appliaction using high productivity tools of SAP BAS, Cloud Application Programming Model (CAP) because it’s the foundation of most topics in this certification. I’m spending around two weeks learning about CDS models, service layers and how everything connects in a CAP project. I’m following the official SAP Learning Journey https://learning.sap.com/certifications/sap-certified-associate-backend-developer-sap-cloud-programming-model and doing small hands-on exercises along the way.

My next focus is Cloud Foundry. I’ll spend about a week learning how to efficiently develop, run, and manage cloud-native applications on SAP BTP, Cloud Foundry Runtime.

After that, I’ll move to Side by side extention on BTP. This will cover deploying extension and integrating the app into SAP Build Work Zone.

The next stage is Developing Appliactions in Kyma Environment. I’ll take about two weeks to explore a comprehensive understanding of Kubernetes and to orchestrate the deployment of the applications in the cloud.

Finally, I’ll study Advanced Extensions with SAP Cloud SDK for about two more weeks. These are slightly advanced topics but very useful for understanding to develop and integrate Java, JavaScript, and TypeScript extension applications for SAP solutions like SAP S/4HANA Cloud Public Edition.

So in short, this will be my roadmap-

Recommended Study Sequence

Here’s the order I suggest, from foundational to more advanced :

Exploring SAP Business Technology Platform 5hrs (link : https://learning.sap.com/courses/exploring-sap-business-technology-platform)
- This gives you a broad overview of the entire platform (services, architecture, what BTP is). Good for building your base understanding.
- So start here.
Develop Full‑Stack Applications Using Productivity Tools in SAP Business Application Studio 8hrs (https://learning.sap.com/learning-journeys/develop-full-stack-applications-using-productivity-tools-in-sap-business-application-studio)
- Once you know the platform, you learn the developer tooling (BAS = Business Application Studio) which is key for CAP and full-stack apps.
- So this is your next step.
Develop Applications on SAP BTP, Cloud Foundry Runtime 4hrs(https://learning.sap.com/learning-journeys/developing-applications-on-sap-btp-cloud-foundry-runtime)
- The Cloud Foundry runtime is a major runtime environment in BTP. Understanding how to build and deploy there is critical.
Build Side‑by‑Side Extensions on SAP BTP 8hrs (https://learning.sap.com/learning-journeys/build-side-by-side-extensions-on-sap-btp)
- After tooling and platform basics, you dive into extension scenarios (for example side-by-side extensions of S/4HANA using CAP). This aligns closely with CAP certification topics.
Developing Applications in SAP BTP, Kyma Runtime 8hrs(https://learning.sap.com/learning-journeys/developing-applications-in-sap-btp-kyma-runtime)
- Kyma Runtime is more advanced (Kubernetes, microservices, event-mesh) and often sits on top of foundational knowledge.
Develop Advanced Extensions with SAP Cloud SDK 11hrs (https://learning.sap.com/learning-journeys/develop-advanced-extensions-with-sap-cloud-sdk)
- This is relatively specialized/advanced (SAP Cloud SDK, perhaps custom libraries, integrations). Once you’ve mastered the fundamentals above, you go here.

By the end of this plan, I’ll go through a short revision period with mock questions and quick notes from my learning.

This structured approach keeps my study plan clear and prevents me from feeling overwhelmed.
I study for two to four hours a day which feels realistic, and the small milestones make it easier to stay consistent.

If you’re also preparing for C_CPE, it really helps to make your own sequence instead of jumping randomly between topics. The Learning Journeys are excellent resources, but having a personal roadmap makes a big difference.

I’d love to hear how others are preparing for this certification too.
What topics are you finding most challenging so far and how are you managing the learning.

How can I access the Alert Notification dashboard for an instance bound to a Kyma application?

2025-11-04T12:31:03.507000+01:00

I have an application deployed on the Kyma runtime. I created a service instance and binding and can create alert notifications from my application. Now I need a way to consume/query those notifications. For applications deployed directly on BTP there is way to access the dashboard of the Alert Notification service, but I can't find a way to do that for the instance bound to my Kyma app.

Transport app to another BTP subaccount

2025-11-06T21:13:48.158000+01:00

Hi Community,
how can I transport an app (e.g. SAP IAS) from one BTP subaccount to another ?

Thanks for your help.

Best Regards

Optimize Cost and usage of Capacity units in BTP KYMA runtime

2025-11-24T22:43:13.013000+01:00

how to calculate and Optimize Cost and usage of Capacity units in BTP KYMA runtime. is it possible to add alert mechanism.

How Can I Design a Scalable, Secure, and Cost-Optimized Architecture Using Microsoft Azure Services

2025-12-11T11:03:57.092000+01:00

I’m currently working on modernizing our organization’s IT infrastructure and evaluating how we can fully leverage Microsoft Azure Services to build a scalable, secure, and cost-efficient cloud environment. Since our business is rapidly growing and we plan to migrate multiple legacy applications, databases, analytics workloads, and internal services to the cloud, I’m looking for guidance on the best architectural approach and which Azure services we should prioritize.

1. How Should I Choose the Right Azure Compute Services?

What decision framework should I follow to select the best compute option for microservices, web apps, APIs, or batch processing workloads?

2. Looking for Real-World Guidance

If anyone has designed or implemented a full-scale enterprise architecture on Azure:

What were your biggest challenges and lessons learned?
What services did you prioritize, and what pitfalls should I avoid?
Any reference architectures or step-by-step practices would be extremely helpful.
Are there recommended patterns for mixing serverless and container-based workloads?

Why does SAP HANA Cloud show estimated cost in a BTP Trial account?

2025-12-18T16:14:37.193000+01:00

Hello everyone:

I have an SAP BTP trial account and am trying to deploy an application in Kyma using SAP HANA Cloud.
During the process, I am asked to create an SAP HANA Cloud instance, but when I do so, a pop-up window appears showing an estimated cost calculation.

My question is:
With an SAP BTP trial account, is it not possible to create an SAP HANA Cloud database instance for free without any cost?

Thanks in advance!

Kyma High availability

2026-01-29T10:06:02.828000+01:00

Hello everyone,

This is a silly question, but I can't really find the right answer.

Let's assume we are creating a basic Kyma cluster with three nodes. According to the documentation, they are in different regions. How is a region defined? As with CF, in a different data centre?

The more interesting question is, how are the components updated? Is this done per node? So as not to cripple the entire cluster? Is this then based on region, as with CF? Where can I see the time periods for this, is there a note?

There is therefore no need to set up multiple clusters in different sub-accounts.

If this is the case, Kyma would be the more elegant option than a multi-region setup using CF.

Best regards

Need Help Verifying Phone Number

2026-02-04T04:20:59.232000+01:00

I'm having trouble verifying the phone number for BTP Trial account.

I'm getting an error message: "We did not send you a code because you are not allowed to request phone calls. Please contact your system administrator." When I’m trying to request a code.

I'm currently living in Vietnam. Is there a way to verify via SMS or other way?