Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Migrating from LocalStack to fakecloud in 10 minutes

Canonical: fakecloud.dev/blog/migrate-from-localstack In March 2026, LocalStack replaced its open-source Community Edition with a proprietary image that requires an account and an auth token. If your build broke last month, this guide is…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Canonical: fakecloud.dev/blog/migrate-from-localstack



In March 2026, LocalStack replaced its open-source Community Edition with a proprietary image that requires an account and an auth token. If your build broke last month, this guide is for you. If you are still on a pinned older tag and worried about the next pull, this is also for you.



fakecloud is a free, open-source AWS emulator — single binary, no account, no token, no paid tier — that covers the services most teams relied on LocalStack Community for, plus several that moved to LocalStack Pro (RDS, ElastiCache, Cognito User Pools, SES v2, API Gateway v2).



This guide is step-by-step. Copy, paste, done.






The one-line summary



Change the image or the install command. Keep http://localhost:4566 and your dummy credentials. Everything else stays the same.






Step 1: Stop LocalStack






docker compose down
# or: docker kill $(docker ps -q --filter ancestor=localstack/localstack)









Step 2: Install fakecloud






# Option A: single binary, no Docker
curl -fsSL https://raw.githubusercontent.com/faiscadev/fakecloud/main/install.sh | bash
fakecloud

# Option B: Docker
docker run --rm -p 4566:4566 ghcr.io/faiscadev/fakecloud

# Option C: cargo
cargo install fakecloud






fakecloud listens on http://localhost:4566 — same as LocalStack.






Step 3: Keep your SDK wiring



Your application code does not change. Endpoint URL and dummy credentials stay identical:




// TypeScript
import { S3Client } from "@aws-sdk/client-s3";
const s3 = new S3Client({
endpoint: "http://localhost:4566",
region: "us-east-1",
credentials: { accessKeyId: "test", secretAccessKey: "test" },
forcePathStyle: true,
});









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









Step 4: Update docker-compose.yml



Before:




services:
localstack:
image: localstack/localstack:latest
ports:
- "4566:4566"
environment:
- SERVICES=s3,sqs,sns,dynamodb,lambda
- DEBUG=1






After:




services:
fakecloud:
image: ghcr.io/faiscadev/fakecloud:latest
ports:
- "4566:4566"






fakecloud starts all services by default (they are lazy and cheap — no SERVICES env var needed).



For Lambda execution you will need Docker-in-Docker or a mounted Docker socket (same as LocalStack Pro required):




services:
fakecloud:
image: ghcr.io/faiscadev/fakecloud:latest
ports:
- "4566:4566"
volumes:
- /var/run/docker.sock:/var/run/docker.sock









Step 5: Update GitHub Actions



Before:




services:
localstack:
image: localstack/localstack
ports:
- 4566:4566
env:
LOCALSTACK_AUTH_TOKEN: ${{ secrets.LOCALSTACK_TOKEN }}






After (install-and-run, no Docker):




steps:
- run: curl -fsSL https://raw.githubusercontent.com/faiscadev/fakecloud/main/install.sh | bash
- run: fakecloud &
- run: |
for i in $(seq 1 30); do
curl -sf http://localhost:4566/_fakecloud/health && exit 0
sleep 1
done
exit 1






~500ms startup vs ~3s for LocalStack container boot. On a cold CI runner the difference adds up over hundreds of test runs.






Step 6: Terraform



Provider block stays the same — only the running emulator changes.




provider "aws" {
access_key = "test"
secret_key = "test"
region = "us-east-1"
skip_credentials_validation = true
skip_metadata_api_check = true
skip_requesting_account_id = true

endpoints {
s3 = "http://localhost:4566"
sqs = "http://localhost:4566"
dynamodb = "http://localhost:4566"
lambda = "http://localhost:4566"
}
}






fakecloud's CI runs the upstream hashicorp/terraform-provider-aws TestAcc* suites against itself, so Terraform flows that worked against LocalStack Community should work against fakecloud.






Things that may need attention





  • SERVICES env var. Drop it. fakecloud starts all services by default.


  • LOCALSTACK_AUTH_TOKEN. Drop it.


  • Persisted state. LocalStack Pro has PERSISTENCE=1. fakecloud has --persist /path/to/dir.






Services that moved from LocalStack Community to Pro (and what fakecloud does)











































Service LocalStack Community now fakecloud
Cognito User Pools Paid only 122 ops, full auth flows + MFA
SES v2 Paid only 110 ops, full send + templates + DKIM
API Gateway v2 Paid only 28 ops, HTTP APIs + JWT/Lambda authorizers
RDS Paid only 163 ops, real PostgreSQL/MySQL/MariaDB via Docker
ElastiCache Paid only 75 ops, real Redis/Valkey via Docker
Bedrock Not available 111 ops (control plane + runtime)





Test-assertion SDKs (bonus)



fakecloud ships test-assertion SDKs that let you inspect side effects from tests without raw HTTP:




import { FakeCloud } from "fakecloud";
const fc = new FakeCloud();

const { emails } = await fc.ses.getEmails();
expect(emails).toHaveLength(1);
expect(emails[0].destination.toAddresses).toContain("[email protected]");

await fc.reset();






SDKs for TypeScript, Python, Go, PHP, Java, Rust. See the SDK docs.






Verify the migration






aws --endpoint-url http://localhost:4566 s3 mb s3://test-bucket
echo hello | aws --endpoint-url http://localhost:4566 s3 cp - s3://test-bucket/hello.txt
aws --endpoint-url http://localhost:4566 s3 ls s3://test-bucket/
aws --endpoint-url http://localhost:4566 s3 rb s3://test-bucket --force






If it works, migration is done.





1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - Migrating from LocalStack to fakecloud in 10 minutes
id: f70d47b5-9fb6-4b86-84bb-13894aad75cd
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "Migrating from LocalStack to f" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Migrating from LocalStack to fakecloud i")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Migrating from LocalStack to fakecloud i*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Migrating from LocalStack to fakecloud i"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Migrating from LocalStack to fakecloud i.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Migrating from LocalStack to fakecloud in 10 minutes

Thematisch verwandte Begriffe: Migrating, from, LocalStack, fakecloud · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-95832 | Improper Neutralization of Special Elements in Output Used by a Downstre…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag