README.md

June 17, 2026 · View on GitHub

Floci Floci

Light, fluffy, and always free
No account. No auth token. No feature gates. Just docker compose up.

Latest Release Build Status Docker Pulls Docker Image Size License: MIT GitHub Stars

Quick Start · Features · Services · SDKs · Testcontainers · Migration · Docs


What is Floci?

Floci is a free, open-source local AWS emulator for development, testing, and CI.

It gives you AWS-shaped services on your machine without requiring a cloud account, an auth token, or paid feature gates. Point your AWS SDK, CLI, Terraform, CDK, OpenTofu, or test suite at http://localhost:4566 and keep your existing workflows.

Floci is named after floccus, the cloud formation that looks like popcorn.

Quick Start

The fastest way to run Floci is with the official CLI

floci start

Export the AWS environment variables:

eval $(floci env)

Use your existing AWS tools normally:

aws s3 mb s3://my-bucket

aws dynamodb create-table \
  --table-name demo-table \
  --attribute-definitions AttributeName=pk,AttributeType=S \
  --key-schema AttributeName=pk,KeyType=HASH \
  --billing-mode PAY_PER_REQUEST

aws dynamodb list-tables

Watch it run

This short demo shows the CLI flow: start Floci, export the local AWS environment, run standard AWS CLI commands, and stop the emulator.

https://github.com/user-attachments/assets/b55714dc-ef36-40ae-a734-cd2cadc288a8

All AWS services are available at http://localhost:4566. Any region works. Credentials can be any non-empty values.

Prefer Docker Compose?

Create a compose.yaml file:

services:
  floci:
    image: floci/floci:latest
    ports:
      - "4566:4566"

Start Floci:

docker compose up

Then configure your AWS environment manually:

export AWS_ENDPOINT_URL=http://localhost:4566
export AWS_DEFAULT_REGION=us-east-1
export AWS_ACCESS_KEY_ID=test
export AWS_SECRET_ACCESS_KEY=test
Using the old hectorvent/floci image?

Update your image name:

# Before
image: hectorvent/floci:latest

# After
image: floci/floci:latest

The old hectorvent/floci repository no longer receives updates.

Features

Local AWS without the cloud account

Run AWS-compatible services locally without an AWS account, auth token, or paid feature gates.

Real Docker where fidelity matters

Lambda, RDS, Neptune, ElastiCache, MSK, ECS, EC2, EKS, OpenSearch, and CodeBuild use real Docker-backed execution instead of shallow mocks.

Drop-in AWS compatibility

Point standard AWS clients at http://localhost:4566. Existing credentials, regions, SDKs, CLI commands, and IaC workflows stay familiar.

Fast enough for CI

The native image starts in milliseconds and keeps idle memory low, making it practical for local development and test pipelines.

Configurable persistence

Choose from in-memory, persistent, hybrid, and write-ahead log storage depending on the durability profile you need.

Why Floci?

LocalStack's community edition sunset in March 2026, requiring auth tokens and freezing security updates. Floci is the no-strings-attached alternative.

CapabilityFlociLocalStack Community
Auth token requiredNoYes
Security updatesYesFrozen
Startup time~24 ms~3.3 s
Idle memory~13 MiB~143 MiB
Docker image size~90 MB~1.0 GB
LicenseMITRestricted
API Gateway v2 / HTTP APIYesNo
CognitoYesNo
RDS, ElastiCache, MSKReal DockerNo
Neptune (graph DB + Gremlin WebSocket)Real DockerNo
DocumentDB (MongoDB-compatible)Real DockerNo
ECS, EC2, EKSReal DockerNo
CodeBuildReal Docker executionNo
Native binary~40 MBNo

58 AWS services. Broad coverage. Free forever.

Architecture Overview

