switching to hostnames routing with HANA XSA on AWS

[Cocquerel]

Hello,

I have successfully installed HANA Express on AWS from SAP CAL. Then, to be able to access XSA from my company network, I had the constrain to switch to 443 port only. So, I followed the steps described in note https://launchpad.support.sap.com/#/notes/2245631 to switch to hostnames routing and port 443.

My new api URL is now https://api.coquerel.airbus-v.cloud/v2/info with coquerel.airbus-v.cloud that is mapped to my fixed public AWS IP in my company DNS server.

The api URL is working fine and I get the following json

{"name": "XS Controller","support": "http://service.sap.com/message","build": "","version": "1","controllerVersion": 8,"model": 52,"timezone": "Etc/UTC","description": "SAP XS Runtime on premise","controllerEndpoint": "https://api.coquerel.airbus-v.cloud","authorizationEndpoint": "https://uaa-server.coquerel.airbus-v.cloud/uaa-security","userAuthorization": true,"allowDebug": true,"acceptEncoding": "gzip, x-gzip","hashAlgorithm": "SHA-256","databaseType": "HANA_MULTI","databaseInfo": "","limits": {},"usage": {"apps": 56,"instances_crashed": 1,"instances_running": 39,"instances_starting": 4,"instances_stopped": 128,"instances_timed_out": 0,"services": 43},"routingMode": "Hostnames","serviceUrls": [{"key": "deploy-service","value": "https://coquerel.airbus-v.cloud:443"},{"key": "product-installer","value": "https://coquerel.airbus-v.cloud:443"},{"key": "hrtt-service","value": "https://coquerel.airbus-v.cloud:443"},{"key": "hrtt-core","value": "https://coquerel.airbus-v.cloud:443"},{"key": "xsa-admin","value": "https://coquerel.airbus-v.cloud:443"},{"key": "di-cert-admin-ui","value": "https://coquerel.airbus-v.cloud:443"},{"key": "di-space-enablement-ui","value": "https://coquerel.airbus-v.cloud:443"},{"key": "javatools","value": "https://coquerel.airbus-v.cloud:443"},{"key": "nodejstools","value": "https://coquerel.airbus-v.cloud:443"},{"key": "portaltools","value": "https://coquerel.airbus-v.cloud:443"},{"key": "webide","value": "https://coquerel.airbus-v.cloud:443"},{"key": "job-scheduler-service-dashboard","value": "https://coquerel.airbus-v.cloud:443"},{"key": "web","value": "https://coquerel.airbus-v.cloud:443"}]}

the url https://uaa-server.coquerel.airbus-v.cloud/uaa-security is also working fine and I get a "where to go?" message after successfull authentication that is normal.

The issue is with the other xsa applications URLs. None of them are working. I get error 503 "Service not available". example: https://webide.coquerel.airbus-v.cloud:443

There is one step in the sap note that I have not done that is to redeploy the applications. For this, I tried to connect with XS CLI with following command :

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff} span.s1 {font-variant-ligatures: no-common-ligatures}

xs api https://api.coquerel.airbus-v.cloud --skip-ssl-validation

but I get the following error message:

p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff} span.s1 {font-variant-ligatures: no-common-ligatures}

FAILED: Could not connect to controller on https://api.coquerel.airbus-v.cloud

Connection refused (Connection refused) (local port 52636 to address 0:0:0:0:0:0:c0a8:10f, remote port 30030 to address 52.4.143.54 (ec2-52-4-143-54.compute-1.amazonaws.com))

Is there an other method to redeploy the applications?

[marcbecker]

Hi Michael,

yes the reason why the applications don't work is because they did not get notified about the changed API URLs.
So redeploying them is the right thing to do.

The issue that you have with the xs client is easily solvable. The xs client for some reason does not use 443 (for https) and 80 (for http) as default ports but actually uses 30030 (for either https and http). You can also see in the "Connection refused" error message, that it tried to connect to 30030. Please specify the API URL as "https://api.coquerel.airbus-v.cloud:443" and your xs client connection will be successful. After that you can try to redeploy all applications.

Best regards,
Marc