floci

Configure Floci to emulate AWS services locally and validate S3, SQS, and DynamoDB smoke tests.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill floci
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: floci
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/codex/.codex/skills/floci
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill floci

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of reliably emulating AWS services locally so development, tests, and CI can run without depending on real AWS endpoints.

Core Features & Use Cases

  • Floci local AWS emulation setup: configure endpoints, region, and dummy credentials to prevent accidental use of real AWS.
  • Project integration & troubleshooting: align docker-compose (or SDK/CLI configs) with http://localhost:4566 and isolate local/CI behavior.
  • Validation via smoke tests: verify key services like S3, SQS, and DynamoDB with reproducible checks, plus optional service coverage (e.g., Lambda/ECR/EventBridge) when needed.

Quick Start

Ask the AI to โ€œSet up Floci in this repo for local development and CI by updating docker-compose and adding endpoint overrides so S3, SQS, and DynamoDB smoke tests pass against http://localhost:4566.โ€

Frequently Asked Questions about floci

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

FAQPage Schema
How do I emulate AWS services locally for development and CI testing?โ–ผ

You can emulate AWS services locally by configuring Floci with endpoint overrides pointing to http://localhost:4566, setting deterministic environment variables, and using safe dummy credentials for S3, SQS, and DynamoDB validation.

What is the best way to migrate from LocalStack to another local AWS emulation tool?โ–ผ

Migrating from LocalStack involves configuring Floci for local AWS emulation, updating your docker-compose setup, aligning SDK or CLI endpoint overrides to http://localhost:4566, and validating S3, SQS, and DynamoDB behavior with smoke tests.

How do I configure endpoint overrides for S3, SQS, and DynamoDB in docker-compose?โ–ผ

Configuring endpoint overrides in docker-compose requires pointing your AWS SDK or CLI settings to http://localhost:4566, applying deterministic environment variables, and isolating local or CI behavior to ensure S3, SQS, and DynamoDB smoke tests pass.

Can I run AWS smoke tests locally without hitting real AWS endpoints?โ–ผ

Yes, you can run AWS smoke tests locally without real endpoints by using Floci to emulate S3, SQS, and DynamoDB, applying safe dummy credentials to prevent accidental real AWS usage, and executing reproducible validation checks via Docker.

Does Floci support AWS emulation for services beyond S3, SQS, and DynamoDB?โ–ผ

Floci primarily validates S3, SQS, and DynamoDB with reproducible smoke tests, but it also supports optional service coverage for other AWS-compatible behaviors like Lambda, ECR, and EventBridge when needed for your local development or CI environment.

Why are my local AWS integration tests failing due to network or runtime constraints?โ–ผ

Local AWS integration tests often fail due to network or runtime constraints if docker-compose execution choices and endpoint overrides are misaligned; configuring deterministic environment variables and isolating local behavior ensures S3, SQS, and DynamoDB smoke tests pass.