greengrass-init

This role sets up a basic configuration in an existing AWS account to enable the deployment of AWS Greengrass groups, cores, and devices.

Requirements

You need to have the AWS CLI set up beforehand, with credentials that have enough permissions to create AWS Greengrass objects.

This role uses the json_query filter, which means you need to have jmespath installed on your local machine.

Variables

Here are some configuration variables that will affect how this role works:

• greengrass_group_names: A list of names for the Greengrass groups you want to create.
• greengrass_device_stub: The basic name for the devices that will be created.
• greengrass_device_count: The number of devices to create, which will have numbers added to the device_stub name.
• root_ca_checksum: The checksum of the root Certificate Authority for Greengrass, which usually remains the same.
• greengrass_s3_bucket: An AWS S3 bucket where the generated Greengrass configuration files will be stored.
• lambda_role: A role document that allows Lambda to execute, which is a common feature in Greengrass.
• greengrass_service_role: A role that allows access to Greengrass and IoT services.
• greengrass_core_policy: A policy applied to the Greengrass core (it is typically assumed to involve IoT and Greengrass).
• greengrass_device_policy: A policy applied to devices (also typically assumed to involve IoT and Greengrass).

Example Playbook

- hosts: greengrass
  roles:
     - { role: vmware.greengrass-init, greengrass_group_names: [g1, g2] }

License

Apache License 2.0 or GPLv3