1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
SSM Agent is not able to access Greengrass variables since it is not executed as a child process of Greengrass, but as an independent process executed by systemd
, even when you deploy it via aws.greengrass.SystemManagerAgent
component.
What you can do is to write a component that export that variable so that it is available to the script run by the SSM Agent. One example would be to write that ThingName in a file inside /var/
or /etc/
folders, and then read it from your script before executing it. Alternatively the custom component could add an export
to the .bashrc
file of the SSM Agent user and execute your script in bash.
Cheers,
Massimiliano
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 4 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
Hi Massimiliano, Is there a way to get the Managed node "SourceId" using the SSM run command to run a shell script?
Could you please explain what you are trying to do?