Administer Azure network traffic

Traffic is always initiated by the Agent to Azure API Manager and Amplify Central. No sessions are ever initiated back to the Agent.

4 minute read

Data destinations

The destination for:

  • Agent Authentication data is login.axway.com
  • API definition (Swagger or WSDL) and API documentation data is apicentral.axway.com
  • API Event data, the transaction summary and headers, is ingestion-lumberjack.datasearch.axway.com
  • Subscription notification for getting platform user information is platform.axway.com
  • API usage statistics, the number of calls placed to, is https://lighthouse.admin.axway.com

Data exchanged

Discovery Agent

The Discovery Agent sends the following information to the Axway Amplify platform:

  • API definition using Swagger or WSDL depending on the API type (REST vs SOAP)
  • API documentation

Traceability Agent

Only traffic related to discovered APIs is sent to the platform.

The agent reads the logs written on the file system ([INSTALL_DIR]/apigateway/events/group-X_instance-Y.log) by the Gateways to get the transaction summary:

  • Transaction HTTP status
  • Transaction URLs (frontend / backend API)
  • Transaction duration and timestamp
  • Transaction service called: method (POST / GET…) + uri path

In order to submit details of the transaction, the Traceability Agent reads the Gateway system to get the transaction details:

  • Request/response headers from each API call

Once the information is extracted it is sent to the Axway platform using the TLS encryption.

Communication ports

All outbound traffic is sent over SSL via TCP / UDP.

Open the following ports so that agents can communicate to the Amplify platform:

Outbound:

Region Host IP port Protocol data
EU/US platform.axway.com 34.211.114.227 443 HTTPS
54.201.86.113
EU/US lighthouse.admin.axway.com 443 HTTPS API usage statics
EU/US login.axway.com 52.58.132.2 443 HTTPS
52.29.4.35
54.93.140.145
US apicentral.axway.com 3.94.245.118 443 HTTPS API definitions, Subscription info
54.208.199.251
3.212.78.217
52.202.95.208
107.23.176.64
3.225.16.120
EU central.eu-fr.axway.com 52.47.84.198 443 HTTPS API definitions, Subscription info
13.36.25.69
35.181.21.87
13.36.2.143
13.36.52.216
15.236.7.112
US ingestion-lumberjack.datasearch.axway.com or ingestion.datasearch.axway.com 54.225.171.111 453 or 443 TCP or HTTPS API event data
54.225.2.221
54.146.97.250
54.147.98.128
52.206.193.184
54.225.92.97
EU ingestion-lumberjack.visibility.eu-fr.axway.com or ingestion.visibility.eu-fr.axway.com 15.236.125.123 453 or 443 TCP or HTTPS API event data
35.180.77.202
13.36.27.97
13.36.33.229

Note: Region column is representing the region where your Amplify organization is deployed. EU means deployed in European data center and US means deployed in US data center. Be sure to use the corresponding Host/Port for your agents to operate correctly.

Inbound:

The docker container does not expose any ports outside of the container. Within the container the following listen:

Host Port Protocol Data
Docker Container 8989 (default) HTTPS Serves the status of the agent and its dependencies for monitoring

Validation

Direct Connection

Connecting to Amplify Central and Login hosts:

curl -s -o /dev/null -w "%{http_code}"  https://apicentral.axway.com

curl -s -o /dev/null -w "%{http_code}"  https://login.axway.com

A return of “200” validates the connection was established.

Connecting to Amplify Central Event Traffic host, HTTPS:

curl -s -o /dev/null -w "%{http_code}" https://ingestion.datasearch.axway.com

A return of “200” validates the connection was established.

Connecting to Amplify Central Event Traffic host, Lumberjack:

curl ingestion-lumberjack.datasearch.axway.com:453

A return of “curl: (52) Empty reply from server” validates the connection was established.

Connection via Proxy

Connecting to Amplify Central and Login hosts:

curl -x {{proxy_host}}:{{proxy_port}} -s -o /dev/null -w "%{http_code}"  https://apicentral.axway.com

curl -x {{proxy_host}}:{{proxy_port}} -s -o /dev/null -w "%{http_code}"  https://login.axway.com

A return of “200” validates the connection was established.

Connecting to Amplify Central Event Traffic host, HTTPS:

curl -x {{proxy_host}}:{{proxy_port}} -s -o /dev/null -w "%{http_code}" https://ingestion.datasearch.axway.com

A return of “200” validates the connection was established.

Connecting to Amplify Central Event Traffic host, Lumberjack:

curl -x socks5://{{proxy_host}}:{{proxy_port}} ingestion-lumberjack.datasearch.axway.com:453

A return of “curl: (52) Empty reply from server” validates the connection was established.

Troubleshooting

Curl connection to ingestion-lumberjack.datasearch.axway.com

  • Error:

    curl: (6) Could not resolve host: ingestion-lumberjack.datasearch.axway.com

    • Cause: The host making the call can’t resolve the ingestion-lumberjack DNS name.

    • Possible Resolution: Tell curl to resolve the hostname on the proxy:

      curl -x socks5h://{{proxy_host}}:{{proxy_port}} ingestion-lumberjack.datasearch.axway.com

  • Error:

    curl: (7) No authentication method was acceptable.

    • Cause: The SOCKS proxy server expected an authentication type other than what was specified.

    • Possible Resolution: Provide authentication to the proxy:

      socks5://{{username}}:{{password}}@{{proxy_host}}:{{proxy_port}}

      The Agents only support the use of username/password authentication method for SOCKS connections.


Last modified May 5, 2021: APIGOV-18060 - add new variables and network traffic doc (#1847) (28ec544e)