Excessive availability patterns for AWS IoT Greengrass utilizing Pacemaker

Edge computing downtime in industrial IoT environments might be each inconvenient and dear. Methods on the edge require steady operation to take care of enterprise continuity. Whereas AWS IoT Greengrass delivers highly effective edge computing capabilities, reaching true enterprise-grade excessive availability requires further orchestration. This submit exhibits the best way to use Pacemaker, a cluster useful resource supervisor, to construct resilient edge infrastructure with automated failover.

On this walkthrough, you’ll be taught to implement energetic/passive and energetic/energetic excessive availability patterns utilizing Pacemaker with AWS IoT Greengrass, full with automated failover, state replication, and monitoring integration.

The excessive availability problem for edge computing

Conventional cloud functions profit from built-in redundancy and auto-scaling, nonetheless, functions on the sting face distinctive challenges:

• Bodily isolation: Edge units function in distant places with restricted connectivity
• Useful resource constraints: Not like cloud environments, edge sources are finite and valuable
• Service criticality: Edge failures can halt bodily operations instantly
• Restoration complexity: Guide intervention at distant websites is dear and sluggish

AWS IoT Greengrass addresses many edge computing challenges, however excessive availability requires considerate structure past a single gadget deployment.

How Pacemaker enhances AWS IoT Greengrass

Pacemaker helps you construct extremely obtainable AWS IoT Greengrass deployments by cluster administration capabilities:

Confirmed reliability

• Utilized in mission-critical environments for over a decade
• Handles complicated failure eventualities with subtle fencing mechanisms
• Works in each energetic/passive and energetic/energetic configurations

AWS IoT Greengrass-aware useful resource administration

• Screens Greengrass service well being and element states
• Manages shared storage for seamless state switch
• Coordinates failover of dependent providers and community sources

Enterprise-ready integration

• Integrates with current Linux infrastructure administration
• Helps complicated dependency chains and useful resource constraints
• Supplies detailed logging and monitoring for compliance necessities

Collectively, these instruments hold your edge workloads working throughout {hardware} failures or community disruptions.

Structure overview: Excessive availability patterns

AWS IoT Greengrass excessive availability might be applied utilizing two main patterns, every optimized for various use circumstances.

Lively/Passive configuration: Maximizing information consistency

This mode maximizes information consistency and automatic failover—ultimate for mission-critical functions the place information integrity and repair continuity are paramount. One node runs Greengrass actively whereas the opposite stands prepared in standby mode. A software-based, block-level information replication service like Distributed Replicated Block System (DRBD) ensures immediate state synchronization between nodes, enabling failover with zero information loss and sustaining gadget identification.

Key advantages:

This configuration ensures full state preservation throughout failover with sub-minute downtime, zero information loss for in-flight transactions and significant operations, whereas sustaining gadget identification, certificates, and Stream Supervisor persistence seamlessly.

Actual-world use circumstances:

Lively/Passive configurations are important in eventualities requiring zero or minimal information loss, corresponding to in-flight leisure programs that deal with offline fee processing and battery manufacturing amenities the place manufacturing strains rely on steady information circulate from essential manufacturing sensors and ML mannequin outputs to take care of operational integrity and high quality management.

Lively/Lively: Most throughput and scalability

This mode maximizes throughput and supplies horizontal scaling for high-volume workloads. A number of impartial Greengrass situations run concurrently throughout cluster nodes, with clever load balancing distributing work primarily based on node well being and capability. Every node operates with its personal distinctive gadget credentials and configurations.

Key advantages:

These configurations allow horizontal scaling for high-throughput eventualities, enhance useful resource utilization throughout nodes, and supply swish degradation beneath partial failures.

Actual-world use circumstances:

Lively/Lively configurations are perfect for high-volume eventualities corresponding to automotive elements manufacturing amenities and large-scale manufacturing operations with a number of manufacturing strains, the place every node handles totally different line segments to offer each redundancy and elevated processing capability for real-time analytics and anomaly detection.

Configuration choice information

Use Lively/Passive for functions that require zero information loss, shared state, and gadget identification preservation. This sample works nicely once you want a single level of management and might settle for failover occasions beneath one minute.Use Lively/Lively once you want excessive throughput and horizontal scaling. This sample fits functions that may function independently with out shared state, the place load distribution supplies operational advantages, and swish degradation is preferable to finish failover.

