Unable to deploy greengrass-cli to new device

0

I set up a raspberry Pi as a greengrass core device following the manually provisioning process. After the core device is registered, I try to deploy greengrass-cli to the device from IoT console, but it always fail with following errors. I don't understand why it is failing to negotiate version because there is no older version.

2021-06-02T21:39:17.230Z [INFO] (pool-2-thread-15) com.aws.greengrass.componentmanager.ComponentManager: negotiate-version-with-cloud-start. Negotiating version with cloud. {}
2021-06-02T21:39:18.901Z [ERROR] (pool-2-thread-15) com.aws.greengrass.componentmanager.ComponentManager: Failed to negotiate version with cloud and no local version to fall back to. {componentName=aws.greengrass.Cli, versionRequirement={thing/gateway_pi64==2.1.0}}
software.amazon.awssdk.services.greengrassv2.model.GreengrassV2Exception: null (Service: GreengrassV2, Status Code: 403, Request ID: f08d99d4-2b93-07ad-57ae-1eada935b967, Extended Request ID: null)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:123)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:79)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:59)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:40)
at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:40)
at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:30)
...
2021-06-02T21:39:32.187Z [INFO] (pool-2-thread-13) com.aws.greengrass.deployment.DeploymentService: Current deployment finished. {DeploymentId=arn:aws:greengrass:us-west-2:308868511064:configuration:thing/gateway_pi64:5, serviceName=DeploymentService, currentState=RUNNING}

Edited by: jcai on Jun 2, 2021 3:38 PM

jcai
asked 3 years ago253 views
2 Answers
0

Hi there,
Since you are seeing a 403 error, this means that your IoT policy is not properly configured to allow Greengrass to deploy components. Please see https://docs.aws.amazon.com/greengrass/v2/developerguide/device-auth.html#greengrass-core-minimal-iot-policy for how to properly configure the policy.

Cheers,
Michael Dombrowski

AWS
EXPERT
answered 3 years ago
0

You are absolute right. I did not specify greengrass permissions in my policy. Thank you very much!

jcai
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions