TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Fakecloud.dev presents a local AWS cloud emulator for integration testing that works with standard AWS clients and offers separate SDKs for inspecting and controlling test behavior. Its site claims support for 105 services and says all 248,557 generated Smithy test variants pass; those figures are vendor claims, and independent verification is not provided in the source material.
Fakecloud.dev is presenting Fakecloud, a local emulator for AWS services designed for integration tests. The project says applications can use standard AWS clients against a local endpoint, while separate test SDKs let developers inspect results and manually control asynchronous processors; the site lists 105 AWS services.
The project describes a workflow in which developers run their application with its usual AWS SDK, CLI, or infrastructure-as-code tools, but direct requests to Fakecloud on localhost. The site says the software is available as a single binary or Docker image, accepts dummy credentials, and does not require users to sign in or obtain an authentication token. Its quick-start instructions use the local endpoint at localhost:4566.
Fakecloud also offers first-party testing clients for TypeScript, Python, Go, PHP, Java, and Rust. According to the project, these clients wrap private `/_fakecloud/*` endpoints for resetting state, making assertions, inspecting effects such as sent email or queued messages, and triggering asynchronous processing after application code has used normal AWS APIs. The source lists packages for several languages, including npm, PyPI, pkg.go.dev, and crates.io.
The site reports 105 supported services and 7,508 operations, and says 248,557 of 248,557 Smithy-model-generated test variants pass for its 3,932 implemented API operations on every commit. It also says its suite includes end-to-end tests with official AWS SDKs and describes more than 30 service-to-service integrations, including S3 notifications and API Gateway to Lambda. These are figures and descriptions published by Fakecloud; the supplied material contains no independent test results.
Local Tests Across AWS Services
Integration tests can reveal failures in interactions among cloud services that isolated unit tests or simple mocks may not reproduce. Fakecloud’s stated approach is to let developers run production-style AWS client calls locally, then use its test-specific tools to inspect effects and prompt asynchronous work. That combination could help teams check flows such as notifications, queue processing, and function invocation without routing routine development tests through a live AWS account.
The project also emphasizes access and setup: it says core local workflows require no account, authentication token, or paid plan. That may matter to teams seeking repeatable local development or automated test runs. The practical value will depend on whether the emulator’s behavior matches the AWS features each team uses; the service and conformance counts alone do not establish that fit.
How Fakecloud Fits Local Testing
Local cloud emulators provide endpoints that resemble cloud APIs, allowing applications and test suites to run against a developer-controlled environment. Fakecloud says it is intended to behave more like connected infrastructure than a collection of isolated mocks: it lists cross-service flows such as S3 notifications, SNS fanout, EventBridge targets, DynamoDB Streams, and Step Functions integrations.
The project compares itself with LocalStack Community and says Fakecloud does not require an account or token for local development. It also publishes comparative claims about startup time, memory use, installation size, supported services, and features. These are the developer’s own comparisons, and the provided source does not explain the test conditions or independently corroborate the figures. Fakecloud identifies its license as AGPL-3.0.
“Local AWS cloud emulator for integration tests.”
— Fakecloud.dev
Independent Validation Remains Open
The source material does not provide an announcement date, independent benchmarks, or outside validation of Fakecloud’s service coverage and conformance figures. It also does not establish how closely each implemented operation matches behavior in live AWS, which service versions or edge cases are covered, or how the project will maintain compatibility as AWS APIs change. Developers will need to evaluate the services and behaviors their own tests depend on.
Evaluate Coverage in Test Workflows
The next practical step for teams considering Fakecloud is to install it, point existing AWS clients at its local endpoint, and check whether their integration tests exercise the required APIs and cross-service behavior. Fakecloud’s site provides installation and SDK links, but the supplied material does not announce a release schedule, roadmap, or independent evaluation. Further details on test methodology and compatibility would help assess the project’s published conformance claims.
Key Questions
What is Fakecloud?
Fakecloud is a local emulator for AWS services, presented by its developers as a tool for application integration tests.
Can applications use standard AWS clients with it?
Yes. Fakecloud says applications can use their regular AWS SDKs, the AWS CLI, and infrastructure-as-code tools against its local endpoint.
What do the Fakecloud SDKs add?
The project says its test clients let developers reset state, inspect outcomes such as messages and invocations, make assertions, and manually control asynchronous processors.
How much AWS coverage does Fakecloud claim?
Its site lists 105 services and 7,508 operations. It also claims that 248,557 generated Smithy test variants pass for 3,932 implemented API operations; these figures have not been independently verified in the supplied source.
Does Fakecloud require an AWS account?
Fakecloud says local use requires no account or authentication token and can use dummy credentials. The source describes local development rather than access to live AWS resources.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