flowchart LR
    Client["AWS SDK / CLI"]

    subgraph Floci ["Floci, port 4566"]
        Router["HTTP Router\nJAX-RS / Vert.x"]

        subgraph Stateless ["Stateless Services"]
            A["SSM · SQS · SNS\nIAM · STS · KMS\nSecrets Manager · SES\nCognito · Kinesis\nEventBridge · Scheduler · AppConfig\nCloudWatch · Step Functions\nCloudFormation · ACM · Config\nAPI Gateway · AppSync · ELB v2 · Auto Scaling\nCodeDeploy · Backup · Bedrock Runtime · Route53 · Transfer"]
        end

        subgraph Stateful ["Stateful Services"]
            B["S3 · DynamoDB\nDynamoDB Streams"]
        end

        subgraph Containers ["Container Services"]
            C["Lambda\nElastiCache\nRDS\nNeptune\nECS\nEC2\nMSK\nEKS\nOpenSearch\nCodeBuild"]
            D["Athena -> floci-duck\nDuckDB sidecar"]
        end

        Router --> Stateless
        Router --> Stateful
        Router --> Containers
        Stateless & Stateful --> Store[("StorageBackend\nmemory · hybrid · persistent · wal")]
    end

    Docker["Docker Engine"]
    Client -->|"HTTP :4566\nAWS wire protocol"| Router
    Containers -->|"Docker API\nIAM / SigV4 auth"| Docker

Supported Services

Floci supports local emulation for application services, data services, eventing, identity, infrastructure, billing, and container-backed workloads.

CategoryServices
Core app servicesS3, SQS, SNS, DynamoDB, Lambda, IAM, STS, KMS, Secrets Manager
Events and workflowsEventBridge, EventBridge Pipes, EventBridge Scheduler, Step Functions, CloudWatch Logs, CloudWatch Metrics
API and identityAPI Gateway REST, API Gateway v2, AppSync, Cognito, ACM, Route53, Cloud Map
Containers and computeECS, EC2, EKS, CodeBuild, CodeDeploy, Auto Scaling, ELB v2
Data and analyticsAthena, Glue, EMR, Firehose, OpenSearch, Textract, Transcribe
Security and governanceWAF v2, CloudTrail
DatabasesRDS, RDS Data API, Neptune, DocumentDB
Messaging and transferSES, SES v2, Kinesis, Transfer Family
Cost and billingPricing, Cost Explorer, Cost and Usage Reports, BCM Data Exports
Backup and configAWS Backup, AWS Config, AppConfig, AppConfigData, CloudFormation

For operation-level compatibility, see the Services Overview.

Detailed service notes
ServiceHow it worksNotable features
SSM Parameter StoreIn-processVersion history, labels, SecureString, tagging
SSM Run CommandIn-process + EC2 containersSendCommand, GetCommandInvocation, ListCommands, CancelCommand, direct EC2 container execution, agent polling via ec2messages
SQSIn-processStandard and FIFO queues, DLQ, visibility timeout, batch operations, tagging
SNSIn-processTopics, subscriptions, SQS, Lambda and HTTP delivery, tagging
S3In-processVersioning, multipart upload, pre-signed URLs, Object Lock, event notifications
DynamoDBIn-processGSI, LSI, Query, Scan, TTL, transactions, batch operations
DynamoDB StreamsIn-processShard iterators, records, Lambda event source mapping trigger
LambdaReal DockerRuntime environment, execution model, warm container pool, aliases, Function URLs
API Gateway RESTIn-processResources, methods, stages, Lambda proxy, MOCK integrations, AWS integrations
API Gateway v2In-processHTTP APIs, routes, integrations, JWT authorizers, stages
AppSyncIn-processGraphQL API management API, schema registry, AWS scalars, domain names, channel namespaces
IAMIn-processUsers, roles, groups, policies, instance profiles, access keys
STSIn-processAssumeRole, WebIdentity, SAML, GetFederationToken, GetSessionToken
CognitoIn-processUser pools, app clients, auth flows, JWKS and OpenID well-known endpoints
KMSIn-processEncrypt, decrypt, sign, verify, data keys, aliases
KinesisIn-processStreams, shards, enhanced fan-out, split and merge
Secrets ManagerIn-processVersioning, resource policies, tagging
Step FunctionsIn-processASL execution, task tokens, execution history
CloudFormationIn-processStacks, change sets, resource provisioning
EventBridgeIn-processCustom buses, rules, SQS, SNS and Lambda targets
EventBridge PipesIn-processPoller-based integration connecting SQS, Kinesis, DynamoDB, and MSK sources to targets with optional filtering
EventBridge SchedulerIn-processSchedule groups, schedules, flexible time windows, retry policies, DLQs
CloudWatch LogsIn-processLog groups, streams, ingestion, filtering
CloudWatch MetricsIn-processCustom metrics, statistics, alarms
ElastiCacheReal DockerRedis / Valkey protocol, IAM auth, SigV4 validation
RDSReal DockerPostgreSQL, MySQL, MariaDB, IAM auth, JDBC-compatible engines
RDS Data APIREST JSON over real RDS containersRaw SQL execution and transactions for local MySQL / MariaDB RDS resources
NeptuneReal DockerGraph DB via TinkerPop Gremlin Server; RDS-shaped control plane; Gremlin WebSocket on port 8182 with SigV4 proxy
DocumentDBReal Docker, mock mode availableMongoDB-compatible cluster via real MongoDB containers; RDS-shaped control plane; MongoDB wire protocol on port 27017
MSKReal DockerKafka-compatible broker via Redpanda
AthenaIn-process with DuckDB sidecarReal SQL execution over S3 and Glue-backed views
GlueIn-processData Catalog, Schema Registry, tables consumed by Athena
EMRIn-processCluster (job flow) lifecycle, instance groups and fleets, steps, security configurations, tagging
Data FirehoseIn-processStreaming delivery, NDJSON flush to S3
ECSReal DockerClusters, task definitions, tasks, services, capacity providers, task sets
EC2Real DockerRunInstances launches containers, SSH key injection, UserData, IMDS, VPC resources
ACMIn-processCertificate issuance and validation lifecycle
ECRIn-process with real registryRepositories, docker push / pull, image-backed Lambda functions
Resource Groups Tagging APIIn-processGetResources, tag and untag resources, tag key and value discovery across services
SESIn-processSend email, raw email, identity verification, DKIM, templates
SES v2In-processREST JSON API, identities, DKIM, account sending, templates
OpenSearchReal DockerDomain CRUD, tags, versions, instance types, upgrade stubs
AppConfigIn-processApplications, environments, profiles, hosted versions, deployments
AppConfigDataIn-processConfiguration sessions and dynamic configuration retrieval
Bedrock RuntimeIn-process stubDummy Converse and InvokeModel responses for local development
EKSReal Docker, mock mode availablek3s clusters with live Kubernetes API server
ELB v2In-processALB, NLB, target groups, listeners, routing rules, Lambda targets, tags
CodeBuildIn-process with real DockerReal buildspec execution, CloudWatch logs, S3 artifacts
CodeDeployIn-process with Lambda traffic shiftingDeployment groups, configs, lifecycle hooks, auto-rollback
Auto ScalingIn-process with reconcilerLaunch configs, ASGs, desired capacity reconciliation, lifecycle hooks
AWS BackupIn-processVaults, backup plans, selections, simulated job lifecycle, recovery points
AWS ConfigIn-processConfig rules, configuration recorders, delivery channels, conformance packs, tagging
CloudTrailIn-processTrail lifecycle, event selectors, logging status; management API only
WAF v2In-processWeb ACLs, IP sets, regex pattern sets, rule groups, logging configs, resource associations, tagging (REGIONAL and CLOUDFRONT scopes)
Route53In-processHosted zones, SOA and NS records, resource record sets, change tracking, tagging
Cloud MapIn-processHTTP and DNS namespaces, services, instance registration, discovery queries, operations, tagging
Transfer FamilyIn-processServer lifecycle, user management, SSH key import, tagging
TextractIn-process stubAPI-compatible stubs, dummy block data, async job simulation
TranscribeIn-process stubTranscription jobs and custom vocabularies; jobs complete immediately, no real audio processing
PricingIn-process with static snapshotProduct discovery, attributes, price list files, pagination
Cost ExplorerIn-processCost synthesized from Floci resource state and pricing snapshots
Cost and Usage ReportsIn-process with floci-duck sidecarCUR 2.0 and FOCUS 1.2 columns, account-scoped storage, Parquet emission
BCM Data ExportsIn-processExport lifecycle, executions, update and delete operations

