integration-aws

Name: integration-aws
Availability: InStock
Author: Paarth

Connect AWS services to a self-hosted Hermes agent via SSH and MCP registration.

13|1|Updated Jun 1, 2026

Search Tags:#automation #aws #integration #mcp #ssh #hermes #sigv4

Ready to run

npx skills add https://github.com/paarths-collab/hstack --skill integration-aws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-aws
Source: https://github.com/paarths-collab/hstack/tree/main/skills/integration-aws
Command: npx skills add https://github.com/paarths-collab/hstack --skill integration-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of connecting AWS services to a self-hosted Hermes agent, so the agent can reach AWS tools securely and reliably from a VPS.

Core Features & Use Cases

AWS MCP Wiring: Connects AWS APIs such as EC2, S3, Lambda, and many more through the managed AWS MCP server.
SSH-First Deployment: Runs the setup on the remote Hermes host, keeping credentials and agent configuration on the VPS.
SigV4 Auth Handling: Uses an mcp-proxy-for-aws stdio proxy so AWS requests are signed correctly instead of failing with bearer-token auth.
Safe, Idempotent Setup: Includes checks, dry-run guidance, rollback steps, and validation to avoid duplicate or broken integrations.

Quick Start

Ask the agent to connect AWS to your self-hosted Hermes installation using the IAM credentials, region, and VPS details you provide.

Frequently Asked Questions about integration-aws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I connect AWS services to a self-hosted Hermes agent over SSH?▼

Wire AWS into Hermes by running an SSH-based configuration on your VPS that registers the AWS MCP endpoint with IAM credentials, enabling the agent to securely reach EC2, S3, and Lambda APIs remotely.

Why do my AWS API requests fail with bearer-token auth when using an MCP proxy?▼

AWS API requests fail because they require SigV4 signing rather than bearer tokens. Using an mcp-proxy-for-aws stdio proxy signs requests correctly, ensuring AWS APIs accept the Hermes agent calls.

How do I set up an AWS MCP integration on a VPS without breaking existing agent configurations?▼

Set up AWS MCP integrations safely by using an idempotent configuration process that includes checks, dry-run guidance, and rollback steps, preventing duplicate or broken integrations on your Hermes host.

What do I need to configure AWS MCP endpoints for a remote Hermes deployment?▼

Configuring AWS MCP endpoints for remote Hermes deployment requires IAM credentials, a region-specific AWS MCP endpoint, VPS SSH access, and an mcp-proxy-for-aws stdio proxy to handle SigV4 request signing.

Can I use this SSH deployment approach to connect AWS Lambda and S3 to my VPS agent?▼

Yes, you can connect AWS Lambda and S3 to your VPS agent. The integration uses the managed AWS MCP server to wire multiple AWS APIs into your self-hosted Hermes installation over SSH.