beam-remote

Connect to a running Elixir/BEAM node via AWS ECS exec for read-only inspection.

2|1|Updated Feb 8, 2021
One-click install
npx skills add https://github.com/jstoobz/dotfiles --skill beam-remote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beam-remote
Source: https://github.com/jstoobz/dotfiles/tree/main/claude/skills/infrastructure/beam-remote
Command: npx skills add https://github.com/jstoobz/dotfiles --skill beam-remote

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables engineers to connect to a live Elixir/BEAM node via AWS ECS exec for read-only inspection and debugging.

Core Features & Use Cases

  • Live inspection of memory, processes, and BEAM state on a running node.
  • Remote console access to interact with the Elixir runtime without downtime.
  • Safety-first workflow with read-only by default and explicit confirmation for mutations, leveraging the included safety-guardrails references.

Quick Start

Use beam-remote to connect to your BEAM node by authenticating to AWS and starting an ECS execute-command session.

Frequently Asked Questions about beam-remote

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

FAQPage Schema
How do I connect to a running Elixir BEAM node on AWS ECS for live inspection?

You can connect to a running Elixir BEAM node on AWS ECS by establishing an ECS execute-command session. This allows live inspection of memory, processes, and BEAM state for on-call debugging without downtime.

What AWS credentials do I need to access a remote Elixir console in production?

Accessing a remote Elixir console in production requires standard AWS credentials and specific ECS permissions. The session enforces read-only inspection by default to ensure safe on-call debugging across environments.

Can I execute mutating commands on a BEAM node during a remote debugging session?

Executing mutating commands on a BEAM node during remote debugging is blocked by default. The safety-guardrails require explicit confirmation before any mutation is allowed, ensuring safe live inspection.

When do I need to use ECS execute-command for Elixir runtime debugging?

You need ECS execute-command for Elixir runtime debugging when troubleshooting memory issues or inspecting BEAM processes across qa, uat, or prod environments. It provides direct remote console access to the live node.

What is the safest way to inspect BEAM state on a live production node?

The safest way to inspect BEAM state on a live production node is using a read-only remote console session. This approach applies safety-guardrails that prevent accidental mutations during memory and process inspection.