BTP & Integrationintermediate

BTP HANA Cloud Part 2: Provisioning, Connectivity and Security Configuration

Key takeaway

Provision HANA Cloud correctly: instance creation and sizing, mapping the instance to Cloud Foundry spaces or Kyma namespaces, allowed connections (IP allowlists), backups, HDI container deployment from CAP, and access for tools and users.

Explanation

📌 KEY POINTS
✅ Create the instance with appropriate memory/storage; enable options (e.g. data lake) as needed.
✅ Instance mapping makes the database available to specific CF spaces or Kyma namespaces.
✅ Allowed connections restrict network access (BTP only, specific IPs, or all).
✅ Backups are automatic; know retention and recovery options.
⚠️ "Allow all IP addresses" exposes the database endpoint to the internet — restrict it.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 introduced HANA Cloud. Now provisioning.

━━━━━━━━━━━━━━━━━━━━
▶ 1. INSTANCE CREATION

Size, version, options.

━━━━━━━━━━━━━━━━━━━━
▶ 2. INSTANCE MAPPING

CF org/space or Kyma namespace.

━━━━━━━━━━━━━━━━━━━━
▶ 3. NETWORK

Allowed connections.

━━━━━━━━━━━━━━━━━━━━
▶ 4. BACKUP & RECOVERY

Automatic backups; point-in-time recovery.

━━━━━━━━━━━━━━━━━━━━
▶ 5. HDI DEPLOYMENT

CAP deploys containers via MTA.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create the instance in HANA Cloud Central.
Map it to your CF space.
Deploy a CAP app and check the HDI container.

✅ CHECKPOINT: deploy succeeds and tables exist.

Code example

ABAP Code

===== STEPS =====HANA Cloud Central → Create instance (memory e.g. 32 GB, allowed connections: BTP only)Instance mapping → environment: Cloud Foundry, org/space GUIDsCAP: cds add hana && mbt build && cf deploy → HDI container created ===== CHECKS =====Database explorer → HDI container → tables | error "no database found" → check mapping

Real project scenario

A project team building a CAP app got HDI deployment failures in a new space. The HANA instance wasn't mapped to that space. Adding the instance mapping fixed deployment.

Common mistakes

Open network access.
Missing mapping.
Shared prod/dev instance.
Oversized instances.
No recovery test.

Best practices

Restrict connections.
Map per space.
Separate prod.
Right-size.
Test recovery.

Interview angle

Questions: "How do you provision HANA Cloud?", "What is instance mapping?", "How do you secure network access?"
Strong answer: creation, mapping, network, backups, HDI deployment.

Practice this lesson

Quick check

1. A team proposes "allow all IP addresses" for HANA Cloud to simplify access. What is the risk?

2. Expect questions distinguishing how Cloud Foundry service bindings differ from Kyma ServiceBindings/Secrets, and why service keys need separate lifecycle management. In the HANA Cloud context, which answer shows the strongest practical judgment?

3. HDI deployment fails with "no database found" in a new space. What is likely missing?

Interview questions

1. What are the most important design decisions, trade-offs, and best practices in HANA Cloud?

Answer it in your own words first, then compare.

2. How would you apply HANA Cloud in a real SAP project? Walk through the design or implementation approach.