Skip to content

Destination Type Note #46

Closed
Closed
@LucimarM

Description

@LucimarM

Issue description

Hello
I got the following question from customer about the following scenarios, they are asking if there is any limitation:

1.Same hyperscaler but same regions (AWS Frankfurt and AWS Frankfurt).
2.Same hyperscaler and different regions (AWS Frankfurt and AWS Virginia).
3.Different hyperscaler and different regions (AWS Frankfurt and Azure Virginia).

Reading the documentation (below note), It is not clear and looks like its only possible to transport to tenants on the same region.

Note: SAP Datasphere is only available on the Cloud Foundry platform. You can share to tenants that use the same type of Cloud Foundry data center as yours. These host systems use two digits, such as eu10 or us30.

I reached the developer to clarify which of those scenarios are supported. I got the following answer:

_ACN would support sharing of packages with all landscapes across hyper-scalers that allow sharing. For example, sharing between tenants on AWS, GCP and Azure are supported (EU10, US10, EU20, US20, US30, IN30…).
Only restriction are on private/EU-access landscapes.

  • Sharing with any landscape (EU10, US10, EU20, US20, US30, IN30…) and EU11 is not allowed
  • Sharing with NS2 landscapes are not allowed
  • Sharing with AliCloud is not allowed._

Could you improve the text of such note making it clear what is supported?

Best reards
Lucimar

Feedback Type (Optional)

clarity

Page Title on SAP Help Portal (prefilled)

Adding Sharing Destinations

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/562e9969426840798e8a5bbf9c395ce8.html?version=cloud

Metadata

Metadata

Assignees

Labels

contributionValuable Contributionneeds-more-infoWe need more info from the contributor to proceedsize/sRequires minimal effort to get changed.type/claritySomething was unclear in the documentation.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions