Requisites Before Installation

Prerequisites #

Overview #

This section of the AWS Connector Configuration process explains in detail the prerequisites that needs to be met by your SAP Server before you start with the installation process of the Add-on.

Topics #

1. Ensure connectivity from your server to AWS Endpoints #

Before you can start using AWS Connector for SAP, you will need to ensure that your SAP server is able to reach the AWS Services Endpoints.

More Information:

All communications from the SAP Server to AWS will be done through HTTPS protocol so network connectivity should be granted to at least the following list of endpoints.

  • Open connection to AWS Core Services Endpoints

    Some services need access to the root service endpoint before they can be redirected to the region where your resources are located. For that, you need to grant access to the following list of services to grant the proper communication from your SAP Server to AWS Services.

    Service Endpoint URL
  • Open connection to AWS Regional Services Endpoints

    The rest of AWS Services accessed from SAP should have granted access to the regional AWS Endpoints. All endpoints will have the following sintax:


    For instance, if your resources are stored in eu-west-1 region

    Service Endpoint URL

    And any additional service needed and supported by AWS Connector.

  • Open Connection to CA and Issuer Certificate Endpoints

    Every certificate has a CA and a Issuer that grant that the certificate is valid. These certificates must also be present in your SAP Server. AWS Connector for SAP can handle the Amazon SSL certificates automatically, but to do that, access to the following links should also be granted.

    Type Provider Endpoint
    Issuer Certificates Amazon Trust
    CA certificates Digicert
  • Test connectivity

    To ensure that the connectivity has been properly granted, you can use one of the following tools to perform some tests.

    telnet <endpoint> <port>


    # telnet 443
    Connected to
    Escape character is '^]'.

    Press Ctrl+C to close

    Common errors

    • Name or service not known. Ensure that your server can resolve public DNS names.
    # telnet 443
    telnet: Name or service not known Unknown host
    • Trying to connect …. Server can resolve name, but server cannot reach the HTTPS port of the destination.
    # telnet 443

    Reference Guide:

    curl -v https://<endpoint>:<port>


    # curl -v
    *   Trying
    * Connected to ( port 80 (#0)
    > GET / HTTP/1.1
    > Host:
    > User-Agent: curl/7.69.1
    > Accept: */*
    * Mark bundle as not supporting multiuse
    < HTTP/1.1 307 Temporary Redirect
    < x-amz-id-2: JH/CXZvDWKZ/byo+HOIK8lSdXh/LnfzEvQBM+o0vWnQ02t6WxARttqzQMhu+IFsqSaJCYZj2E8g=
    < x-amz-request-id: A2FE83DB7EE23B7E
    < Date: Tue, 13 Oct 2020 16:42:25 GMT
    < Location:
    < Content-Length: 0
    < Server: AmazonS3
    * Connection #0 to host left intact

    Known Errors

    • Name can not be resolved. Ensure that your server can resolve public DNS names.
    # curl -v
    * Could not resolve host:
    * Closing connection 0
    curl: (6) Could not resolve host:
    • Trying to connect …. Server can resolve name, but server cannot reach the HTTPS port of the destination.
    # curl -v
    *   Trying

    Reference Guide:

    nmap -p <port> --script ssl-cert <endpoint>


    # nmap -p 443 --script ssl-cert
    Starting Nmap 7.80 ( ) at 2020-10-13 20:14 CEST
    Nmap scan report for (
    Host is up (0.044s latency).
    rDNS record for
    443/tcp open  https
    | ssl-cert: Subject: commonName=*, Inc./stateOrProvinceName=Washington/countryName=US
    | Subject Alternative Name:, DNS:*,, DNS:*,, DNS:*, DNS:*, DNS:*,, DNS:*,, DNS:*, DNS:*, DNS:*
    | Issuer: commonName=DigiCert Baltimore CA-2 G2/organizationName=DigiCert Inc/countryName=US
    | Public Key type: rsa
    | Public Key bits: 2048
    | Signature Algorithm: sha256WithRSAEncryption
    | Not valid before: 2020-08-04T00:00:00
    | Not valid after:  2021-08-09T12:00:00
    | MD5:   e160 590c b4d7 9780 4129 6a54 bfe2 e45d
    |_SHA-1: 5e7c be8d abc2 1f27 d666 bd6c 7e2b 04eb 5628 2317
    Nmap done: 1 IP address (1 host up) scanned in 6.26 seconds

2. Create or Prepare the needed AWS Resources in your account #

AWS Connector for SAP will use an IAM User to connect to the AWS Services. This IAM User will have an IAM Policy with all the permissions needed to access the AWS Resources always following the least privilege principle.

  • Creating the IAM User and Policy

    The following guide will help you to create the proper AWS resources in IAM.

    1. Sign in to the AWS Management Console and open the IAM console at

    2. In the navigation panel, choose Users and then choose Add user.

    3. Type the user name for the new user.

    4. Select Programmatic access. This creates an access key for each new user. You can view or download the access keys when you get to the Final page.

    5. Choose Next: Permissions.

    6. Choose Attach existing policies to user directly

    7. Create policy to open a new browser tab and create a new policy from scratch. For more information, see step 4 in the AWS Documentation Creating IAM policies (console). Use the below policy as an example to create your IAM Policy.

      1. Specify a name and a description (optional) for the Policy.

      2. Add the proper permissions. Use the following policy as an example.

        Attention required. The following example allows the SAP Server to access a specific Amazon S3 bucket and encrypt/decrypt the data stored on it with a specific key.

        "Version": "2012-10-17",
        "Statement": [
            "Effect": "Allow",
            "Action": [
            "Resource": "*"
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": [
                "arn:aws:s3::: <SAPSID>_*/*"
            "Effect": "Allow",
            "Action": ["kms:Decrypt", "kms:Encrypt", "kms:GetKeyPolicy"],
            "Resource": [
      3. Create Policy and close the browser tag.

      4. Back to the user creation. Select the newly created policy.

    8. Next:Tags.

    9. Add your tags if required.

    10. Next:Review

    11. Create User if all data is correct.

    12. Note down or download the credentials created. Will be used during configuration process.

3. Prepare your SAP Server to use AWS Connector for SAP #

As part of AWS Connector for SAP implementation, as in any SAP Netweaver based server, there is a requirement to establish SSL (Secure Sockets Layer) security for an ABAP-based system that requires secure, encrypted communications. SSL (Secure Sockets Layer) is a communication method whereby secure communication between system entities is accomplished by the use of encryption facilitated by X.509 certificates published by Certificate Authorities (CA) in tandem with public and private decryption keys.

For your SAP Server to connect to AWS Services you will need to ensure that it meets all requirements from SAP to enable SSL communications.

You can find a detailed guide in how to configure SSL in ABAP System in the following SAP Help Guide:

All communications from the SAP Server to AWS will be done through HTTPS protocol and using SSL (Secure Sockets Layer), a communication method whereby secure communication between system entities is accomplished by the use of encryption facilitated by X.509 certificates published by Certificate Authorities (CA) in tandem with public and private decryption keys.

  • Ensure that all mandatory prerequisites are met before continuing with the AWS Connector for SAP installation.

    1. Check the minimum SAP Version required

      • SAP Netweaver 7.0 or higher (SAP Kernel release 720 or higher)
      • SAP S/4HANA 1609 or higher (SAP Kernel release 753 or higher)
      • BW/4HANA 1.0
      • BW/4HANA 2.0
      • SAP SLT on SAP Netweaver 7.40 or higher
      • EHP3 FOR SAP CRM 7.0
    2. The Change and Transport System (CTS) is configured correctly and there is enough free space in the transport directory (UNIX: /usr/sap/trans).

    3. You are using the latest version or at least SP58 of the SAP Add-On Installation Tool.

    4. Ensure that SAP Cryptographic Library is properly installed (minimum CommonCryptoLib version 8.4.38, recommended 8.4.49)

      More information: SAP Note 1848999 - Central Note for CommonCryptoLib 8 (SAPCRYPTOLIB)
    5. Check that your SAP Server is ready to run ABAP Webdynpros

      More information: SAP Note 1088717 - Active services for Web Dynpro ABAP in transaction SICF
    6. Both ICM Services HTTP and HTTPS must be configured and active

    7. You must be able to connect to client 000 with a user with enough privileges to install the AddOn.

    8. (optional) KMS Encryption profile parameters. If you want to use KMS for encryption, following parameters must be configured in the SAP default or instance profile.

      ssl / ciphersuites = 135: PFS: HIGH :: EC_P256: EC_HIGH
      ssl / client_ciphersuites = 150: PFS: HIGH :: EC_P256: EC_HIGH
      icm / HTTPS / client_sni_enabled = TRUE
      ssl / client_sni_enabled = TRUE
      More information: SAP Note 510007 - Additional considerations for setting up SSL on Application Server ABAP
    9. Connectivity to AWS services granted. See Ensure your server can reach AWS endpoints Section

    10. Import the Amazon SSL Certificates into the STRUST transaction (skip this step if you plan to automate this process with AWS Connector for SAP)

      To establish outgoing connections that use SSL, the AS ABAP must possess an SSL client PSE. There are different types of SSL client PSEs that the server can use (that is, standard, individual, or anonymous). The standard SSL client PSE is used by default, so we recommend creating this PSE, even if it is not explicitly being used at this time.

      For AS ABAP to establish connections with AWS Services the following parameters should be downloaded and stored in the STRUST transaction.

      Importing certificates to SAP STRUST transaction

      You can perform this action manually by downloading and adding the certificates to the STRUST transaction following SAP Note 2521098 - How to import a certificate in Abap using STRUST transaction

      Or you can leverage the process to SAP by configuring /LNKAWS/AWS_STRUST report to do it following instructions in Configure Add-On section.

      Certificate list

      Root Certificates
      AWS Core Services Certificates

      Additionally to the AWS Core certificates, the specific certificates for the region where your AWS resources are created must be downloaded also and stored in STRUST transaction.

      AWS Regional Service Endpoints Certificates

      Example if your resources are stored in eu-west-1 region.

4. (optional) Install required software in your server to download Amazon SSL Certificates #

This section describes the needed software needed to allow the SAP Server to download the proper Amazon SSL Certificates from its specific endpoints. AWS Connector will use the listed software packages to retrieve the certificate information to import them into the Strust transaction.

Attention Required. These steps are only required if you plan to manage the Amazon SSL Certificate (See Configure Automatic Amazon SSL Certificates Lifecycle Management for more information) through AWS Connector for SAP. If you plan to upload the certificates manually to STRUST transaction in your SAP, you can skip this section.

Ensure that the following packages are installed and accessible with the SAP Administrator User sidadm.

  1. Amazon S3 Endpoint certification retrieval (OpenSSL)

    Minimum version recommended Official Website

    Proxy Requirements.

    If the server must use a Proxy to access the internet, then, at least, OpenSSL version 1.1.0 is mandatory. If the operating system only supports older versions of OpenSSL, it can be bypassed by installing proxytunnel or similar software in the system.

    You can find your current OpenSSL version by executing the following command

    openssl version

    Output sample:

    OpenSSL 1.1.1h FIPS 22 Sep 2020
  2. CA and Issuer Certification retrieval (WGET)

    Minimum version recommended Official Website

    You can find your current WGET version by executing the following command

    wget --version

    Output sample:

    GNU Wget 1.20.3 built on linux-gnu.
    -cares +digest +gpgme +https +ipv6 +iri +large-file +metalink +nls 
    +ntlm +opie +psl +ssl/gnutls