# Install Amazon IoT Greengrass Core software with Amazon IoT fleet provisioning This feature is available for v2.4.0 and later of the [Greengrass nucleus component](greengrass-nucleus-component.md). With Amazon IoT fleet provisioning, you can configure Amazon IoT to generate and securely deliver X.509 device certificates and private keys to your devices when they connect to Amazon IoT for the first time. Amazon IoT provides client certificates that are signed by the Amazon Root certificate authority (CA). You can also configure Amazon IoT to specify thing groups, thing types, and permissions for Greengrass core devices that you provision with fleet provisioning. You define a *provisioning template* to define how Amazon IoT provisions each device. The provisioning template specifies the thing, policy, and certificate resources to create for a device when provisioning. For more information, see [Provisioning templates](https://docs.amazonaws.cn/iot/latest/developerguide/provision-template.html) in the *Amazon IoT Core Developer Guide*. Amazon IoT Greengrass provides an Amazon IoT fleet provisioning plugin that you can use to install the Amazon IoT Greengrass Core software using Amazon resources created by Amazon IoT fleet provisioning. The fleet provisioning plugin uses *provisioning by claim*. Devices use a provisioning claim certificate and private key to obtain a unique X.509 device certificate and private key that they can use for regular operations. You can embed the claim certificate and private key in each device during manufacturing, so your customers can activate devices later when each device comes online. You can use the same claim certificate and private key for multiple devices. For more information, see [Provisioning by claim](https://docs.amazonaws.cn/iot/latest/developerguide/provision-wo-cert.html#claim-based) in the *Amazon IoT Core Developer Guide*. **Note** The fleet provisioning plugin for [Greengrass nucleus](greengrass-nucleus-component.md) doesn't currently support storing private key and certificate files in a hardware security module (HSM). To use an HSM with [Greengrass nucleus](greengrass-nucleus-component.md), [install the Amazon IoT Greengrass Core software with manual provisioning](manual-installation.md). [Greengrass nucleus lite](greengrass-nucleus-lite-component.md) v2.5.0 and later support TPM with fleet provisioning natively. To install the Amazon IoT Greengrass Core software with Amazon IoT fleet provisioning, you must set up resources in your Amazon Web Services account that Amazon IoT uses to provision Greengrass core devices. These resources include a provisioning template, claim certificates, and a [token exchange IAM role](device-service-role.md). After you create these resources, you can reuse them to provision multiple core devices in a fleet. For more information, see [Set up Amazon IoT fleet provisioning for Greengrass core devices](fleet-provisioning-setup.md). **Important** Before you download the Amazon IoT Greengrass Core software, check that your core device meets the [requirements](greengrass-nucleus-component.md#greengrass-v2-requirements) to install and run the Amazon IoT Greengrass Core software v2.0. **Topics** + [Prerequisites](#fleet-provisioning-prerequisites) + [Retrieve Amazon IoT endpoints](#retrieve-iot-endpoints) + [Download certificates to the device](#download-claim-certificates) + [Set up the device environment](#set-up-device-environment) + [Download the Amazon IoT Greengrass Core software](#download-greengrass-core-v2) + [Download the Amazon IoT fleet provisioning plugin](#download-fleet-provisioning-plugin) + [Install the Amazon IoT Greengrass Core software](#run-greengrass-core-v2-installer-fleet) + [Set up Amazon IoT fleet provisioning for Greengrass core devices](fleet-provisioning-setup.md) + [Configure the Amazon IoT fleet provisioning plugin](fleet-provisioning-configuration.md) + [Amazon IoT fleet provisioning plugin changelog](fleet-provisioning-changelog.md) ## Prerequisites To install the Amazon IoT Greengrass Core software with Amazon IoT fleet provisioning, you must first [set up Amazon IoT fleet provisioning for Greengrass core devices](fleet-provisioning-setup.md). After you complete these steps once, you can use fleet provisioning to install the Amazon IoT Greengrass Core software on any number of devices. ## Retrieve Amazon IoT endpoints Get the Amazon IoT endpoints for your Amazon Web Services account, and save them to use later. Your device uses these endpoints to connect to Amazon IoT. Do the following: 1. Get the Amazon IoT data endpoint for your Amazon Web Services account. ``` aws iot describe-endpoint --endpoint-type iot:Data-ATS ``` The response looks similar to the following example, if the request succeeds. ``` { "endpointAddress": "device-data-prefix-ats.iot.us-west-2.amazonaws.com" } ``` 1. Get the Amazon IoT credentials endpoint for your Amazon Web Services account. ``` aws iot describe-endpoint --endpoint-type iot:CredentialProvider ``` The response looks similar to the following example, if the request succeeds. ``` { "endpointAddress": "device-credentials-prefix.credentials.iot.us-west-2.amazonaws.com" } ``` ## Download certificates to the device The device uses a claim certificate and private key to authenticate its request to provision Amazon resources and acquire an X.509 device certificate. You can embed the claim certificate and private key into the device during manufacturing, or copy the certificate and key to the device during installation. In this section, you copy the claim certificate and private key to the device. You also download the Amazon Root certificate authority (CA) certificate to the device. **Important** Provisioning claim private keys should be secured at all times, including on Greengrass core devices. We recommend that you use Amazon CloudWatch metrics and logs to monitor for indications of misuse, such as unauthorized use of the claim certificate to provision devices. If you detect misuse, disable the provisioning claim certificate so that it can't be used for device provisioning. For more information, see [Monitoring Amazon IoT](https://docs.amazonaws.cn/iot/latest/developerguide/monitoring_overview.html) in the *Amazon IoT Core Developer Guide*. To help you better manage the number of devices, and which devices, that register themselves in your Amazon Web Services account, you can specify a pre-provisioning hook when you create a fleet provisioning template. A pre-provisioning hook is an Amazon Lambda function that validates template parameters that devices provide during registration. For example, you might create a pre-provisioning hook that checks a device ID against a database to verify that the device has permission to provision. For more information, see [Pre-provisioning hooks](https://docs.amazonaws.cn/iot/latest/developerguide/pre-provisioning-hook.html) in the *Amazon IoT Core Developer Guide*. **To download claim certificates to the device** 1. Copy the claim certificate and private key to the device. If SSH and SCP are enabled on the development computer and the device, you can use the `scp` command on your development computer to transfer the claim certificate and private key. The following example command transfers these files a folder named `claim-certs` on your development computer to the device. Replace *device-ip-address* with the IP address of your device. ``` scp -r claim-certs/ device-ip-address:~ ``` 1. Create the Greengrass root folder on the device. You'll later install the Amazon IoT Greengrass Core software to this folder. **Note** Windows has a path length limitation of 260 characters. If you are using Windows, use a root folder like `C:\greengrass\v2` or `D:\greengrass\v2` to keep the Greengrass components paths under the 260 character limit. ------ #### [ Linux or Unix ] + Replace `/greengrass/v2` with the folder to use. ``` sudo mkdir -p /greengrass/v2 ``` ------ #### [ Windows Command Prompt ] + Replace *C:\$1greengrass\$1v2* with the folder to use. ``` mkdir C:\greengrass\v2 ``` ------ #### [ PowerShell ] + Replace *C:\$1greengrass\$1v2* with the folder to use. ``` mkdir C:\greengrass\v2 ``` ------ 1. (Linux only) Set the permissions of the parent of the Greengrass root folder. + Replace */greengrass* with the parent of the root folder. ``` sudo chmod 755 /greengrass ``` 1. Move the claim certificates to the Greengrass root folder. + Replace `/greengrass/v2` or *C:\$1greengrass\$1v2* with the Greengrass root folder. ------ #### [ Linux or Unix ] ``` sudo mv ~/claim-certs /greengrass/v2 ``` ------ #### [ Windows Command Prompt (CMD) ] ``` move %USERPROFILE%\claim-certs C:\greengrass\v2 ``` ------ #### [ PowerShell ] ``` mv -Path ~\claim-certs -Destination C:\greengrass\v2 ``` ------ 1. Download the Amazon root certificate authority (CA) certificate. Amazon IoT certificates are associated with Amazon's root CA certificate by default. ------ #### [ Linux or Unix ] ``` sudo curl -o /greengrass/v2/AmazonRootCA1.pem https://www.amazontrust.com/repository/AmazonRootCA1.pem ``` ------ #### [ Windows Command Prompt (CMD) ] ``` curl -o C:\greengrass\v2\\AmazonRootCA1.pem https://www.amazontrust.com/repository/AmazonRootCA1.pem ``` ------ #### [ PowerShell ] ``` iwr -Uri https://www.amazontrust.com/repository/AmazonRootCA1.pem -OutFile C:\greengrass\v2\\AmazonRootCA1.pem ``` ------ ## Set up the device environment Follow the steps in this section to set up a Linux or Windows device to use as your Amazon IoT Greengrass core device. ### Set up a Linux device **To set up a Linux device for Amazon IoT Greengrass V2** 1. Install the Java runtime, which Amazon IoT Greengrass Core software requires to run. We recommend that you use [Amazon Corretto](https://www.amazonaws.cn/corretto/) or [OpenJDK](https://openjdk.java.net/) long-term support versions. Version 8 or higher is required. The following commands show you how to install OpenJDK on your device. + For Debian-based or Ubuntu-based distributions: ``` sudo apt install default-jdk ``` + For Red Hat-based distributions: ``` sudo yum install java-11-openjdk-devel ``` + For Amazon Linux 2: ``` sudo amazon-linux-extras install java-openjdk11 ``` + For Amazon Linux 2023: ``` sudo dnf install java-11-amazon-corretto -y ``` When the installation completes, run the following command to verify that Java runs on your Linux device. ``` java -version ``` The command prints the version of Java that runs on the device. For example, on a Debian-based distribution, the output might look similar to the following sample. ``` openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment (build 11.0.9.1+1-post-Debian-1deb10u2) OpenJDK 64-Bit Server VM (build 11.0.9.1+1-post-Debian-1deb10u2, mixed mode) ``` 1. (Optional) Create the default system user and group that runs components on the device. You can also choose to let the Amazon IoT Greengrass Core software installer create this user and group during installation with the `--component-default-user` installer argument. For more information, see [Installer arguments](configure-installer.md). ``` sudo useradd --system --create-home ggc_user sudo groupadd --system ggc_group ``` 1. Verify that the user that runs the Amazon IoT Greengrass Core software (typically `root`), has permission to run `sudo` with any user and any group. 1. Run the following command to open the `/etc/sudoers` file. ``` sudo visudo ``` 1. Verify that the permission for the user looks like the following example. ``` root ALL=(ALL:ALL) ALL ``` 1. (Optional) To [run containerized Lambda functions](run-lambda-functions.md), you must enable [cgroups](https://en.wikipedia.org/wiki/Cgroups) v1, and you must enable and mount the *memory* and *devices* cgroups. If you don't plan to run containerized Lambda functions, you can skip this step. To enable these cgroups options, boot the device with the following Linux kernel parameters. ``` cgroup_enable=memory cgroup_memory=1 systemd.unified_cgroup_hierarchy=0 ``` For information about viewing and setting kernel parameters for your device, see the documentation for your operating system and boot loader. Follow the instructions to permanently set the kernel parameters. 1. Install all other required dependencies on your device as indicated by the list of requirements in [Device requirements](greengrass-nucleus-component.md#greengrass-v2-requirements). ### Set up a Windows device **Note** This feature is available for v2.5.0 and later of the [Greengrass nucleus component](greengrass-nucleus-component.md). **To set up a Windows device for Amazon IoT Greengrass V2** 1. Install the Java runtime, which Amazon IoT Greengrass Core software requires to run. We recommend that you use [Amazon Corretto](https://www.amazonaws.cn/corretto/) or [OpenJDK](https://openjdk.java.net/) long-term support versions. Version 8 or higher is required. 1. Check whether Java is available on the [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) system variable, and add it if not. The LocalSystem account runs the Amazon IoT Greengrass Core software, so you must add Java to the PATH system variable instead of the PATH user variable for your user. Do the following: 1. Press the Windows key to open the start menu. 1. Type **environment variables** to search for the system options from the start menu. 1. In the start menu search results, choose **Edit the system environment variables** to open the **System properties** window. 1. Choose **Environment variables...** to open the **Environment Variables** window. 1. Under **System variables**, select **Path**, and then choose **Edit**. In the **Edit environment variable** window, you can view each path on a separate line. 1. Check if the path to the Java installation's `bin` folder is present. The path might look similar to the following example. ``` C:\\Program Files\\Amazon Corretto\\jdk11.0.13_8\\bin ``` 1. If the Java installation's `bin` folder is missing from **Path**, choose **New** to add it, and then choose **OK**. 1. Open the Windows Command Prompt (`cmd.exe`) as an administrator. 1. Create the default user in the LocalSystem account on the Windows device. Replace *password* with a secure password. ``` net user /add ggc_user password ``` **Tip** Depending on your Windows configuration, the user's password might be set to expire at a date in the future. To ensure your Greengrass applications continue to operate, track when the password expires, and update it before it expires. You can also set the user's password to never expire. To check when a user and its password expire, run the following command. ``` net user ggc_user | findstr /C:expires ``` To set a user's password to never expire, run the following command. ``` wmic UserAccount where "Name='ggc_user'" set PasswordExpires=False ``` If you’re using Windows 10 or later where the [`wmic` command is deprecated](https://learn.microsoft.com/en-us/windows/win32/wmisdk/wmic), run the following PowerShell command. ``` Get-CimInstance -Query "SELECT * from Win32_UserAccount WHERE name = 'ggc_user'" | Set-CimInstance -Property @{PasswordExpires="False"} ``` 1. Download and install the [PsExec utility](https://docs.microsoft.com/en-us/sysinternals/downloads/psexec) from Microsoft on the device. 1. Use the PsExec utility to store the user name and password for the default user in the Credential Manager instance for the LocalSystem account. Replace *password* with the user's password that you set earlier. ``` psexec -s cmd /c cmdkey /generic:ggc_user /user:ggc_user /pass:password ``` If the **PsExec License Agreement** opens, choose **Accept** to agree to the license and run the command. **Note** On Windows devices, the LocalSystem account runs the Greengrass nucleus, and you must use the PsExec utility to store the default user information in the LocalSystem account. Using the Credential Manager application stores this information in the Windows account of the currently logged on user, instead of the LocalSystem account. ## Download the Amazon IoT Greengrass Core software You can download the latest version of the Amazon IoT Greengrass Core software from the following location: + [https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip](https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip) **Note** You can download a specific version of the Amazon IoT Greengrass Core software from the following location. Replace *version* with the version to download. ``` https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-version.zip ``` **To download the Amazon IoT Greengrass Core software** 1. On your core device, download the Amazon IoT Greengrass Core software to a file named `greengrass-nucleus-latest.zip`. ------ #### [ Linux or Unix ] ``` curl -s https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip > greengrass-nucleus-latest.zip ``` ------ #### [ Windows Command Prompt (CMD) ] ``` curl -s https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip > greengrass-nucleus-latest.zip ``` ------ #### [ PowerShell ] ``` iwr -Uri https://d2s8p88vqu9w66.cloudfront.net/releases/greengrass-nucleus-latest.zip -OutFile greengrass-nucleus-latest.zip ``` ------ By downloading this software, you agree to the [Greengrass Core Software License Agreement](https://greengrass-release-license.s3.us-west-2.amazonaws.com/greengrass-license-v1.pdf). 1. (Optional) To verify the Greengrass nucleus software signature **Note** This feature is available with Greengrass nucleus version 2.9.5 and later. 1. Use the following command to verify your Greengrass nucleus artifact's signature: ------ #### [ Linux or Unix ] ``` jarsigner -verify -certs -verbose greengrass-nucleus-latest.zip ``` ------ #### [ Windows Command Prompt (CMD) ] The file name might look different depending on the JDK version you install. Replace *`jdk17.0.6_10`* with the JDK version you installed. ``` "C:\\Program Files\\Amazon Corretto\\jdk17.0.6_10\\bin\\jarsigner.exe" -verify -certs -verbose greengrass-nucleus-latest.zip ``` ------ #### [ PowerShell ] The file name might look different depending on the JDK version you install. Replace *`jdk17.0.6_10`* with the JDK version you installed. ``` 'C:\\Program Files\\Amazon Corretto\\jdk17.0.6_10\\bin\\jarsigner.exe' -verify -certs -verbose greengrass-nucleus-latest.zip ``` ------ 1. The `jarsigner` invocation yields output that indicates the results of the verification. 1. If the Greengrass nucleus zip file is signed, the output contains the following statement: ``` jar verified. ``` 1. If the Greengrass nucleus zip file isn't signed, the output contains the following statement: ``` jar is unsigned. ``` 1. If you provided the Jarsigner `-certs` option along with `-verify` and `-verbose` options, the output also includes detailed signer certificate information. 1. Unzip the Amazon IoT Greengrass Core software to a folder on your device. Replace *GreengrassInstaller* with the folder that you want to use. ------ #### [ Linux or Unix ] ``` unzip greengrass-nucleus-latest.zip -d GreengrassInstaller && rm greengrass-nucleus-latest.zip ``` ------ #### [ Windows Command Prompt (CMD) ] ``` mkdir GreengrassInstaller && tar -xf greengrass-nucleus-latest.zip -C GreengrassInstaller && del greengrass-nucleus-latest.zip ``` ------ #### [ PowerShell ] ``` Expand-Archive -Path greengrass-nucleus-latest.zip -DestinationPath .\\GreengrassInstaller rm greengrass-nucleus-latest.zip ``` ------ 1. (Optional) Run the following command to see the version of the Amazon IoT Greengrass Core software. ``` java -jar ./GreengrassInstaller/lib/Greengrass.jar --version ``` **Important** If you install a version of the Greengrass nucleus earlier than v2.4.0, don't remove this folder after you install the Amazon IoT Greengrass Core software. The Amazon IoT Greengrass Core software uses the files in this folder to run. If you downloaded the latest version of the software, you install v2.4.0 or later, and you can remove this folder after you install the Amazon IoT Greengrass Core software. ## Download the Amazon IoT fleet provisioning plugin You can download the latest version of the Amazon IoT fleet provisioning plugin from the following location: + [https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-latest.jar](https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-latest.jar) **Note** You can download a specific version of the Amazon IoT fleet provisioning plugin from the following location. Replace *version* with the version to download. For more information about each version of the fleet provisioning plugin, see [Amazon IoT fleet provisioning plugin changelog](fleet-provisioning-changelog.md). ``` https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-version.jar ``` The fleet provisioning plugin is open source. To view its source code, see the [Amazon IoT fleet provisioning plugin](https://github.com/aws-greengrass/aws-greengrass-fleet-provisioning-by-claim) on GitHub. **To download the Amazon IoT fleet provisioning plugin** + On your device, download the Amazon IoT fleet provisioning plugin to a file named `aws.greengrass.FleetProvisioningByClaim.jar`. Replace *GreengrassInstaller* with the folder that you want to use. ------ #### [ Linux or Unix ] ``` curl -s https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-latest.jar > GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar ``` ------ #### [ Windows Command Prompt (CMD) ] ``` curl -s https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-latest.jar > GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar ``` ------ #### [ PowerShell ] ``` iwr -Uri https://d2s8p88vqu9w66.cloudfront.net/releases/aws-greengrass-FleetProvisioningByClaim/fleetprovisioningbyclaim-latest.jar -OutFile GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar ``` ------ By downloading this software, you agree to the [Greengrass Core Software License Agreement](https://greengrass-release-license.s3.us-west-2.amazonaws.com/greengrass-license-v1.pdf). ## Install the Amazon IoT Greengrass Core software Run the installer with arguments that specify the following actions: + Install from a partial configuration file that specifies to use the fleet provisioning plugin to provision Amazon resources. The Amazon IoT Greengrass Core software uses a configuration file that specifies the configuration of every Greengrass component on the device. The installer creates a complete configuration file from the partial configuration file that you provide and the Amazon resources that the fleet provisioning plugin creates. + Specify to use the `ggc_user` system user to run software components on the core device. On Linux devices, this command also specifies to use the `ggc_group` system group, and the installer creates the system user and group for you. + Set up the Amazon IoT Greengrass Core software as a system service that runs at boot. On Linux devices, this requires the [Systemd](https://en.wikipedia.org/wiki/Systemd) init system. **Important** On Windows core devices, you must set up the Amazon IoT Greengrass Core software as a system service. For more information about the arguments that you can specify, see [Installer arguments](configure-installer.md). **Note** If you are running Amazon IoT Greengrass on a device with limited memory, you can control the amount of memory that Amazon IoT Greengrass Core software uses. To control memory allocation, you can set JVM heap size options in the `jvmOptions` configuration parameter in your nucleus component. For more information, see [Control memory allocation with JVM options](configure-greengrass-core-v2.md#jvm-tuning). **To install the Amazon IoT Greengrass Core software** 1. Check the version of the Amazon IoT Greengrass Core software. + Replace *GreengrassInstaller* with the path to the folder that contains the software. ``` java -jar ./GreengrassInstaller/lib/Greengrass.jar --version ``` 1. Use a text editor to create a configuration file named `config.yaml` to provide to the installer. For example, on a Linux-based system, you can run the following command to use GNU nano to create the file. ``` nano GreengrassInstaller/config.yaml ``` Copy the following YAML content into the file. This partial configuration file specifies parameters for the fleet provisioning plugin. For more information about the options that you can specify, see [Configure the Amazon IoT fleet provisioning plugin](fleet-provisioning-configuration.md). ------ #### [ Linux or Unix ] ``` --- services: aws.greengrass.Nucleus: version: "2.17.0" aws.greengrass.FleetProvisioningByClaim: configuration: rootPath: "/greengrass/v2" awsRegion: "us-west-2" iotDataEndpoint: "device-data-prefix-ats.iot.us-west-2.amazonaws.com" iotCredentialEndpoint: "device-credentials-prefix.credentials.iot.us-west-2.amazonaws.com" iotRoleAlias: "GreengrassCoreTokenExchangeRoleAlias" provisioningTemplate: "GreengrassFleetProvisioningTemplate" claimCertificatePath: "/greengrass/v2/claim-certs/claim.pem.crt" claimCertificatePrivateKeyPath: "/greengrass/v2/claim-certs/claim.private.pem.key" rootCaPath: "/greengrass/v2/AmazonRootCA1.pem" templateParameters: ThingName: "MyGreengrassCore" ThingGroupName: "MyGreengrassCoreGroup" ``` ------ #### [ Windows ] ``` --- services: aws.greengrass.Nucleus: version: "2.17.0" aws.greengrass.FleetProvisioningByClaim: configuration: rootPath: "C:\\greengrass\\v2" awsRegion: "us-west-2" iotDataEndpoint: "device-data-prefix-ats.iot.us-west-2.amazonaws.com" iotCredentialEndpoint: "device-credentials-prefix.credentials.iot.us-west-2.amazonaws.com" iotRoleAlias: "GreengrassCoreTokenExchangeRoleAlias" provisioningTemplate: "GreengrassFleetProvisioningTemplate" claimCertificatePath: "C:\\greengrass\\v2\\claim-certs\\claim.pem.crt" claimCertificatePrivateKeyPath: "C:\\greengrass\\v2\\claim-certs\\claim.private.pem.key" rootCaPath: "C:\\greengrass\\v2\\AmazonRootCA1.pem" templateParameters: ThingName: "MyGreengrassCore" ThingGroupName: "MyGreengrassCoreGroup" ``` ------ Then, do the following: + Replace *2.17.0* with the version of the Amazon IoT Greengrass Core software. + Replace each instance of `/greengrass/v2` or *C:\$1greengrass\$1v2* with the Greengrass root folder. **Note** On Windows devices, you must specify path separators as double backslashes (`\\`), such as `C:\\greengrass\\v2`. + Replace *us-west-2* with the Amazon Region where you created the provisioning template and other resources. + Replace the `iotDataEndpoint` with your Amazon IoT data endpoint. + Replace the `iotCredentialEndpoint` with your Amazon IoT credentials endpoint. + Replace *GreengrassCoreTokenExchangeRoleAlias* with the name of the token exchange role alias. + Replace *GreengrassFleetProvisioningTemplate* with the name of the fleet provisioning template. + Replace the `claimCertificatePath` with the path to the claim certificate on the device. + Replace the `claimCertificatePrivateKeyPath` with the path to the claim certificate private key on the device. + Replace the template parameters (`templateParameters`) with the values to use to provision the device. This example refers to the [example template](fleet-provisioning-setup.md#example-fleet-provisioning-template) that defines `ThingName` and `ThingGroupName` parameters. **Note** In this configuration file, you can customize other configuration options such as the ports and network proxy to use, as shown in the following example. For more information, see [Greengrass nucleus configuration](greengrass-nucleus-component.md#greengrass-nucleus-component-configuration). ``` --- services: aws.greengrass.Nucleus: version: "2.17.0" configuration: mqtt: port: 443 greengrassDataPlanePort: 443 networkProxy: noProxyAddresses: "http://192.168.0.1,www.example.com" proxy: url: "http://my-proxy-server:1100" username: "Mary_Major" password: "pass@word1357" aws.greengrass.FleetProvisioningByClaim: configuration: rootPath: "/greengrass/v2" awsRegion: "us-west-2" iotDataEndpoint: "device-data-prefix-ats.iot.us-west-2.amazonaws.com" iotCredentialEndpoint: "device-credentials-prefix.credentials.iot.us-west-2.amazonaws.com" iotRoleAlias: "GreengrassCoreTokenExchangeRoleAlias" provisioningTemplate: "GreengrassFleetProvisioningTemplate" claimCertificatePath: "/greengrass/v2/claim-certs/claim.pem.crt" claimCertificatePrivateKeyPath: "/greengrass/v2/claim-certs/claim.private.pem.key" rootCaPath: "/greengrass/v2/AmazonRootCA1.pem" templateParameters: ThingName: "MyGreengrassCore" ThingGroupName: "MyGreengrassCoreGroup" mqttPort: 443 proxyUrl: "http://my-proxy-server:1100" proxyUserName: "Mary_Major" proxyPassword: "pass@word1357" ``` ``` --- services: aws.greengrass.Nucleus: version: "2.17.0" configuration: mqtt: port: 443 greengrassDataPlanePort: 443 networkProxy: noProxyAddresses: "http://192.168.0.1,www.example.com" proxy: url: "http://my-proxy-server:1100" username: "Mary_Major" password: "pass@word1357" aws.greengrass.FleetProvisioningByClaim: configuration: rootPath: "C:\\greengrass\\v2" awsRegion: "us-west-2" iotDataEndpoint: "device-data-prefix-ats.iot.us-west-2.amazonaws.com" iotCredentialEndpoint: "device-credentials-prefix.credentials.iot.us-west-2.amazonaws.com" iotRoleAlias: "GreengrassCoreTokenExchangeRoleAlias" provisioningTemplate: "GreengrassFleetProvisioningTemplate" claimCertificatePath: "C:\\greengrass\\v2\\claim-certs\\claim.pem.crt" claimCertificatePrivateKeyPath: "C:\\greengrass\\v2\\claim-certs\\claim.private.pem.key" rootCaPath: "C:\\greengrass\\v2\\AmazonRootCA1.pem" templateParameters: ThingName: "MyGreengrassCore" ThingGroupName: "MyGreengrassCoreGroup" mqttPort: 443 proxyUrl: "http://my-proxy-server:1100" proxyUserName: "Mary_Major" proxyPassword: "pass@word1357" ``` To use an HTTPS proxy, you must use version 1.1.0 or later of the fleet provisioning plugin. You must additionally specify the `rootCaPath` under `system`, as shown in the following example. ``` --- system: rootCaPath: "/greengrass/v2/AmazonRootCA1.pem" services: ... ``` ``` --- system: rootCaPath: "C:\\greengrass\\v2\\AmazonRootCA1.pem" services: ... ``` 1. Run the installer. Specify `--trusted-plugin` to provide the fleet provisioning plugin, and specify `--init-config` to provide the configuration file. + Replace `/greengrass/v2` with the Greengrass root folder. + Replace each instance of *GreengrassInstaller* with the folder where you unpacked the installer. ------ #### [ Linux or Unix ] ``` sudo -E java -Droot="/greengrass/v2" -Dlog.store=FILE \ -jar ./GreengrassInstaller/lib/Greengrass.jar \ --trusted-plugin ./GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar \ --init-config ./GreengrassInstaller/config.yaml \ --component-default-user ggc_user:ggc_group \ --setup-system-service true ``` ------ #### [ Windows Command Prompt (CMD) ] ``` java -Droot="C:\greengrass\v2" "-Dlog.store=FILE" ^ -jar ./GreengrassInstaller/lib/Greengrass.jar ^ --trusted-plugin ./GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar ^ --init-config ./GreengrassInstaller/config.yaml ^ --component-default-user ggc_user ^ --setup-system-service true ``` ------ #### [ PowerShell ] ``` java -Droot="C:\greengrass\v2" "-Dlog.store=FILE" ` -jar ./GreengrassInstaller/lib/Greengrass.jar ` --trusted-plugin ./GreengrassInstaller/aws.greengrass.FleetProvisioningByClaim.jar ` --init-config ./GreengrassInstaller/config.yaml ` --component-default-user ggc_user ` --setup-system-service true ``` ------ **Important** On Windows core devices, you must specify `--setup-system-service true` to set up the Amazon IoT Greengrass Core software as a system service. If you specify `--setup-system-service true`, the installer prints `Successfully set up Nucleus as a system service` if it set up and ran the software as a system service. Otherwise, the installer doesn't output any message if it installs the software successfully. **Note** You can't use the `deploy-dev-tools` argument to deploy local development tools when you run the installer without the `--provision true` argument. For information about deploying the Greengrass CLI directly on your device, see [Greengrass Command Line Interface](gg-cli.md). 1. Verify the installation by viewing the files in the root folder. ------ #### [ Linux or Unix ] ``` ls /greengrass/v2 ``` ------ #### [ Windows Command Prompt (CMD) ] ``` dir C:\greengrass\v2 ``` ------ #### [ PowerShell ] ``` ls C:\greengrass\v2 ``` ------ If the installation succeeded, the root folder contains several folders, such as `config`, `packages`, and `logs`. If you installed the Amazon IoT Greengrass Core software as a system service, the installer runs the software for you. Otherwise, you must run the software manually. For more information, see [Run the Amazon IoT Greengrass Core software](run-greengrass-core-v2.md). For more information about how to configure and use the software and Amazon IoT Greengrass, see the following: + [Configure the Amazon IoT Greengrass Core software](configure-greengrass-core-v2.md) + [Develop Amazon IoT Greengrass components](develop-greengrass-components.md) + [Deploy Amazon IoT Greengrass components to devices](manage-deployments.md) + [Greengrass Command Line Interface](gg-cli.md)