run-cloudstub

Execute the CloudStub Java server to mock AWS services for integration testing.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/cloudstub/cloudstub --skill run-cloudstub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-cloudstub
Source: https://github.com/cloudstub/cloudstub/tree/main/.claude/skills/run-cloudstub
Command: npx skills add https://github.com/cloudstub/cloudstub --skill run-cloudstub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires java, curl, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the need for external Docker containers or complex infrastructure when testing AWS service integrations, allowing for rapid, in-process JVM testing.

Core Features & Use Cases

  • Standalone Server Management: Start, stop, and verify the CloudStub server process with configurable ports and service modules.
  • Protocol Validation: Exercise AWS protocols including SQS, SNS, Secrets Manager, DynamoDB, and Lambda to ensure integration compatibility.
  • Use Case: Use this Skill to perform a full smoke test of your AWS-integrated application logic by spinning up a local mock server, executing API requests, and verifying state persistence across different AWS surfaces.

Quick Start

Use the run-cloudstub skill to start the server and run the full suite of smoke tests.

Frequently Asked Questions about run-cloudstub

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

FAQPage Schema
How do I test AWS integrations locally without using Docker containers?

You can test AWS integrations locally without Docker by launching the standalone CloudStub Java server, which provides in-process JVM mocking for rapid validation of AWS SDK v2 client interactions.

What AWS protocols can I validate using a local mock server?

Using a local mock server, you can validate AWS protocols including SQS, SNS, Secrets Manager, DynamoDB, and Lambda to verify integration compatibility and stateful service behavior.

Do I need a specific Java version to run AWS mock services for integration testing?

Yes, you need a Java 17+ runtime environment to run AWS mock services for integration testing, along with the ability to execute shell scripts for process lifecycle management.

How do I perform a smoke test of my AWS-integrated application logic?

To perform a smoke test of your AWS-integrated application logic, start the local mock server, execute API requests, and verify state persistence across different AWS service surfaces.

Can I configure ports and service modules when launching a local AWS mock server?

Yes, you can configure ports and service modules when launching the local AWS mock server, allowing you to start, stop, and verify the server process according to your testing requirements.

Why use in-process JVM mocking instead of external containers for AWS testing?

In-process JVM mocking eliminates the need for complex external infrastructure, enabling rapid setup and faster execution when validating AWS service integrations during testing.