Real Docker Integration

Floci uses real Docker containers when in-process emulation would reduce fidelity. This applies to stateful databases, connection-heavy protocols, runtimes, and build systems.

ServiceDefault imageWhat is real
Lambdapublic.ecr.aws/lambda/<runtime>AWS runtime environment, execution model, warm container pool
ElastiCachevalkey/valkey:8Redis / Valkey protocol, ACL-based IAM auth, SigV4 validation
RDS PostgreSQLpostgres:16-alpinePostgreSQL engine, IAM auth, JDBC-compatible access
RDS MySQL / Auroramysql:8.0MySQL engine, IAM auth, JDBC-compatible access
RDS MariaDBmariadb:11MariaDB engine, IAM auth, JDBC-compatible access
Neptunetinkerpop/gremlin-server:3.7.3TinkerPop Gremlin Server; Gremlin WebSocket on port 8182; SigV4 auth proxy
DocumentDBmongo:7.0MongoDB engine; MongoDB wire protocol on port 27017
MSKredpandadata/redpanda:latestKafka-compatible broker via Redpanda
EC2AMI-mapped Linux imagesLinux containers, SSH key injection, UserData, IMDS, IAM credentials
ECSUser-specified task imageContainer lifecycle, start, stop, health checks
EKSrancher/k3s:latestKubernetes API server via k3s
CodeBuildUser-specified environment imageBuildspec execution, log streaming, S3 artifact upload
OpenSearchopensearchproject/opensearch:2Full OpenSearch engine with REST API
ECRregistry:2OCI-compatible registry for docker push and docker pull

Docker-backed services require the Docker socket:

docker run -d --name floci \
  -p 4566:4566 \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -u root \
  floci/floci:latest

Overriding default images

VariableDefault
FLOCI_SERVICES_ELASTICACHE_DEFAULT_IMAGEvalkey/valkey:8
FLOCI_SERVICES_RDS_DEFAULT_POSTGRES_IMAGEpostgres:16-alpine
FLOCI_SERVICES_RDS_DEFAULT_MYSQL_IMAGEmysql:8.0
FLOCI_SERVICES_RDS_DEFAULT_MARIADB_IMAGEmariadb:11
FLOCI_SERVICES_MSK_DEFAULT_IMAGEredpandadata/redpanda:latest
FLOCI_SERVICES_OPENSEARCH_DEFAULT_IMAGEopensearchproject/opensearch:2
FLOCI_SERVICES_NEPTUNE_DEFAULT_IMAGEtinkerpop/gremlin-server:3.7.3
FLOCI_SERVICES_DOCDB_DEFAULT_IMAGEmongo:7.0
FLOCI_SERVICES_EKS_DEFAULT_IMAGErancher/k3s:latest
FLOCI_SERVICES_ECR_REGISTRY_IMAGEregistry:2
FLOCI_ECR_BASE_URIpublic.ecr.aws

Persistence and Storage Modes

Floci can trade speed for durability depending on the workflow. Configure the default mode with FLOCI_STORAGE_MODE, or override storage per service.

