Greengrass V2 positioning for new device

Question

Hi there,

I am just confuse about the provisioning process on greengrass v2. I just wonder at which point the provisioning process is triggered - as in a Core devices is created in AWS IoT Core. 
so I follow the guide https://docs.aws.amazon.com/greengrass/v2/developerguide/fleet-provisioning.html for fleet provisioning, I got the gg software running on my rpi.

seem like the gg software is installed correctly.
```
pi@raspberrypi:~ $ ls /greengrass/v2
alts               bin          cli_ipc_info  deployments  logs      plugins    work
AmazonRootCA1.pem  claim-certs  config        ipc.socket   packages  telemetry
```

```
pi@raspberrypi:~ $ sudo systemctl status greengrass.service
● greengrass.service - Greengrass Core
   Loaded: loaded (/etc/systemd/system/greengrass.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2022-03-09 16:39:32 AEDT; 1min 10s ago
 Main PID: 3551 (sh)
```

Thanks for your time.

Answer

Hi, thanks for using Greengrass. If you got the device to install and run correctly without issues the device is provisioned. Did you try making any deployments to the device and see if they work as well? The core device entry in your AWS account will appear when your device first sends a status report to cloud. Status reports are by sent every 24 hours (unless you change this frequency) and after each deployment issued from the cloud (your AWS account's console/AWS CLI/AWS SDK) has been received and finished on the device.

Answer

so if I understand the deployment process for gg v2 correctly, I need to have the thingArn. However, as far as i know there is no new thing is created. I wonder what did i do wrong.

here is the config for gg installer

---
services:
  aws.greengrass.Nucleus:
    version: "2.5.3"
  aws.greengrass.FleetProvisioningByClaim:
    configuration:
      rootPath: "/greengrass/v2"
      awsRegion: " <> "
      iotDataEndpoint: "<>.amazonaws.com"
      iotCredentialEndpoint: "<>.amazonaws.com"
      iotRoleAlias: "GreengrassCoreTokenExchangeRoleAlias"
      provisioningTemplate: "test-fleet-template"
      claimCertificatePath: "/greengrass/v2/claim-certs/claim.pem.crt"
      claimCertificatePrivateKeyPath: "/greengrass/v2/claim-certs/claim.private.pem.key"
      rootCaPath: "/greengrass/v2/AmazonRootCA1.pem"
      templateParameters:
        model: "rpi4"
        parking: "false"

I also tried to use the wrong provisioningTempalate, but the installer could still run successfully

I am not sure why i rpi cant connect connect to the backend, the ip match with my device

{
  "clientId": "c0b4def9-406d-155a6d88",
  "timestamp": 1646876289069,
  "eventType": "disconnected",
  "clientInitiatedDisconnect": false,
  "sessionIdentifier": "a59a42d2-39ab3b732186",
  "principalIdentifier": "de56ae093b3d75481acf40b3d30e38053ad2e8219fa925e8b",
  "disconnectReason": "CLIENT_ERROR",
  "versionNumber": 0
}

{
  "clientId": "c0b4def9-406d-155a6d88",
  "timestamp": 1646876288970,
  "eventType": "connected",
  "sessionIdentifier": "a59a42d2-39ab3b732186",
  "principalIdentifier": "de56ae093b3d75481acf40b3d30e38053ad2e8219fa925e8b",
  "ipAddress": " ",
  "versionNumber": 0
}

AWS-User-6797102

answered 2 years ago

Greengrass V2 positioning for new device

Relevant content