Skip to main content

Command Palette

Search for a command to run...

Floci Deep Dives

Updated
2 min read
A
Hi there! I'm a passionate AWS DevOps Engineer with 2+ years of experience in building and managing scalable, reliable, and secure cloud infrastructure. I'm excited to share my knowledge and insights through this blog. Here, you'll find articles on: AWS Services: Deep dives into core AWS services like EC2, S3, Lambda, and more. DevOps Practices: Best practices for CI/CD, infrastructure as code, and automation. Security: Tips and tricks for securing your AWS environments. Serverless Computing: Building and deploying serverless applications. Troubleshooting: Common issues and solutions in AWS. I'm always eager to learn and grow, and I hope this blog can be a valuable resource for fellow DevOps enthusiasts. Feel free to connect with me on [LinkedIn/Twitter] or leave a comment below!

What is Floci?

Floci is an open-source local cloud emulator that allows developers to run AWS-compatible services locally without using a real AWS account. It is often positioned as an alternative to LocalStack.

Why was it created?

The project aims to provide:

No authentication tokens No paid feature gates Local AWS service emulation Fast startup and low memory usage CI/CD-friendly local testing environments Architecture Deep Dive Application ↓ AWS SDK / CLI ↓ localhost:4566 ↓ Floci ↓ Emulated AWS Services

Your application continues to use standard AWS SDK calls, but instead of hitting AWS, it talks to Floci running locally.

Example:

aws --endpoint-url http://localhost:4566 s3 ls Supported AWS Services

Floci supports dozens of AWS services including:

S3 DynamoDB Lambda ECS EC2 EKS ECR RDS IAM STS SQS SNS CloudFormation Secrets Manager Step Functions CloudWatch API Gateway

and many others.

Why DevOps Engineers Use It

  1. Local Development

Instead of: Developer ↓ AWS Account ↓ Pay AWS Costs

You use: Developer ↓ Floci ↓ Local AWS Environment

This reduces costs and speeds up testing.

  1. CI/CD Pipeline Testing

Example GitHub Actions:

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

Now integration tests can run against local AWS services without provisioning real cloud resources.

  1. Terraform Testing

You can test Terraform locally:

terraform init 
terraform plan 
terraform apply

while pointing providers to Floci endpoints instead of AWS.

ECS/EKS Deep Dive

One interesting aspect is that Floci uses real Docker-backed execution for some services rather than simple mock responses.

Examples include:

Lambda ECS EKS RDS ElastiCache OpenSearch

This provides higher-fidelity testing compared with basic API stubs.

Installation

Run with Docker:

docker run --rm -p 4566:4566 floci/floci:latest

Then configure AWS CLI:

aws --configure

Test:

aws --endpoint-url=http://localhost:4566 s3 mb s3://test-bucket

Floci vs LocalStack Feature Floci LocalStack Open Source Yes Limited community edition Auth Token Required No Often required Startup Speed Very fast Slower Memory Usage Lower Higher Docker-backed Services Yes Some Cost Free Freemium

According to Floci's published benchmarks, it focuses heavily on startup speed and low resource consumption.

Floci Deep Dives