ModeBehaviorBest forDurability
memoryEntirely in RAM. Data is lost when the container stops.CI and ephemeral testsNone
persistentLoaded at startup and flushed to disk immediately on every write operation.Simple local state preservation with immediate persistenceMedium
hybridIn-memory performance with periodic async flushing every 5 seconds.Local developmentGood
walWrite-ahead log. Every mutation is logged before responding.Maximum durabilityHighest

Use memory for fast test runs. Use hybrid when you want state preserved across container restarts without much overhead.

For more detail, see the Storage Configuration documentation.

Multi-Account Isolation

Floci supports per-account resource isolation with no extra setup. If AWS_ACCESS_KEY_ID is exactly 12 digits, Floci uses it as the account ID. Resources created by one account are invisible to another.

AWS_ACCESS_KEY_ID=111111111111 aws sqs create-queue --queue-name orders
AWS_ACCESS_KEY_ID=222222222222 aws sqs create-queue --queue-name orders

Any other key format, such as test or AKIA..., causes Floci to fall back to FLOCI_DEFAULT_ACCOUNT_ID, which defaults to 000000000000.

See the Multi-Account Isolation docs.

SDK Integration

Point your existing AWS SDK at http://localhost:4566.

Java, AWS SDK v2
var client = DynamoDbClient.builder()
    .endpointOverride(URI.create("http://localhost:4566"))
    .region(Region.US_EAST_1)
    .credentialsProvider(StaticCredentialsProvider.create(
        AwsBasicCredentials.create("test", "test")))
    .build();

client.createTable(b -> b
    .tableName("demo-table")
    .billingMode(BillingMode.PAY_PER_REQUEST)
    .attributeDefinitions(
        AttributeDefinition.builder().attributeName("pk").attributeType(ScalarAttributeType.S).build())
    .keySchema(
        KeySchemaElement.builder().attributeName("pk").keyType(KeyType.HASH).build()));

System.out.println(client.listTables().tableNames());
Python, boto3
import boto3

client = boto3.client(
    "ssm",
    endpoint_url="http://localhost:4566",
    region_name="us-east-1",
    aws_access_key_id="test",
    aws_secret_access_key="test",
)

client.put_parameter(
    Name="/demo/app/message",
    Value="hello from floci",
    Type="String",
    Overwrite=True,
)

response = client.get_parameter(Name="/demo/app/message")
print(response["Parameter"]["Value"])
Node.js, AWS SDK v3
import { SQSClient, SendMessageCommand } from "@aws-sdk/client-sqs";

const client = new SQSClient({
  endpoint: "http://localhost:4566",
  region: "us-east-1",
  credentials: { accessKeyId: "test", secretAccessKey: "test" },
});

await client.send(
  new SendMessageCommand({
    QueueUrl: "http://localhost:4566/000000000000/demo-queue",
    MessageBody: "hello from floci",
  }),
);
Go, AWS SDK v2
package main

import (
    "context"
    "fmt"
    "log"

    "github.com/aws/aws-sdk-go-v2/config"
    "github.com/aws/aws-sdk-go-v2/credentials"
    "github.com/aws/aws-sdk-go-v2/service/s3"
)