The way to implement the answer

The whole playbook, together with detailed configuration examples and testing procedures, is obtainable within the GitHub respository. This supplies an Lively/Passive implementation automation utilizing Ansible which you could customise to your particular necessities. Lively/Lively setup steps are additionally obtainable in MANUAL-SETUP-GUIDE throughout the identical repository.

Setup steps

1. Setting setup

Clone the repository and arrange the event setting

git clone https://github.com/aws-samples/sample-greengrass-ha-pacemaker.git
cd sample-greengrass-ha-pacemaker
./scripts/setup-dev-env.sh && supply .venv/bin/activate

2. Configure cluster secrets and techniques

Generate and encrypt cluster credentials utilizing Ansible Vault

# Create vault password file
echo "your_secure_password" > .vault_pass
chmod 600 .vault_pass
# Auto-generate encrypted secrets and techniques
./scripts/setup-vault.sh

This creates `vars/cluster-vault.yml` with encrypted credentials for cluster authentication and DRBD replication.

3. Put together Greengrass credentials

Observe: This method is designed for testing and demonstration functions solely.

Obtain Greengrass set up recordsdata from AWS IoT Console.

1. Navigate to AWS IoT Core console → Greengrass → Core units
2. Click on ‘Arrange one core gadget’ → ‘Arrange a tool with installer obtain’
3. Identify your gadget (e.g., ‘greengrass-ha-device’)
4. Choose or create a Factor Group
5. Obtain each recordsdata and rename them:
   1. Rename hash-setup.sh to greengrass-setup.sh
   2. Rename hash.zip to greengrass-certs.zip
6. Place recordsdata in `recordsdata/greengrass/` listing

4. Deploy and configure

It will deploy AWS EC2 and vital sources to check on AWS.

# Deploy infrastructure
make cdk-deploy && make cdk-inventory
# Retrieve SSH personal key
./scripts/get-ssh-key.sh
# Configure HA cluster
ansible-playbook playbooks/setup/system-prerequisites.yml -i stock/cdk-dev-hosts
ansible-playbook playbooks/setup/configure-ha.yml -i stock/cdk-dev-hosts --vault-password-file .vault_pass

5. Validate and take a look at

Test cluster standing and optionally, run an automatic failover take a look at.

# Test cluster standing
ansible node-1 -i stock/cdk-dev-hosts -m shell -a "sudo pcs standing" --become
# Take a look at failover (non-obligatory)
ansible-playbook playbooks/testing/test-failover-simulation.yml -i stock/cdk-dev-hosts --vault-password-file .vault_pass

The automated assessments validate useful resource migration, DRBD promotion, and information consistency throughout failover.

Cleanup

It will destroy the sources created by CDK.

# Destroy infrastructure
make cdk-destroy

Conclusion: Enterprise-ready edge computing

AWS IoT Greengrass and Pacemaker collectively present the excessive availability wanted for mission-critical edge deployments. Through the use of Pacemaker’s cluster administration capabilities, organizations can confidently deploy Greengrass the place reliability is important.Whether or not you’re managing industrial management programs, processing real-time analytics, or orchestrating edge AI workloads, this architectural sample supplies the muse for resilient, scalable edge computing that your online business can rely on.

Subsequent steps

Able to implement enterprise-grade excessive availability to your AWS IoT Greengrass deployments? Right here’s your path ahead:

Repository: sample-greengrass-ha-pacemaker

In regards to the authors

Yong Ji Yong Ji is a Senior Options Architect at Amazon Net Companies (AWS), serving to enterprises construct modern cloud-based options. With over 25 years of expertise in cloud structure, analytics and information engineering, Yong brings deep technical experience and a ardour for fixing complicated enterprise challenges. Outdoors of labor, Yong is a passionate desk tennis participant.

Siddhant Srivastava Siddhant Srivastava is a Software program Improvement Engineer with AWS IoT Greengrass. He has 3+ years of expertise in edge computing with concentrate on constructing resilient, scalable distributed programs. Outdoors work, Siddhant participates in soccer leagues and billiards tournaments.