Greengrass v2 # ThingGroup # Flexibility for Tenant use case

Question

Need help with following use case. I am working on use case where I need tenant bifurcation on device. For e.g  I have Tenant1 and Tenant 2. In Tenant 1 I have sell 3 devices and in Tenant 2 sold 5 devices.

To manager tenant I need to create logical group which I can achive through Thing Group.

**Tenant_Thing_Group1**
		- Thing_1
		- Thing_2
		- Thing_3
		
	**Tenant_Thing_Group2**
		- Thing_4
		- Thing_5
		- Thing_6
		- Thing_7
		- Thing_8
		
Now I am going to use **AWS greengrass v2** for components deployment and all. I have taken greengrass setup in my yocto OS setup recipe. But as per my experience whenever we trigger greengraa v2 command to create deployment. It would create 
individual deployment for each device. Instead of that I want to use the single deployment per tenant so I can deploy changes in single go to all the devices.

Could please guide me of provide some steps to address this requirement ??

Answer

Hi,

Greengrass supports [deploying to both Things and Thing Groups  as targets](https://docs.aws.amazon.com/greengrass/v2/developerguide/create-deployments.html).

Given your setup, to deploy specific components to all the Tenant 1 devices you can create a deployment targeting `Tenant_Thing_Group1`. The same applies to devices for Tenant 2 using `Tenant_Thing_Group2` as a target.

If you need to deploy components which are common to all devices, you can create another Thing Groups, let's call it  for example `AllDevices`, and create a deployment with the common components targeting that thing group.

Keep in mind that component configurations specified in a deployment applies to all targeted devices. If you need to deploy the same component but have device specific configurations you can use device shadows to hold the device specific configurations.

Cheers,

Massimiliano

Greengrass v2 # ThingGroup # Flexibility for Tenant use case

Contenuto pertinente