Usando AWS re:Post, accetti AWS re:Post Termini di utilizzo
AWS re:Postre:Post

Any standard way to move greengrass device to a different account/endpoint

0

I have greengrass setup reporting to one particular endpoint, but I need to move it to a different one. I have the endpoint detail necessary.

  • I have the device registered in the other account with IoT in the same way

  • I same device deployment configuration available in the other account.

  • I have the device assigned the same deployment in the new account

    Basically I'd like to move it to the other account, and then be able to continue deploying as before. is there any standard way to do this type of thing ?

  • MassimilianoAWS ESPERTO
    8 mesi fa

    Is this about a device in production or test/dev? Is there any local component state which is stored inside the Greengrass component work folder you need to keep?

  • majh
    8 mesi fa

    @MassimilanoAWS - Yes this is similar to the test/dev scenario - or potentially event moving between multiple production account endpoints. There isn't any local component state required. How would you recommend dealing with this ?

Argomenti
Internet delle cose (IoT)
Tag
AWS IoT GreengrassAWS IoT Core
Lingua
English
majh
posta 8 mesi fa304 visualizzazioni
2 Risposte
0
Risposta accettata

If you are in a dev/test scenario, you can just rerun the installer on the same machine, using credentials belonging to the new target account. If the endpoint is in the same account (that is only a different region) you just need to ensure you set the right region in the installer parameters.

AWS
ESPERTO
MassimilianoAWS
con risposta 8 mesi fa
  • majh
    8 mesi fa

    OK - what about in a production environment ?

0

One relatively straightforward way to do this is to un-install Greengrass, then re-install it via our quick installer with the new account parameters. See https://docs.aws.amazon.com/greengrass/v2/developerguide/quick-installation.html for more details.

Aside from the quick installer, there is presently no out-of-the-box migration utility.

AWS
dghz
con risposta 8 mesi fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande

Contenuto pertinente