func main() {
    cfg, err := config.LoadDefaultConfig(context.TODO(),
        config.WithRegion("us-east-1"),
        config.WithCredentialsProvider(
            credentials.NewStaticCredentialsProvider("test", "test", ""),
        ),
        config.WithBaseEndpoint("http://localhost:4566"),
    )
    if err != nil {
        log.Fatal(err)
    }

    client := s3.NewFromConfig(cfg, func(o *s3.Options) {
        o.UsePathStyle = true
    })

    out, err := client.ListBuckets(context.TODO(), nil)
    if err != nil {
        log.Fatal(err)
    }

    fmt.Println(out.Buckets)
}
Rust, AWS SDK
use aws_sdk_secretsmanager::config::{Credentials, Region};
use aws_sdk_secretsmanager::Client;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let config = aws_config::defaults(aws_config::BehaviorVersion::latest())
        .region(Region::new("us-east-1"))
        .credentials_provider(Credentials::new("test", "test", None, None, "floci"))
        .endpoint_url("http://localhost:4566")
        .load()
        .await;

    let client = Client::new(&config);

    client
        .create_secret()
        .name("demo/secret")
        .secret_string("hello from floci")
        .send()
        .await?;

    Ok(())
}
Bash, AWS CLI
export AWS_ACCESS_KEY_ID=test
export AWS_SECRET_ACCESS_KEY=test
export AWS_DEFAULT_REGION=us-east-1

aws --endpoint-url http://localhost:4566 s3 mb s3://my-bucket
aws --endpoint-url http://localhost:4566 s3 ls

Testcontainers

Floci has Testcontainers modules for starting isolated Floci instances directly from tests. This avoids shared state, manual daemon setup, and port conflicts.

LanguagePackageLatestRegistrySource
Javaio.floci:testcontainers-floci1.4.0Maven CentralGitHub
Node.js@floci/testcontainers0.1.0npmGitHub
Pythontestcontainers-floci0.1.1PyPIGitHub
GoIn progressIn progressN/AGitHub
Java
<dependency>
    <groupId>io.floci</groupId>
    <artifactId>testcontainers-floci</artifactId>
    <version>1.4.0</version>
    <scope>test</scope>
</dependency>
@Testcontainers
class S3IntegrationTest {

    @Container
    static FlociContainer floci = new FlociContainer();

    @Test
    void shouldCreateBucket() {
        S3Client s3 = S3Client.builder()
                .endpointOverride(URI.create(floci.getEndpoint()))
                .region(Region.of(floci.getRegion()))
                .credentialsProvider(StaticCredentialsProvider.create(
                        AwsBasicCredentials.create(floci.getAccessKey(), floci.getSecretKey())))
                .forcePathStyle(true)
                .build();

        s3.createBucket(b -> b.bucket("my-bucket"));
    }
}

For Testcontainers 2.x / Spring Boot 4.x, use version 2.5.0.

Node.js / TypeScript
npm install --save-dev @floci/testcontainers
import { FlociContainer } from "@floci/testcontainers";
import { S3Client, CreateBucketCommand } from "@aws-sdk/client-s3";

describe("S3", () => {
  let floci: FlociContainer;

  beforeAll(async () => {
    floci = await new FlociContainer().start();
  });

  afterAll(async () => {
    await floci.stop();
  });

  it("creates a bucket", async () => {
    const s3 = new S3Client({
      endpoint: floci.getEndpoint(),
      region: floci.getRegion(),
      credentials: {
        accessKeyId: floci.getAccessKey(),
        secretAccessKey: floci.getSecretKey(),
      },
      forcePathStyle: true,
    });

    await s3.send(new CreateBucketCommand({ Bucket: "my-bucket" }));
  });
});
Python
pip install testcontainers-floci
import boto3
from testcontainers_floci import FlociContainer


def test_s3_create_bucket():
    with FlociContainer() as floci:
        s3 = boto3.client(
            "s3",
            endpoint_url=floci.get_endpoint(),
            region_name=floci.get_region(),
            aws_access_key_id=floci.get_access_key(),
            aws_secret_access_key=floci.get_secret_key(),
        )
        s3.create_bucket(Bucket="my-bucket")

Compatibility Testing

The compatibility-tests directory validates Floci across SDKs and tooling workflows.

ModuleLanguage / ToolSDK / ClientTests
sdk-test-javaJava 17AWS SDK for Java v2899
sdk-test-nodeNode.jsAWS SDK for JavaScript v3366
sdk-test-pythonPython 3boto3272
sdk-test-goGoAWS SDK for Go v2 + RDS Data API SDK v1145
sdk-test-awscliBashAWS CLI v2152
sdk-test-rustRustAWS SDK for Rust90
compat-terraformTerraformv1.10+14
compat-opentofuOpenTofuv1.9+14
compat-cdkAWS CDKv2+17

1,969 automated compatibility tests across 6 SDKs and 3 IaC tools.

Migrating from LocalStack

Floci is a drop-in replacement for LocalStack Community. The port, credentials, SDK configuration, and CLI endpoint pattern work the same way. Swap the image and keep going.

# Before
image: localstack/localstack

# After, standard image
image: floci/floci:latest

# After, if init scripts need AWS CLI or boto3
image: floci/floci:latest-compat

LocalStack environment variables are translated automatically:

LocalStackFloci equivalent
LOCALSTACK_HOSTFLOCI_HOSTNAME
PERSISTENCE=1FLOCI_STORAGE_MODE=persistent
LAMBDA_DOCKER_NETWORKFLOCI_SERVICES_LAMBDA_DOCKER_NETWORK
LAMBDA_REMOVE_CONTAINERS=1FLOCI_SERVICES_LAMBDA_EPHEMERAL=true
DEBUG=1QUARKUS_LOG_LEVEL=DEBUG

Init scripts mounted under /etc/localstack/init/ run unchanged. The /_localstack/init and /_localstack/health endpoints are still served. Once the emulator is up, the log also ends with a LocalStack-style Ready. line, so tooling that watches the log for it — such as the default wait strategy of Testcontainers' LocalStackContainer — works unchanged. Set LOCALSTACK_PARITY=false to opt out of automatic translation.

See the full migration guide.

Image Tags

Every tag combines a variant and a channel.

ChannelStandardCompat with AWS CLI and boto3
Release, floatinglatestlatest-compat
Release, pinnedx.y.zx.y.z-compat
Nightly, floatingnightlynightly-compat
Nightly, datednightly-mmddyyyynightly-mmddyyyy-compat

Use latest for stable releases, a pinned version for reproducible builds, and nightly to track main.

# Recommended
image: floci/floci:latest

# Includes AWS CLI and boto3
image: floci/floci:latest-compat

# Pinned release
image: floci/floci:1.5.11

# Track main
image: floci/floci:nightly

Configuration

All settings are overridable through environment variables with the FLOCI_ prefix.

VariableDefaultDescription
FLOCI_PORT4566Port exposed by the Floci API
FLOCI_DEFAULT_REGIONus-east-1Default AWS region
FLOCI_DEFAULT_ACCOUNT_ID000000000000Default AWS account ID
FLOCI_BASE_URLhttp://localhost:4566Base URL used when Floci returns service URLs
FLOCI_HOSTNAMEUnsetHostname used in returned URLs when Floci runs inside Docker Compose
FLOCI_STORAGE_MODEmemoryStorage mode: memory, persistent, hybrid, or wal
FLOCI_STORAGE_PERSISTENT_PATH./dataDirectory used for persisted state
FLOCI_ECR_BASE_URIpublic.ecr.awsECR base URI used when pulling container images

Full reference: configuration docs

Multi-container Docker Compose

When your application runs in a different container, set FLOCI_HOSTNAME to the Floci service name so returned URLs, such as SQS QueueUrl values, resolve correctly.

services:
  floci:
    image: floci/floci:latest
    ports:
      - "4566:4566"
    environment:
      - FLOCI_HOSTNAME=floci

  my-app:
    environment:
      - AWS_ENDPOINT_URL=http://floci:4566
    depends_on:
      - floci

Without this, services may return URLs using localhost, which points to the wrong container from the application container.

Community

Join the Floci community on Slack or GitHub Discussions. Feature ideas, compatibility questions, design tradeoffs, and rough proposals are welcome.

Star History

Star History Chart

Contributors

License

MIT. Use it however you want.