# AWS Data Provider for SAP AWS Data Provider AWS Data Provider for SAP is a tool that collects performance-related data from AWS services. It makes this data available to SAP applications to help monitor and improve the performance of business transactions. SAP requires customers to install the agent as described in SAP note [1656250](https://me.sap.com/notes/1656250) (login credentials required). The AWS Data Provider for SAP uses operating system, network, and storage data that is most relevant to the operation of the SAP infrastructure. Its data sources include Amazon Elastic Compute Cloud (Amazon EC2) and Amazon CloudWatch. This guide provides installation, configuration, and troubleshooting information for the AWS Data Provider for SAP on both Linux and Windows. # Introduction Many organizations of all sizes are choosing to host key SAP systems in the Amazon Web Services Cloud. With AWS, you can quickly provision an SAP environment. Additionally, the elastic nature of the AWS Cloud enables you to scale computing resources up and down as needed. As a result, your business can dedicate more resources (both people and funds) to innovation. Many SAP systems operate daily business transactions and are critical to business functions. As an SAP customer, you need the ability to track and troubleshoot the performance of these transactions. The AWS Data Provider for SAP is a tool that collects key performance data on an [Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2) (Amazon EC2) instance that SAP applications can use to monitor transactions built by SAP. The data is collected from a variety of sources within your AWS Cloud operating environment, including Amazon EC2 and [Amazon CloudWatch](https://aws.amazon.com/cloudwatch). This data includes information about the operating system, network, and storage that is relevant to your SAP infrastructure. Data from the AWS Data Provider for SAP is read by the SAP Operating System Collector (SAPOSCOL) and the SAP CIM Provider. The diagram provides a high-level illustration of the AWS Data Provider for SAP, its data sources, and its outputs. **Data sources for the AWS Data Provider for SAP** ![\[Data sources for the Data Provider for SAP\]](http://docs.aws.amazon.com/sap/latest/general/images/dataprovider-arch.png) The purpose of this guide is to help you: + Understand the technical requirements and components necessary to install and operate the AWS Data Provider for SAP. + Install the AWS Data Provider for SAP. + Understand the update process for the AWS Data Provider for SAP. + Troubleshoot installation issues. ## Pricing The DataProvider agent is provided free of charge. However, there are indirect costs associated with running the agent due to SAP requiring monitoring data to be delivered at specific intervals. This causes the DataProvider to do frequent **GetMetric** calls to Amazon CloudWatch and the Amazon EC2 API to retrieve the metric data. The expected costs for these calls ranges approximately from **\$120.00 to \$140.00** per month per system and will vary based on how many disks are attached to the Amazon EC2 instance. Example: Costs per month for using the DataProvider agent in the US East (N. Virginia) Region. **Fixed:** + Running the 2 required Amazon VPC endpoints (monitoring, Amazon EC2) is approximately **\$114.00 \$1 \$10.01** per processed GB of data. **Note** These endpoints only need to be created once and are shared by the entire landscape. If you are already using these endpoints, you do not need to create them again. **Per System:** + You should expect around 70,000 API calls a day per instance (with 6 disks attached. At **\$10.01** per 1,000 calls, it is approximately **\$121.00** per month. The API call number increases or decreases based on the number of disks that are attached. # Technical Requirements Before creating an SAP instance, ensure that the following technical requirements are met. **Topics** + [ ## Amazon VPC Network Topologies ](#data-provider-vpc-network-topology) + [ ## Amazon VPC Endpoints ](#vpc-endpoints) + [ ## IAM Roles ](#data-provider-iam-roles) ## Amazon VPC Network Topologies You need to deploy SAP systems that receive information from the AWS Data Provider for SAP within an [Amazon Virtual Private Cloud](https://aws.amazon.com/vpc) (Amazon VPC). You can use one of the following network topologies to enable routing to internet-based endpoints: + The first topology configures routes and traffic directly to the AWS Cloud through a NAT gateway within an Amazon VPC. For more information about internet gateways, see the [AWS documentation](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Internet_Gateway.html). **Connection to the AWS Cloud via an internet gateway** ![\[An example cloud connection via an internet gateway\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-internet-gateway.png) + A second topology routes traffic from the Amazon VPC, through your organization’s on-premises data center, and back to AWS Cloud. For more information about this topology, see the [What is AWS Site-to-Site VPN?](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_VPN.html) **Connection to the Amazon Web Services Cloud via an on-premises data center** ![\[Connection to the Amazon Web Services Cloud via an on-premises data center\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-data-center.png) ## Amazon VPC Endpoints Create endpoints for the following services that the DataProvider uses: + Monitoring + Amazon EC2 To create data endpoints in the AWS console, use the following procedure for each of the two endpoints: 1. Sign in to the [Amazon VPC console](https://console.aws.amazon.com/vpc), navigate to **Endpoints**, and select **Create Endpoint**. 1. On the next screen, search for the service name, then select the appropriate VPC and route table, and select **Create Endpoint**. 1. After creating all three endpoints you should see them in your list of endpoints as shown below: ## IAM Roles You need to grant the AWS Data Provider for SAP read-only access to the Amazon CloudWatch, Amazon Simple Storage Service (Amazon S3), and Amazon EC2 services so that you can use their APIs. You can do this by creating an AWS Identity and Access Management (IAM) role for your Amazon EC2 instance and attaching a permissions policy. Use the following procedure to create an IAM role and grant permissions to your Amazon EC2 instance: 1. Sign in to the [AWS Management Console](https://aws.amazon.com/console/) and open the [IAM console](https://console.aws.amazon.com/iam). 1. In the navigation pane, select **Roles**, and select **Create role**. 1. Choose the ** AWS service** role type, and select **EC2**. 1. Select **EC2** as the use case, and select **Next Permissions**. 1. Select **Create Policy**, and select **JSON**. 1. Copy and paste the following policy into the input field, replace all existing text, and select **Review Policy**. **Note** If your Amazon EC2 instances are running in Beijing and Ningxia, you must update the **Resource line** with the correct region. See the following example policies based on your AWS Region. ** AWS Regions (except AWS GovCloud (US-East), AWS GovCloud (US-West), Beijing and Ningxia)** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "EC2:DescribeInstances", "cloudwatch:GetMetricStatistics", "EC2:DescribeVolumes" ], "Resource": "*" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:GetObject", "Resource": [ "arn:aws:s3:::aws-sap-dataprovider-us-east-1/config.properties" ] } ] } ``` **Beijing and Ningxia** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "EC2:DescribeInstances", "cloudwatch:GetMetricStatistics", "EC2:DescribeVolumes" ], "Resource": "*" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:GetObject", "Resource": [ "arn:aws-cn:s3:::aws-sap-dataprovider-cn-north-1/config.properties" ] } ] } ``` ** AWS GovCloud (US-East) and AWS GovCloud (US-West)** ``` { "Version":"2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "EC2:DescribeInstances", "cloudwatch:GetMetricStatistics", "EC2:DescribeVolumes" ], "Resource": "*" }, { "Sid": "VisualEditor1", "Effect": "Allow", "Action": "s3:GetObject", "Resource": [ "arn:aws-us-gov:s3:::aws-sap-dataprovider-us-gov-west-1/config.properties" ] } ] } ``` 1. Provide a **Name** and **Description** for the role, and select **Create Policy**. 1. Select **Create Policy**. The IAM console confirms the new policy with a message similar to the following. 1. Navigate to the **Create Role** page, refresh the screen, search for the newly created role, and select the policy. 1. Select **Next:Tags**. 1. Add any tags if needed, otherwise select **Next:Review**. 1. Provide a name for the Role and select **Create Role**. # DataProvider 4.3 If you are new to AWS Data Provider for SAP, see [Installing DataProvider 4.3](data-provider-installation.md). If you need to update or uninstall DataProvider 4.3, see [Updating to DataProvider 4.3](data-provider-update.md). If you have an older version on your system, see [Uninstalling older versions](uninstall-older-dp.md). **Important** All the previous versions (v1, v2, v3) of the DataProvider have been deprecated and will no longer receive updates. For new DataProvider installations, you must install DataProvider 4.3 using an SSM distributor. **Run the following command to check the current version of DataProvider on your system.** ``` rpm -qa | grep aws-sap ``` To check the current version of DataProvider on **Windows**, go to **Services(Local)**, select ** AWS Data Provider for SAP**, and open **Properties**. You can see the current version in the Description field. ![\[Data sources for Data Provider for SAP\]](http://docs.aws.amazon.com/sap/latest/general/images/check-data-provider-on-windows.png) # Installing DataProvider 4.3 The AWS Data Provider for SAP runs as a service that automatically starts at boot and collects, aggregates, and exposes metrics to the SAP host agent. Metrics are sourced from a variety of providers that pull metrics from the relevant areas of the platform. The AWS Data Provider for SAP is designed to continue operating, regardless of whether its providers have connectivity or permissions to access the AWS service metrics they are requesting. Providers that cannot reach the metrics they are harvesting return blank values. For example, if your Amazon EC2 instance does not have an IAM role associated with it that grants explicit access to the Amazon CloudWatch **GetMetricStatistics** API, the CloudWatch provider will be unable to perform the **GetMetricStatistics** action on the Amazon EC2 instance and will return blank values. The provider needs to be installed on each SAP production system in order to be eligible for SAP support. You can only install one instance of the provider at a time on a system. The AWS Data Provider for SAP is designed to automatically update itself so that it can provide you with the most current metrics. When the AWS Data Provider for SAP starts up, a built-in update service retrieves the latest versions of its components and metric definitions from an AWS managed Amazon S3 bucket. If the AWS Data Provider for SAP cannot access the update service, it will continue to run as-is. ## Installing with an SSM distributor – DataProvider 4.3 (Recommended) The DataProvider 4.3 version enables you to install the package through a SSM distributor. AWS recommends using this method for installation, you can install the DataProvider using a either a Linux or Windows platform. ### Prerequisites for installing the DataProvider using a SSM distributor #### SSM-Agent You must have the `ssm-agent` installed on your instance before you can use the SSM distributor to install the DataProvider Agent. Use the following AWS Systems Manager user guide to install the `ssm-agent` on your instances. + RHEL: [Manually installing SSM Agent on Red Hat Enterprise Linux instances](https://docs.aws.amazon.com/systems-manager/latest/userguide/agent-install-rhel.html) + SUSE: [Manually install SSM Agent on SUSE Linux Enterprise Server instances](https://docs.aws.amazon.com/systems-manager/latest/userguide/agent-install-sles.html) + Oracle : [Manually installing SSM Agent on Oracle Linux instances](https://docs.aws.amazon.com/systems-manager/latest/userguide/agent-install-oracle.html) + Windows: [Manually installing SSM Agent on Amazon EC2 instances for Windows Server](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-install-win.html) #### Java Runtime The DataProvider is a java application that needs Java Runtime to be installed on the instance to run. If your instance doesn’t already have Java Runtime installed, you can use OpenJDK provided by Amazon Corretto to install the Java Runtime. With DataProvider 4.3, the following Java Runtime versions are supported: + Amazon Corretto 8 or OpenJDK 8 + Amazon Corretto 11 or OpenJDK 11 + Amazon Corretto 17 or OpenJDK 17 For more information on how to download and install JDK on your Amazon EC2 instance, see [Amazon Corretto Documentation](https://docs.aws.amazon.com/corretto/index.html). In the terminal, run the following commands to verify installation. ``` java -version ``` For example, expected output for Coretto-8.252.09.1 should be as follows: ``` openjdk version "1.8.0_252"OpenJDK Runtime Environment Corretto-8.252.09.1 (build 1.8.0_252-b09)OpenJDK 64-Bit Server VM Corretto-8.252.09.1 (build 25.252-b09, mixed mode) ``` #### GPG Key If you are a SUSE user, you must download the DataProvider GPG key and import it before installation. + GPG Key URL: [GPG Key](https://aws-sap-data-provider.s3.amazonaws.com/Installers/RPM-GPG-KEY-AWS) + Sign in to your SUSE instance and run the following commands to import the key: ``` wget https// ``` ``` rpm --import RPM-GPG-KEY-AWS ``` ## Installing the DataProvider Agent using an SSM distributor Use the following procedure to install DataProvider 4.3. 1. Open the [Systems Manager console](https://console.aws.amazon.com//systems-manager/). 1. In the left navigation pane, under the Node Management section, choose **Distributor**. ![\[The navigation pane\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-distributor.png) 1. In the search bar, type **AWSSAPTools-DataProvider**, and choose the package. ![\[The search bar\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-package.png) 1. To receive auto updates for the DataProvider when there is a new release, choose **Install on a schedule**. ![\[The details page\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-schedule.png) 1. On the **Create Association** page, type a **Name** for your association. ![\[The Create Association page\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-association.png) 1. In the **Parameters** section, for **Action**, choose **Install**. ![\[The Parameters section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-parameters.png) 1. In the >**Targets** section, for **Target selection**, select **Choose instances manually**. Then, choose the instances where you want to install the DataProvider. ![\[The targets section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-instances.png) 1. In the **Specify schedule** section, make the following selections: + Choose **On Schedule** + For **Specify with**, choose **Rate schedule builder**. + For **Associate runs**, choose **30 days**. (AWS recommends 30 days) ![\[The Specify schedule section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-schedule-selection.png) 1. In the **Output options **section, choose **Create Association**. ![\[The Output options section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-create.png) 1. Once the association is created, choose the **Association ID**. ![\[The Associations list\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-association-id.png) 1. Choose the **Execution History** tab. Then, choose the Execution id. ![\[Execution history tab\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-execution.png) 1. On the **Execution ID** page, choose **Output** to see the installation results. ![\[Example output in the user interface\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-output.png) 1. Once the installation is completed, log in to the instance, and http://localhost:8888/vhostmd [call the endpoint] to enable the DataProvider to fetch metrics. + Linux example ![\[Example output from a Linux terminal\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-linux-example.png) + Windows example ![\[Example output from a browser on a Windows instance\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-example.png) ## Installing with Downloadable Installer – DataProvider 4.3 If you choose to not use SSM to install the DataProvider 4.3, you can manually install the DataProvider using the following procedure. **Note** Before beginning the manual installation you must install the items listed in the [Prerequisites](#prerequisites-ssm) section. You don’t need to install the `SSM-Agent`. The downloadable DataProvider will not provide auto-updates, to get the latest versions, you must manually check for and download new releases manually. Download the following file for your environment. By default the files will download in the us-east-1 region, change the default region before downloading if you want the files to download in a different region. + **Red Hat** [https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/RHEL/aws-sap-dataprovider-rhel-standalone.x86_64.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/RHEL/aws-sap-dataprovider-rhel-standalone.x86_64.rpm) + **SUSE** [https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/SUSE/aws-sap-dataprovider-sles-standalone.x86_64.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/SUSE/aws-sap-dataprovider-sles-standalone.x86_64.rpm) + **Oracle Linux** [https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/ORACLE/aws-sap-dataprovider-oel-standalone.x86_64.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/ORACLE/aws-sap-dataprovider-oel-standalone.x86_64.rpm) + **Windows** https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/win/aws-data-provider-installer-win-x64-Standalone.exe + **GPG Key** [GPG Key: https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/RPM-GPG-KEY-AWS](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/RPM-GPG-KEY-AWS) ## Installing on Linux On Linux the data provider is delivered as an RPM package. ### SUSE Linux Enterprise Server To install the AWS Data Provider for SAP on SUSE Linux Enterprise Server (SLES) download the following files: + **Standard:** [aws-sap-dataprovider-sles.x86\$164.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/SUSE/aws-sap-dataprovider-sles-standalone.x86_64.rpm) and [GPG Key](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/RPM-GPG-KEY-AWS) + **China:** [aws-sap-dataprovider-sles.x86\$164.rpm](https://aws-sap-dataprovider-cn-north-1.s3.cn-north-1.amazonaws.cn/v4/installers/linux/SUSE/aws-sap-dataprovider-sles-standalone.x86_64.rpm) and [GPG Key](https://aws-sap-dataprovider-cn-north-1.s3.cn-north-1.amazonaws.cn/v4/installers/RPM-GPG-KEY-AWS) The files are identical but AWS offers these two location options due to possible connectivity issues when working from China. To install the data provider run the following commands: ``` wget https:// wget https:// rpm ––import RPM-GPG-KEY-AWS zypper install -y ``` Example: ``` wget https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/SUSE/aws-sap-dataprovider-sles-standalone.x86_64.rpm wget https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/RPM-GPG-KEY-AWS rpm ––import RPM-GPG-KEY-AWS zypper install -y aws-sap-dataprovider-sles-standalone.x86_64.rpm ``` When the RPM package is installed, the agent starts as a daemon, as seen in the following image. **RPM package installation** ![\[Starting the aws-dataprovider service as systemd\]](http://docs.aws.amazon.com/sap/latest/general/images/rpm-package-install.png) Verify that the service is running by calling `netstat -ant` to determine if the listener is running on localhost port 8888. **Verifying installation on Linux** ![\[Output of netstat -ant with a listener on port 8888\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-linux-install.png) You should also view the log files at `/var/log/aws-dataprovider/messages.0` to ensure the daemon has the appropriate connectivity and authorization to access the required metrics. **Verifying connectivity and authorization on Linux** ![\[Example log file\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-connectivity-linux.png) At startup, the monitoring agent runs three sets of diagnostics: + The AWS connectivity diagnostic ensures network connectivity to Amazon S3 for obtaining automatic updates to the AWS Data Provider for SAP. + The second diagnostic tests for authorization to access CloudWatch. This authorization requires assigning an IAM role to the Amazon EC2 instance you are running on with an IAM policy that allows access to CloudWatch. For details, see [IAM Roles](data-provider-req.md#data-provider-iam-roles), earlier in this guide. + The third diagnostic tests for authorization to access Amazon EC2, which also requires an IAM role associated with the Amazon EC2 instance. The AWS Data Provider for SAP is designed to run with or without connectivity, but you can’t obtain updates without connectivity. Amazon CloudWatch and Amazon EC2 will return blank values if you don’t have the proper authorizations in place. You can also call the AWS Data Provider for SAP directly to view the metrics. Calling `wget http://localhost:8888/vhostmd` returns a file of metrics. You can look inside the file to see the metrics that were returned, as shown here. **Viewing metrics on Linux** ![\[Example metrics output on Linux\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-linux-view-metrics.png) The AWS Data Provider for SAP now starts automatically each time the operating system starts. You can also manually stop and restart the AWS Data Provider for SAP with the following command, which depends on your operating system version: + SLES 11, Oracle Linux 6, and Red Hat Linux 6: ``` service aws-dataprovider [start|stop] ``` + SLES 12, SLES 15, Oracle Linux 7, Oracle Linux 8, Red Hat Linux 7, and Red Hat Linux 8. ``` systemctl [start|stop] aws-dataprovider ``` You can configure AWS Data Provider to use proxies if you do not have transparent HTTP/HTTPS access to the internet. 1. Stop AWS Data Provider for SAP. 1. Enter proxy information in the file (as seen below) located at `/usr/local/ec2/aws-dataprovider/proxy.properties`. ``` #proxy.properties #used to set web proxy settings for the {aws} Data Provider for SAP #Https is the only supported proxy method #Blank values for everything means no proxy set https.proxyHost= https.proxyPort= https.proxyDomain= https.proxyUsername= https.proxyPassword= ``` 1. Start AWS Data Provider for SAP. ## Installing on Red Hat and Oracle Enterprise Linux For Red Hat and Oracle Enterprise Linux, the installation steps are the same as described for SLES above but the RPM file and command to install the RPM package differs. + **Red Hat** **Default:** [aws-sap-dataprovider-rhel.x86\$164.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/RHEL/aws-sap-dataprovider-rhel-standalone.x86_64.rpm) + **Oracle Enterprise Linux** **Default:** [aws-sap-dataprovider-oel.x86\$164.rpm](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/linux/ORACLE/aws-sap-dataprovider-oel-standalone.x86_64.rpm) To install the data provider run the following commands: ``` wget https:// yum -y install ``` Example: ``` wget https://aws-sap-data-provider.s3.amazonaws.com/Installers/aws-sap-dataprovider-rhel.x86_64.rpm yum -y install aws-sap-dataprovider-rhel.x86_64.rpm ``` ## Installing on Windows On Windows, the installer is delivered in the form of an NSIS (Nullsoft Scriptable Install System) executable. 1. Open a web browser and download the installer: + **Default:** [aws-data-provider-installer-win-x64.exe](https://aws-sap-dataprovider-us-east-1.s3.us-east-1.amazonaws.com/v4/installers/win/aws-data-provider-installer-win-x64-Standalone.exe) 1. Run the downloaded **exe** file. 1. Verify the installation. + Once the installation is complete, you can see the file in `C:\Program Files\Amazon\DataProvider` directory. + The installation also creates and starts a Windows service called ** AWS Data Provider for SAP**. + Verify that the service is running by entering http://localhost:8888/vhostmd in a web browser. The page returns metrics from AWS Data Provider for SAP if your installation is successful. 1. You can configure AWS Data Provider to use proxies if you do not have transparent HTTP/HTTPS access to the internet. 1. Stop AWS Data Provider for SAP. 1. Enter proxy information in the file (as seen below) located at `C:\Program Files\Amazon\DataProvider\proxy.properties`. ``` #proxy.properties #used to set web proxy settings for the {aws} Data Provider for SAP #Https is the only supported proxy method #Blank values for everything means no proxy set https.proxyHost= https.proxyPort= https.proxyDomain= https.proxyUsername= https.proxyPassword= ``` 1. Start AWS Data Provider for SAP. 1. Verify that the service is running by calling `netstat -ant` from a command window or from a Windows PowerShell script to determine if the listener is running on localhost port 8888. ![\[Verifying the installation on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-windows.png) **Verifying the installation on Windows** 1. Navigate to the Windows event log, and find the application log for startup events from the AWS Data Provider for SAP. Check the diagnostics. ![\[Checking diagnostics on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-diagnostic.png) **Checking diagnostics on Windows** At startup, the monitoring agent runs three sets of diagnostics: + The AWS connectivity diagnostic ensures network connectivity to Amazon S3 for obtaining automatic updates to the AWS Data Provider for SAP. + The second diagnostic tests for authorization to access CloudWatch, which requires assigning an IAM role to the EC2 instance you are running on with an IAM policy that allows access to CloudWatch. For details, see [IAM Roles](data-provider-req.md#data-provider-iam-roles), earlier in this guide. + The third diagnostic tests for authorization to access Amazon EC2, which also requires an IAM role associated with the Amazon EC2 instance. The AWS Data Provider for SAP is designed to run with or without connectivity, but you can’t obtain updates without connectivity. If you don’t have the proper authorizations in place, Amazon CloudWatch and Amazon EC2 return blank values. You can also call the AWS Data Provider for SAP directly from your web browser to view metrics, as shown in the figure. **Viewing metrics on Windows** ![\[Example metrics output on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-view-metrics.png) AWS Data Provider for SAP now starts automatically each time the operating system starts. You can also manually stop and restart the AWS Data Provider for SAP, just as you would stop and restart any other Windows service. **Stopping and restarting the AWS Data Provider for SAP on Windows** ![\[Stopping and restarting Data Provider for SAP on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-stop-start.png) In order to configure proxy settings, you can place a customized `proxy.properties` file in Window’s temp directory, which is designated by the windows system variable %TEMP%. ## Subscribe to AWS Data Provider Agent for notifications Amazon Simple Notification Service can notify you when new versions of AWS Data Provider Agent are released. Use the following steps to setup this subscription. 1. Open https://console.aws.amazon.com/sns/v3/home. 1. Ensure that you are in **US East N. Virginia** (us-east-1) Region. 1. In the left navigation pane, select **Subscriptions** > **Create subscription**. 1. Add a **Topic ARN** based on the AWS Region in which you are using AWS Data Provider Agent. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/sap/latest/general/data-provider-installation.html) 1. **Protocol** – choose Email or SMS. + **Email** – enter an email address where you would like to receive the notification in the **Endpoint** field. **Note** To enable email notifications, you must confirm your email subscription by following the instructions you receive on the provided email address. + **SMS** – enter a phone number where you would like to receive the notification in the **Endpoint** field. 1. Choose **Create subscription**. You can now receive notifications whenever a new version of AWS Data Provider Agent is released. To unsubscribe from notifications, use the following steps. 1. Open https://console.aws.amazon.com/sns/v3/home. 1. In the left navigation pane, select **Subscriptions**. 1. Select the subscription from your list of subscriptions and choose **Delete**. # Updating to DataProvider 4.3 If you have previously installed DataProvider 2.0 or 3.0 and want to update to DataProvider 4.3, you need to uninstall the running version first, and then install DataProvider 4.3. ## Updating to DataProvider 4.3 using the SSM Distributor package When you install DataProvider 4.3 through the SSM distributor, it will auto-update the installed package on a new version release. For more information, see [Install or update packages](https://docs.aws.amazon.com/systems-manager/latest/userguide/distributor-working-with-packages-deploy.html). To update the DataProvider 4.3 manually, you must first uninstall the running version and then install the updated version. **DataProvider 4.3 does *not* support the following actions:** + Manual update of the RPM package if the DataProvider has been installed using the SSM distributor. + Automatic update through the SSM distributor if the DataProvider has been manually installed using RPM. + Manual update of the RPM package in any scenario. ## Uninstall DataProvider 4.3 using the SSM distributor 1. Open the [AWS Systems Manager](https://console.aws.amazon.com/systems-manager/) console, on the left navigation pane, choose **State Manager**. ![\[The navigation pane\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-state-manager.png) 1. On the **Associations** page, and choose the **Association id**. Then, choose **Delete**. After the delete is successful, the auto-update stops. ![\[The Associations page\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-delete.png) 1. On the main page, in the left navigation page, choose **Distributor**. ![\[The navigation pane\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-distributor-1.png) 1. Choose the **AWSSAPTools-DataProvider** distributor package, and choose **Install one time**. ![\[The package details page\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-install-one-time.png) 1. In the **Command parameters** section, choose **Uninstall**. ![\[The Command parameters section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-command-parameters.png) 1. In the **Targets** section, select **Choose instances manually**. Then choose the **instance** to uninstall the DataProvider. ![\[The Targets section\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-choose-instance.png) 1. Choose **Run** to begin the uninstall. ## Uninstall DataProvider 4.3 manually **RedHat** ``` yum erase aws-dataprovider-standalone ``` **SUSE** ``` zypper rm aws-dataprovider-standalone ``` **Windows** 1. Run the uninstaller. ``` C:\Program Files\AmazonA\DataProvider\uninstall.exe ``` 1. When prompted, choose **Uninstall**. **Uninstalling the AWS Data Provider for SAP on Windows** ![\[Uninstalling Data Provider for SAP on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-uninstall-windows.png) # Uninstalling older versions Uninstalling the AWS Data Provider for SAP does not require SAP downtime and can be done online. The only impact will be a gap in metric monitoring information for the time that the DataProvider was installed on your system. ## Uninstall DataProvider 3.0 **Linux** 1. Log in to Linux as a superuser, like root. 1. Stop and remove the DataProvider using the following command. **SLES** ``` zypper remove -y aws-sap-dataprovider ``` **RHEL/OEL** ``` yum -y erase aws-sap-dataprovider ``` **Windows** ``` “C:\Program Files\Amazon\DataProvider\uninstall.exe“ ``` ## Uninstall DataProvider 2.0 **Linux** 1. Log in to Linux as a superuser, like root. 1. Stop and remove the DataProvider using the following command. ``` /usr/local/ec2/aws-agent/bin/aws-agent_uninstall ``` **Windows** ``` “C:\Program Files\Amazon\DataProvider\uninstall.exe“ ``` # Troubleshooting This section provides help to analyze installation problems. ## Troubleshooting on Linux ### Problem: The installation failed, and I’m not sure if my files are in a consistent state. Stop and remove the Data Provider with the following command. SLES: ``` zypper remove -y aws-sap-dataprovider ``` RHEL / OEL: ``` yum -y erase aws-sap-dataprovider ``` ### Problem: The AWS Data Provider for SAP failed to start at the end of the installation process. Check the log files in `/var/log/aws-dataprovider` for hints on what is not going as expected. If needed, uninstall and reinstall the Data Provider. If reinstalling the AWS Data Provider for SAP doesn’t solve the problem, you can gather debug information about the AWS Data Provider for SAP by editing the `/usr/local/ec2/aws-dataprovider/bin/aws-dataprovider` file. **Debugging the installation on Linux** ![\[Debugging the installation on Linux\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-debug-linux.png) Now if you run service `aws-dataprovider-start` or `systemctl start aws-dataprovider`, you will get a lot of debugging output that might help you diagnose the root cause of the problem. **Debugging information on Linux** ![\[Debugging information on Linux\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-debug-linux2.png) ### Problem: When I looked at my logs I noticed that my installation failed all diagnostics. **Symptoms of internet connectivity problems on Linux** ![\[Symptoms of internet connectivity problems on Linux\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-linux-internet-problem.png) Failing *all* diagnostics indicates that there’s a problem with your outbound connection to the internet. You can confirm this by pinging a well-known internet location, like [www.amazon.com.](http://www.amazon.com/) The most common cause of routing issues is in the VPC network configuration, which needs to have either an internet gateway in place or a VPN connection to your data center with a route to the internet. For details, see [Amazon VPC Network Topologies](data-provider-req.md#data-provider-vpc-network-topology), earlier in this guide. ### Problem: When I looked at my logs I noticed that I don’t have access to CloudWatch and Amazon EC2, but I did pass the first diagnostic for AWS connectivity. **Symptoms of authorization issues on Linux** ![\[Symptoms of authorization issues on Linux\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-linux-authorization-problem.png) This is a clear indicator that you have an authorization issue when trying to access CloudWatch and Amazon EC2. The common cause for this problem is not having an IAM role associated with your instance that contains the IAM policy, as specified in [IAM Roles](data-provider-req.md#data-provider-iam-roles), earlier in this guide. You can quickly diagnose this issue by looking at the Amazon EC2 instance in question in the Amazon EC2 console and verifying the IAM role. **Verifying the IAM role for an EC2 instance** ![\[Verifying the IAM role for an EC2 instance\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-iam-role.png) If the IAM role doesn’t exist, then create it as specified in IAM Roles, which is described earlier in this guide. If you do have an IAM role assigned to the instance, go to the IAM console, select the IAM role name, and then expand the policy. Verify that you have the required policy that is specified in [IAM Roles](data-provider-req.md#data-provider-iam-roles), earlier in this guide. **Verifying the policy for the IAM role** ![\[Verifying the policy for the IAM role\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-iam-policy.png) ### Problem: I want to configure/update `JAVA_HOME` for Data Provider. Open the `/usr/local/ec2/aws-dataprovider/env` file and update the `JAVA_HOME` variable. Restart Data Provider after the update, with the following command. ``` sudo systemctl daemon-reload sudo systemctl start aws-dataprovider ``` ## Troubleshooting on Windows ### Problem: The installation failed, and I’m not sure if my files are in a consistent state. Based on the DataProvider version on your system, follow the procedure in [Updating to DataProvider 4.3](data-provider-update.md) or [Uninstalling older versions](uninstall-older-dp.md). ### Problem: The AWS Data Provider for SAP failed to start at the end of the installation process. If reinstalling the AWS Data Provider for SAP doesn’t solve the problem, you can gather debugging information about the AWS Data Provider for SAP by reviewing the log files in the `C:\Program Files\Amazon\DataProvider` directory. These log files include an installation log, a log of the service installation, and the output of the AWS Data Provider for SAP itself. **Log files on Windows** ![\[Log files on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-log-files.png) ### Problem: I want to get more detailed log information from the data provider. Start by stopping the data provider service. **Stop Service on Windows** ![\[Stop Service on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-stop-service-windows.png) Open the registry editor by clicking on the Windows logo in the bottom left and typing `regedit` and then clicking the option that is shown on screen: **Start ` regedit ` ** ![\[Start regedit\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-start-regedit.png) In the registry, navigate to the key: ``` HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\awsDataProvider\Start ``` **Logging setting** ![\[Logging setting\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-logging-setting.png) The data provider accepts two log levels: INFO and FINE. FINE will generate more detailed logging which can be useful when debugging a problem. The recommendation is to set it back to INFO when you have finished troubleshooting to avoid the logs consuming unnecessary disk space. ### Problem: I want to reinstall the AWS Data Provider for SAP from scratch. Based on the DataProvider version on your system, follow the procedure in [Updating to DataProvider 4.3](data-provider-update.md) or [Uninstalling older versions](uninstall-older-dp.md). ### Problem: When I looked at my logs, I noticed that my installation failed all diagnostics. **Symptoms of internet connectivity problems on Windows** ![\[Symptoms of internet connectivity problems on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-internet-problems.png) Failing *all* diagnostics indicates that there’s a problem with your outbound connection to the internet. You can confirm this by pinging a well-known internet location, like [www.amazon.com.](http://www.amazon.com/) The most common cause of routing issues is in the VPC network configuration, which needs to have either an internet gateway in place or a VPN connection to your data center with a route to the internet. ### Problem: When I looked at my logs, I noticed that I don’t have access to CloudWatch and Amazon EC2, but I did pass the first diagnostic for AWS connectivity. **Symptoms of authorization issues on Windows** ![\[Symptoms of authorization issues on Windows\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-windows-authorization-problems.png) This is a clear indicator that you have an authorization issue when trying to access Amazon CloudWatch and Amazon EC2. The common cause for this problem is not having an IAM role associated with your instance that contains the IAM policy, as specified in [IAM Roles](data-provider-req.md#data-provider-iam-roles) earlier in this guide. You can quickly diagnose this issue by looking at the specific EC2 instance in the Amazon EC2 console and verifying the IAM role. **Verifying the IAM role for an EC2 instance** ![\[Verifying the IAM role for an EC2 instance\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-iam-role-windows.png) If the IAM role doesn’t exist, then create is as specified in IAM Roles, described earlier in this guide. If you do have an IAM role assigned to the instance, go to the IAM console, select the IAM role name, and then choose **Show**. Verify that you have the required policy that is specified in [IAM Roles](data-provider-req.md#data-provider-iam-roles). **Verifying the policy for the IAM role** ![\[Verifying the policy for the IAM role\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-verify-iam-policy-windows.png) # Customizing the AWS Data Provider for SAP Customizing the DataProvider Some settings are hard coded in the AWS Data Provider for SAP. You can override existing settings or add new settings. For example, when AWS adds new instance types, you can add these to the AWS Data Provider for SAP configuration. The AWS Data Provider for SAP creates a database by reading the configuration information from the available `config.properties`, files in this sequence: + The JAR (Java Archive) file of the data provider application. + The installation directory. This file is required only if you want to override or extend the current configuration. The default directories are as follows: + Linux – `/usr/local/ec2/aws-dataprovider/config.properties` + Windows – `C:\Program Files\Amazon\DataProvider\config.properties` + The Regional S3 bucket. Replace with the Region code for the Region (for example, `us-east-1`). ``` https://aws-sap-dataprovider-.s3..amazonaws.com/config.properties ``` ## Syntax Rules for Configuration Files + The configuration files require a comma after the last value in every row. + Spaces are not ignored in strings. The entire string between the commas, including any spaces, is accepted as the value. + If there are multiple rows with the same instance type, the existing value for that type is overwritten. + Capitalization in strings is case sensitive. ## User-Configurable EC2 Instance Types The AWS Data Provider for SAP maintains a database of all relevant Amazon EC2 instance types for SAP. Entries for EC2 instance types must be in a comma-separated list, as follows: *ec2type,i-type,cpu,core,threads,t-ecu,ecu,hthread,l-map,w-map,speed,p-ecu,* For example: ``` ec2type,r3.8xlarge,2,16,2,32,1,thread,eth0,lan2,10000,true, ``` where the following applies: | Field name | Content | Example | Type | Description | | --- | --- | --- | --- | --- | | **keyword** | ec2type |  —  | String | A token to identify a record with an EC2 instance description | | **i-type (instance-type)** | [See list](https://aws.amazon.com/ec2/instance-types/) | r3.8xlarge | String | Instance type, which must match the EC2 instance metadata string | | **cpu (CPUs)** | 1 \$1 2 | 2 | Integer | Number of sockets | | **core (Cores)** | *integer* | 16 | Integer | Total number of processor cores | | **threads (threads per core)** | 1 \$1 2 | 2 | Integer | Threads per core | | **t-ecu (total ECU value)** | *integer* | 32 | Double | ECU value for previous-generation instance types that have ECU ratings; number of cores for post-ECU instance types | | **ecu (ECU per core)** | *double* | 1 | Double | 1 for all post-ECU instance types; total ECU divided by cores for previous- generation instance types that have ECU ratings | | **hthread (hyperthreading)** | thread \$1 core | thread | String | **thread** for hyperthreaded instance types; **core** for non- hyperthreaded instance types | | **l-map (Linux NIC mapping)** | eth0 | eth0 | String | Linux mapping of network interface | | **w-map (Windows NIC mapping)** | eth0 | lan2 | String | Windows mapping of network interface | | **speed (network interface speed)** | 1000 \$1 2000 \$1 10000 | 100000 | Integer | Maximum speed of network interface, in KB | | **p-ecu (post ECU)** | true \$1 false | true | Boolean | **true** for modern instances that don’t have ECU ratings | ## User-Configurable EBS Volume Types The AWS Data Provider for SAP maintains a database of all relevant EBS volume types for SAP. Entries for EBS volume types must be in a comma-separated list, as follows: *voltype,ebs-type,sample-time,* For example: ``` voltype,io1,60, ``` where the following applies: | Field name | Content | Example | Type | Description | | --- | --- | --- | --- | --- | | **keyword** | voltype |  —  | String | A token to identify a record with an EBS volume description | | **ebs-type (EBS-type)** | io1 \$1 gp2 \$1 sc1 \$1 st1 | Io1 | String | EBS type, which must match the EBS volume metadata string | | **sample-time** | 60 \$1 300 | 60 | Integer | CloudWatch sample time, in seconds | **Important** The sample time is required to calibrate the EBS metrics to the SAP monitoring requirements. Changes in the sample time will lead to incorrect EBS metrics in the SAP monitoring system. # Verification of AWS Data Provider for SAP in SAP system monitoring Verification of monitoring The AWS Data Provider for SAP exposes AWS-specific metrics through an XML page at http://localhost:8888/vhostmd of the given system. This section explains which metrics get exposed to the SAP system and how you can access them for SAP system monitoring. ## Checking Metrics with the SAP Operating System Collector (SAPOSCOL) The information provided by the AWS Data Provider for SAP is read by the SAP Operating System Collector ([SAPOSCOL](https://help.sap.com/saphelp_nw70/helpdata/en/c4/3a6bff505211d189550000e829fbbd/frameset.htm)). You can use the interactive mode of SAPOSCOL to verify that the two tools are working together correctly. The following example shows a lookup under Windows. A lookup under Linux is very similar. 1. Open a Windows command shell and direct the shell to the directory `C:\Program Files\SAP\hostctrl\exe`. Start `saposcol.exe` with the `-d` option. **Starting SAPOSCOL** ![\[Starting SAPOSCOL\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-starting-saposcol.png) 1. SAPOSCOL is now in interactive mode. Type `dump ccm` and press **Enter** to list all values gathered. SAPOSCOL will display a lengthy list of metrics, as shown here. **Metrics from SAPOSCOL** ![\[Metrics from SAPOSCOL\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-metrics-saposcol.png) The following two metrics indicate that SAPOSCOL is collaborating successfully with the AWS Data Provider for SAP: + Enhanced Monitoring Access TRUE + Enhanced Monitoring Details ACTIVE The AWS-specific metrics start with the following strings: \$1 + Virtualization\$1Configuration + CPU\$1Virtualization\$1Virtual\$1System + Memory\$1Virtualization\$1Virtual\$1System + System\$1Info\$1Virtualization\$1System ** AWS-specific metrics** ![\[Data Provider metrics\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-aws-metrics-saposcol.png) ## Checking Metrics with the SAP CCMS Transactions SAPOSCOL hands the AWS-enhanced statistics with other operating system-specific metrics to the SAP system. You can also check the AWS-enhanced statistics in the SAP CCMS. You can enter the transaction *st06* (or */nst06*) in the upper-left transaction field of the SAP GUI for quick access to this data. **Note** You will need the appropriate authorizations to look up this information. **Statistics in the SAP CCMS (standard view)** ![\[Statistics in the SAP CCMS (standard view)\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-ccms-standard.png) On this screen, you can verify core AWS information such as: + Cloud provider + Instance type + Status of enhanced monitoring access (must be TRUE) + Status of enhanced monitoring details (must be ACTIVE) + Virtual machine identifier **Important** The enhanced AWS metrics aren’t shown in standard view. To view enhanced AWS statistics, choose the **Standard View** button in the upper-left corner. It changes to **Expert View** and displays the enhanced AWS statistics. The list that appears is comprehensive. It shows the processor details. **Enhanced AWS statistics (expert view)** ![\[Enhanced statistics (expert view)\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-ccms-expert.png) It also shows details about the memory subsystem (main memory and disks) and network interfaces. **Memory and networking statistics (expert view)** ![\[Memory and networking statistics (expert view)\]](http://docs.aws.amazon.com/sap/latest/general/images/data-provider-memory-stats-expert.png) **Note** The screen illustrations in Figures 37–39 were taken from SAP NetWeaver 7.4 SP08. This version shows the enhanced AWS statistics in the **Memory Virtualization** section. This problem has been fixed by SAP in later versions of NetWeaver. # Example of captured metrics This following show example metrics. Your system metrics may slightly differ. ``` Time Stamp 1584376572 Refresh Interval 60 Data Provider Version 3.0.139 Cloud Provider Amazon Web Services Instance Type m5.large Virtualization Solution KVM Virtualization Solution Version ba185a32 CloudWatch Calls 12 EC2 Calls 4 CPU Over-Provisioning no Memory Over-Provisioning no Virtualization Type default-hvm Virtual Machine ID i-################# Last Hardware Change 1572284007 Processor Type Intel(R) Xeon(R) @ 2500MHz Number of Cores per CPU 1 Number of Threads per Core 2 Max HW Frequency 2500 Current HW Frequency 2500 Reference Compute Unit (CU) Intel(R) Xeon(R) @ 2500MHz vCPU Mapping thread Phys. Processing Power per vCPU 1 Guaranteed VM Processing Power 2 Current VM Processing Power 2 Max. VM Processing Power 2 VM Processing Power Consumption 3.00 Guaranteed Memory assigned 8274 Current Memory assigned 8274 Max Memory assigned 8274 VM Memory Consumption 29.00 Memory SwapIn Rate 0 Memory Swapped Out 0 Memory Lent 0 Total Visible Memory -1 Visible Memory Consumed -1 Visible Memory SwapIn Rate 0 Visible Memory Swapped Out 0 Network Read Bytes 54110386 Network Write Bytes 1330726 TCP Packets Retransmitted 396480 Minimum Network Bandwidth 10000 Maximum Network Bandwidth 10000 Mapping lan2 Volume Idle Time 58489 Volume Queue Length 0 Volume Read Bytes 9878528 Volume Read Ops 144 Volume Read Time 246 Volume Write Time 8266 Volume Write Bytes 282332160 Volume Write Ops 3090 Volume Type gp2 Guaranteed IOps 180 Interval 300 Mapping disk0 ``` # Version history **Version 4.3.2 (August, 2023)** + Bug fix : Security updates to address [CVE-2022-45688](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-45688). **Version 4.3.1 (June, 2023)** + Bug fix : Data Provider is now setup for successful installation of SAP JVM. **Version 4.3 (January, 2023)** + Added support for JDK 17 + Added reading configuration information from remote Amazon S3 bucket **Version 4.2 (November, 2022)** + Added support for Oracle and Linux + Added integration with Linux `logrotate` feature + Updates to the RPM package build. **Version 4.1.1 (September, 2022)** + Added support for new Amazon EC2 instance types. **Version 4.1.0 (January, 2022)** + Added support for JDK 11. + Added support for new Amazon EC2 instance types. **Version 4.0.3 (December, 2021)** + Bug fixes: Removed Log4j dependency. **Version 4.0.2 (December, 2021)** + Bug fixes: Security updates for Log4j2 issue (CVE-2021-44228). **Version 4.0 (April, 2021)** + Initial release of the 4.0 version. + Support for SSM package installation. + Support for IMDSv2. **Version 3.0 (April, 2020)** + Initial release of the 3.0 version. + Switched the Java Runtime from Oracle to Amazon Corretto. **Version 2.9 (August 30, 2017)** + Added support for China Regions. + Added Linux uninstaller. + Linux installer can be customized to install from a custom S3 bucket. + Silent installer for Windows (does not require any input). + Improvements in determination of access points. + Support for X1E instance family. **Version 2.8 (March 1, 2017)** + SLES 12, Red Hat 7, and Oracle Linux 7 will now use SYSTEMD to manage the daemon. + Support for SLES and SLES for SAP 12 SP2. + SLES 12 SP1 systems will get migrated from Linux services to SYSTEMD when trying to install the AWS Data Provider without having it de- installed first. + Minor changes in logging texts. + Support for R4 and M4 instance types. + Updated Windows installation verification. **Version 2.7 (December 21, 2016)** + Support for Canada (Central), US East (Ohio), and EU (London) Regions. + Default access point resolution for common AWS Regions is added. **Version 2.6 (September 1, 2016)** + Bug fixes: Installation script checks for existence of wget + Support for Oracle Linux. **Version 2.5 (May 2, 2016)** + Bug fixes: Security and stability fixes in versions 2.2-2.4. + New: Support for new Amazon EBS volume types: + Throughput Optimized HDD (st1) + Cold HDD (sc1) + New: Support for the Amazon EC2 X1 instance family. **Version 2.1 (January 20, 2016)** + Support for Asia Pacific (Seoul) Region. + Bug fix: Version 2.0 pulled files from an incorrect S3 bucket for installation. Version 2.0 needs to be uninstalled before version 2.1 is installed. **Version 2.0 (December 22, 2015)** + New: Windows devices in the range sdb to sdzz get correct SCSI device IDs assigned. + New: Java VM consumption is now limited to 64 MB maximum heap size. **Version 1.3.1 (July 14, 2015)** + Bug fixes: Security fixes. + New: Support for C4, D2, and M4 instance types. Users who migrate instances with installed 1.3 agents will automatically receive support for the new instance types through an updated configuration database on the web. **Version 1.3 (February 17, 2015)** + New: Support for new Amazon EC2 C4 instance family. + Security fix: Upgraded Linux and Windows versions to JRE 8u31. + Bug fix: Relative performance of c3.8xlarge instances is now reported correctly. + New: CloudWatch and Amazon EC2 metrics access points: + Support for the EU (Frankfurt) Region was added. + Access points are user configurable. You can add information about new AWS Regions without having to install a new product version. + Access points are now updated from an internet-based database file. You can add new AWS Regions by updating a web-based configuration file and then restarting the daemon/service. + New: Message log files with fixed disk space consumption are provided on Linux. + New: User-configurable EC2 instance types are available. + New: Web update support was added for future EC2 instance types without product updates. + Bug fix: GP2 volumes now report the correct sample interval time. + New: User-configurable sample times for new EBS volume types are now available. + New: The AWS Data Provider for SAP now reports the virtualization type of the EC2 instance. **Version 1.2.2 (October 1, 2014)** + Windows bug fix: Installer executable pulls installation from correct Amazon S3 bucket. + Windows bug fix: AWS Data Provider for SAP now reports the correct disk mapping for Windows EBS volumes with the following names: xvd[a-z][a-z]. **Version 1.2.1 (September 29, 2014)** + Bug fix: EBS volumes now report correct attribute type ("string") for volume type. **Version 1.2 (September 16, 2014)** + New: Support for the T2, R3, and C3 instance families. + New: Support for post-ECU (EC2 Compute Unit) instance types: + New instance types no longer have ECU values. + The reference compute power for these instance types is a hardware thread of the given processor. The total CPU power is equal to the number of the vCPUs of a given instance type. + New: Support for the new EBS GP2 volume type. + Every volume is now tagged with the EBS volume type. + New: Report of EBS one-minute volume statistics. + EBS volumes now report their individual sample interval in a separate attribute. + Bug fix: EBS volume mapping for Windows devices now reports the correct name. + Bug fix: Installation, update, and operation through HTTP/HTTPS proxies has been fixed. + New: JRE 8 support has been added on Linux.