AWS emulator (github.com)
881 points by super_linear 18 hours ago
CharlieDigital 18 hours ago
Skeptical of using because it's not clear whether this was just an exercise or a real product they are going to ship and maintain.
Floci[0] has been great for me. Use the Testcontainers[1], too.
Bonus: works for GCP and Azure, too (so far have only used in limited capacity, though).
ke4qqq 18 hours ago
It’s a real product that we plan to maintain.
sequence7 17 hours ago
Is there anywhere I can find a matrix of what services are emulated and how complete that emulation is? I tried the docs but just ended up going round in circles.
tyingq 17 hours ago
jasonseattle 17 hours ago
icedchai 17 hours ago
dataviz1000 17 hours ago
I mock (ask Claude Code to make something run in a container) my own AWS services today for CI and development. I'm excited to learn more about how AWS uses it and hopefully use this for CI and development.
solyin 14 hours ago
Not to be rude, but your profile doesn't list who you are in relation to AWS.
selfmodruntime 15 hours ago
Any chance it will be able to spawn actual containers in the future?
lysace 10 hours ago
DetroitThrow 10 hours ago
Okay I've asked for this product for literally years on a cadence of every 18 months, so I'm very thankful to hear this.
AdieuToLogic 10 hours ago
>> Skeptical of using because it's not clear whether this was just an exercise or a real product they are going to ship and maintain.
> It’s a real product that we plan to maintain.
29,684 commits in a repository less than a month old does not instill confidence in this being a "real product." That is roughly 1,000 accepted commits per day.
g-b-r 9 hours ago
gigatexal 13 hours ago
Good! Been waiting for a first party thing like this.
It’s actually interesting that such a thing exists. It’s in Amazon’s interest that the only way to test a lot of services is to have a test environment in AWS.
dogleash 18 hours ago
Nothing personal, but unless you can link us to a public announcement made by Amazon, your statement is worth less than nothing.
Official statements made by a company are still poor representations of their current business plans, and don't mean anything 3 months later (no matter how much they pinky promise). But a HN post isn't even that.
ke4qqq 18 hours ago
Cthulhu_ 18 hours ago
toomuchtodo 18 hours ago
Until the plan changes, which at some point, it will. Comment is still appreciated for what it is.
Edit: Comment is in the spirit of "it gets tiring to build on sand which is at the whims of corporate management folks far disconnected from the actual work." If someone is asserting "this will stick around," words are insufficient, words are free. Show me the contract, show me the penalties for failure to abide by the assertion.
dotancohen 18 hours ago
switchbak 17 hours ago
QGQBGdeZREunxLe 18 hours ago
aseipp 17 hours ago
polishdude20 18 hours ago
switchbak 18 hours ago
In my experience Floci has been the epitome of vibe coded - huge amount of changes, with things breaking randomly between releases. Moved away from it as soon as I could. Still better than Localstack :)
I didn't have a good experience with test containers, but perhaps it'd work better with fast starting containers. We run our test fixture with compose, and have the tests manage their data in isolation - so we don't pay the startup penalty in our test suites.
I think I'd trust this project at least as much as Floci. Embedded Rust mode also looks very interesting for us.
CharlieDigital 17 hours ago
I only use Testcontainers with "explicit" tests (do not run by default in CI; must be run explicitly). This lets agents exercise the integration with a realistic fake locally, but does not incur the cost in CI nor for any dev unless they run it explicitly (usually also with a category so it's explicit + category filter)
olalonde 15 hours ago
It's in their official docs, so probably not just someone's side project: https://docs.aws.amazon.com/emulator/
ttul 16 hours ago
AWS isn’t Google. They tend to maintain everything they put out and they don’t put out things randomly as a result.
thinkingtoilet 15 hours ago
Not really. I was trying to use their own Q AI to help me get something set up and it was constantly wrong about what screens to go to, what was on the screens etc... If their own AI doesn't understand AWS, I don't have confident this will either.
iLoveOncall 17 hours ago
It has an official documentation on the AWS website, why would you assume it's not a real product? Because it was launched recently?
CharlieDigital 17 hours ago
No docs site linked on the GH. 3 weeks old. Blog post talks more about the process than the tool and opens with:
> How we built the agents that built AWS Emulator
> Thousands of autonomous AI agents wrote every line of code in AWS Emulator, a new local emulator for AWS now available for download.
Doesn't feel like a real product. But I also didn't look very hard for docs; I kind of expect it to be linked on the GH in the site and have a nice `llms.txt` for me to give to my agents.
_msw_ 16 hours ago
simgoh 17 hours ago
iLoveOncall 17 hours ago
scriptsmith 14 hours ago
From the security page [0]
> Don’t use the emulator to test the following:
> - IAM policies and permissions boundaries
> - Resource-based policies, such as bucket policies
> - AWS KMS key policies
> - Access across AWS accounts or across AWS Regions
> - Any other security control
> Some services in the emulator evaluate IAM policies for IAM users and roles that you create in the emulator, but not the same way as AWS. The emulator never denies a request signed with its own key. It doesn’t check AWS KMS key policies or Amazon S3 bucket policies. It also doesn’t support calls across accounts or Regions. So a request that AWS denies might succeed in the emulator. A request that AWS allows might fail.
This is a shame because I'd love for the official AWS product to be better than e.g. ministack and localstack on this, which will go some of the distance. I think because the agents were only building on the public API surface, it's hard to build this part. But they should've tried and let the agents read whatever policy engines AWS has. Or maybe it's a way to prevent someone from trivially running aws-emulator as AWSaaS?
[0] https://docs.aws.amazon.com/emulator/latest/userguide/securi...
davidjkerber 12 hours ago
I've implemented the AWS IAM engine and all policy types, conditions, etc in here if you want to try it out. It's the most thorough in terms of edge case coverage I'm aware of and I'm constantly adding enhancements and closing edge cases.
https://github.com/act-security-labs/iam-lens
It uses https://github.com/act-security-labs/iam-collect to get all the policies which includes example terraform to gather all the data at scale.
solatic 3 hours ago
I shudder at the thought that local emulation is somehow supposed to handle IAM conditions like source VPC endpoints, EKS Pod Identity, chained roles originating from web identity providers...
IAM itself is free. Most IAM conditions involve resources which are free (e.g. VPC gateway endpoints, web identity providers) or which are free additions on top of a cluster you have for other purposes (e.g. EKS Pod Identity). Presumably you already have an AWS account. What value does an emulator give here?
scriptsmith an hour ago
Yep, it's a complicated beast so I'd love to be able to mess around with it locally! I don't mind using an AWS account for a shared staging environment in the CI pipeline, but trying to figure out policies and roles during development, it can get a bit messy coordinating and handling the lifecycle of resources in a team's testing account (maybe this is easier if you get your own account?). And accounts aren't free when they require GuardDuty etc, unfortunately.
donavanm 13 hours ago
The current IAM engine and language “balsa”, is its own thing. Its vended as a library with large “there be dragons” disclaimers if you even think about going outside the public interfaces. There are also big opaque interactions between different components like STS, KMS, service principals, service-specific resource policy evaluations, etc. I doubt that can be reasonably open sourced or exposed.
There was an attempt at a public implementation of the “next gen” AWS IAM language/engine with “cedar.” However I think that got sidetracked as an authz product and didnt have any real penetration with AWS IAM.
Lucasoato 13 hours ago
I suppose it would have been extremely complex to replicate all of that. Maybe they thought it’s out of the scope to emulate all security patterns locally, they just wanted to focus into providing a native alternative to let users do integration tests.
wg0 15 hours ago
Say whatever but without AI and agents, no one in AWS would have thought of building this given the huge amount of services they have. Humanly, possible but very very costly. Not saying has not happened before but fakecloud and localstack etc? That moat is gone.
I am shocked TBH that this is the new normal. Agents writing code in one of the most difficult to use languages. And ugly as well TBH, it pokes into your eyes. Subjective I know but it is a horrible language for humans.
neobrain 14 hours ago
> Agents writing code in one of the most difficult to use languages
Arguably, languages with strong static guarantees are exceptionally effective for LLMs since they're much quicker to provide feedback to the LLM than a dynamically typed language (which only fails once you actually run it - often several times to find the actual problem). You also get very well-designed build error messages rather than having to parse unstructured stderr output, etc etc.
wg0 14 hours ago
Yes absolutely - that's objectively true. That's why Typescript, Go and Rust are some of the best languages with LLMs because feedback loop is precise and fast to verify the generated output.
UltraSane 13 hours ago
iknowstuff 15 hours ago
Rust is beautiful! The way all the stdlib traits slot into each other satisfies a very particular itch
fukaiall 13 hours ago
You serious? Visually it is one of the most ugliest languages that I know of.
nchie 12 hours ago
wg0 12 hours ago
wg0 15 hours ago
Like I said - subjective. Crates, modularity, tooling? Nothing comes close to Rust. Period.
dzonga 15 hours ago
yeah for all the faults with 'a.i' certain things have just become possible because of it.
nalekberov 15 hours ago
We are talking about a company with ~3T market cap, right?
Geezus_42 an hour ago
That's for paying execs and buying politicians, not paying workers.
raincole 14 hours ago
Exactly. Amazon is worth 3T because they're really good at cutting cost.
airstrike 14 hours ago
As a human, beep boop, I find Rust a beautiful language.
fergie 5 hours ago
I feel like we don't talk enough about the massive problem of creating local test environments for AWS deployments.
An actual AWS supported env that you can run on your local machine would be super useful, even if it just had a subset comprising the most popular services.
morelandjs 18 hours ago
Fellow Amazonian here. Want to say that I’m grateful you built this and it has tremendous value if pulled off well and properly maintained.
Agentic development is all about closing off a system as much possible, then mocking up or simulating any inputs or dependencies that cannot be closed off. At that point, you let Claude crawl over the system and do its thing.
This inevitably runs into problems with infrastructure and any tools that help mock up those interfaces will be tremendously valuable. Thank you!
pprotas 40 minutes ago
Tried it out, this does not seem to work well. A codebase that runs fine on MiniStack could not be emulated with this official AWS emulator.
Specifically it does not support certain SFN fields (like `Assign`) and Lambda Python code was not fully supported, so SFNs and Lambdas did not work and the test had to stop there.
Shakahs 16 hours ago
AWS already models all their services with Smithy, the specification language they created. Their API clients are all generated from Smithy, and the emulator seems to have been built using the Smithy specs and comprehensive integration testing against the real APIs. Using the spec ensures they hit every variant and optional field of every endpoint, unlike Floci and Ministack that only implement the more commonly used ones.
arpinum 20 minutes ago
Smithy doesn't help when a field is a string type but embeds an entire DSL.
Waterluvian 17 hours ago
If I understand this correctly, it means I can point my entire CDK project to the emulator and test a `cdk deploy`?
I'm curious just how realistic the "internal" behaviour is emulated. It's been a while (since I got my stack working and I just don't like touching it now...), but I recall it being a real pain that sometimes odd, sometimes inconsistent things happened with setup and teardown (even through Terraform), which led to long timeouts if you did things in the wrong (but seemingly valid) order.
billyp-rva 17 hours ago
> I'm curious just how realistic the "internal" behaviour is emulated.
It seems like some reasonable shortcuts are taken, like services reading from each other's states directly instead of using APIs [0]. But then it will go so far as to run an in-process NodeJS emulator for lambda functions, and give it a shim so the code it runs can call other emulated AWS services using the main router [1].
[0] https://app.ilograph.com/demo.ilograph.AWS%2520Emulator/Serv... [1] https://app.ilograph.com/demo.ilograph.AWS%2520Emulator/Invo...
0xbadcafebee 13 hours ago
You could try but it likely wouldn't be reliable. AWS services have a lot of undocumented business logic that fails only when you trigger the code path. Like trying to create a resource with an attribute with too many characters, or the wrong character, etc. Doesn't fail until you run that call with that specific value. This emulator doesn't contain each service's full business logic, so you won't see the error until you try the real thing.
jbmchuck 17 hours ago
AFAICT there isn't a quick way to reset state other than restarting the process - in other words it probably isn't a drop in replacement for https://github.com/getmoto/moto for running tons of tests where the state of the mocked AWS system needs to be reset after each test. Hopefully they will implement a quick reset functionality; multiple accounts and full org APIs emulation would be nice too.
brianskarda 12 hours ago
I’m curious how you would want to leverage the orgs API or multiple accounts? What’s the use case you are envisioning?
mdaniel 9 hours ago
I'm not them but I added AWS Organizations support to moto because we needed to test all of the child account enumeration APIs. If I would have had more time/energy I would have continued my tilting at windmills to have it honor the actual $(aws sts assume-role) keys, too, since hopping between accounts in the org via the injected IAM Role was also very critical to the product at the time
I got a lot of enjoyment out of https://awsteele.com/blog/2020/09/26/aws-access-key-format.h... at the time, too
super_linear 18 hours ago
Related to this post: https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent...
singron 16 hours ago
> We’ve had our agents build many versions of this emulator as we’ve refined the building machine.
I'm curious how many versions they made and the token spend on each one. There are a lot of failure modes to projects like these (e.g. gas town endlessly developing itself). Is this more of a sly marketing stunt or a real indication that this methodology is practical and economical?
FYI I checked out the repo. `du --apparent-size -h` output for some dirs:
2.2G .
1.3G .git
58M issues/things-that-do-not-work
74M issues/things-that-now-work
MiroslavPokorny 11 hours ago
> At least 100 GB of free disk for target/. The workspace has one crate per AWS service, so a debug build of everything is large, and it grows as services are added.
100GB !??!?!
schonfinkel 17 hours ago
What makes this any different than fakecloud?
https://github.com/faiscadev/fakecloud
I had a good time using its SDK inside my integration tests. I'll give a couple months before even moving to this because it's weird how similar both projects look like.
EDIT: After checking AWS's project I'd say stay away from it, looks heavily vibe slopped.
Bnjoroge 16 hours ago
claude is the second-most frequent author in that fakecloud repo, what makes you say that's not vibeslopped either? This is 100% the perfect usecase of using a swarm of agents. It's a bounded, and easily-verifiable with property testing/mitm proxying, task. If you think in November 2026, agentic engineering is equivalent to vibe coding, you need to update your priors
schonfinkel 15 hours ago
at least in fakecloud's case, there's still humans being assisted by LLMs.
one can also argue that offering SKDs for python / typescript / golang makes the project superior still. So you are not stuck with Rust-only projects.
jatora 9 hours ago
every codebase has ai code. get over it. humans can be sloppy coders as well.
resters 13 hours ago
This will make it even easier for competitors to reliably clone AWS services, which reveals that cloud is fully commoditized at this point, and advantages come down to market power (buying servers/bandwidth at scale, building data centers at scale, etc).
0x696C6961 11 minutes ago
A DynamoDB that only runs on one machine won't help you build a DynamoDB that horizontally scales.
Lucasoato 13 hours ago
I don’t think AWS is worried about that. If the small cloud provider competitor standardizes on their API, they’re already winning. It will be easier for you to migrate to AWS once you hit the ceiling of the competitor’s scale. That’s something you can’t copy out of the box (and the true AWS value proposition imo).
jaza 12 hours ago
I think you massively underestimate how big AWS's moat is, and how hard it is for newcomers to effectively compete with them. AWS's ever-growing feature list is impressive, sure, but what customers are actually paying for is good customer service, high reliability, and most importantly, trust that AWS will be around for decades to come and that all infra issues become AWS's problem rather than their own.
Salgat 11 hours ago
Any serious competitor would have already invested the trivial amount of money required to gain full access to AWS to probe and test all their services.
2001zhaozhao 13 hours ago
This is my first thought when I saw this as well.
tptacek 18 hours ago
The title for this story should be "aws-emulator, from AWS".
simgoh 16 hours ago
Why?
akerl_ 15 hours ago
Because the rules say not to editorialize post titles
simgoh 15 hours ago
JoshTriplett 14 hours ago
This simulates API responses, like a mocking mechanism, which is enough for some testing. But if you call RunInstances, the corresponding code of the launched instance doesn't actually run. So if you have orchestration code you want to test, that depends on actually running the instances you launch, this won't test it.
Spinifex (https://github.com/mulgadc/spinifex/) seems more promising than this, because its RunInstances actually launches VMs.
OptionOfT 15 hours ago
I remember asking this to one of the evangelists when AWS first came out, how do I run this locally. This was during the times where we actually tried to get all the .NET and C/C++ docs locally.
Now doing the math I feel old.
mdaniel 9 hours ago
There was an offline help system in Visual Studio Community 2012 that would cheerfully download all the help files as a pseudo-.zip file, and for sure included both .NET and C++, along with SQL Server and it's my _recollection_ it included Office's OpenXML documentation, too
gateauxd 18 hours ago
Excited to see this develop and be a free replacement to localstack / similar providers.
schonfinkel 16 hours ago
Except that https://github.com/faiscadev/fakecloud has been a thing for a long time and it's AGPLv3.
aabhay 18 hours ago
Localstack is almost entirely free. I’ve used it at our company for years without paying.
sequence7 17 hours ago
Localstack is no longer free and if you’re using it commercially you need to pay for a license. The free plan explicitly states that it is non commercial.
https://blog.localstack.cloud/2026-upcoming-pricing-changes/
thatslast 6 hours ago
I'm wondering how much of this was vibecoded
floro 6 hours ago
Likely no human ever read the code
Thaxll 13 hours ago
All those emulators are usually bad even if it's official, full of shortcuts and corner cases, just connect to the real service.
gosen 18 hours ago
Do I need to get certified to use it?
OJFord 16 hours ago
> How AWS Emulator keeps improving
> AI agents keep the emulator up to date with AWS.
Is pretty interesting! No more detail than that tease though.
https://docs.aws.amazon.com/emulator/latest/userguide/what-i...
papichulo4 16 hours ago
Thanks to Fable, I’d imagine :)
I’ve been having it build local mock APIs for any service that exposes its OpenAPI spec. Works like a charm.
paavohtl 18 hours ago
Looks like this was ~100% generated with Claude within the past month. Interestingly it still has a lot of occurrences of words that Opus used way too much pre 5.5, so maybe they're not using the latest models.
https://github.com/search?q=repo%3Aaws%2Faws-emulator+load-b...
https://github.com/search?q=repo%3Aaws%2Faws-emulator+%2Fno+...
https://github.com/search?q=repo%3Aaws%2Faws-emulator+golden...
mystifyingpoi 17 hours ago
Seems like a great fit for LLM - extensive documentation, plus a live system it can probe against freely to match the behavior.
whalesalad 17 hours ago
29,000 commits in a month is crazy
switchbak 17 hours ago
I mean, if they're using it internally then there's probably a TON of context you can feed these things to converge on approximately-correct solutions. Certainly it sounds like it can be a much better alternative to Localstack/Floci and friends.
stuff4ben 18 hours ago
Wonder if this could be considered a replacement for Ministack which itself was a vibe-code replacement of Localstack?
nnucera an hour ago
Hey, I'm one of the MiniStack maintainers. We'll definitely keep maintaining and running MiniStack. We're already well established, with many companies using it, including NVIDIA, NASA, Block, and others.
Until the AWS emulator can match all our current capabilities, such as multi-account, multi-region, IAM, running IaC, etc., we'll still be around
One of our core principles has always been to focus on supporting only the most commonly used services
BorisMelnik 18 hours ago
looks like ministack made an announcment
pavel_lishin 18 hours ago
toddyholiday 12 hours ago
This is cool, looks like AWS heard all the buzz around emulators like Floci, Ministack, Fakecloud etc. Wonder how this will fit in with proper infra tools like Spinifex.
ppcdeveloper 15 hours ago
Thank the maker!! I was not having a good time with LocalStack, only an average time. Definitely have to try this out. I need the environment to survive a reboot.
cypherpunk666 13 hours ago
i once saw someone suggest simulation, with a formal model. https://docs.google.com/document/d/154XE2Wx3Ojp7weqaHyrqN9U3...
seshness 13 hours ago
How did you choose CC0 for the open source license vs relatively more common MIT/BSD/Apache licenses?
chaz6 15 hours ago
The README.md states you need 100GB free disk space to build, and they do not provide binary releases. I hope that changes soon!
hollowturtle 16 hours ago
Wouldn't be better using agents for simplifying the mess some services like iam or cognito are?
ram_rattle 9 hours ago
looking at the project history it looks new, if so why did it take AWS so long to put out something like this?
asdfman123 16 hours ago
This is no doubt made possible by an agentic coding loop. If you have the right checks in place, it can be easy to emulate existing software.
I was able to create a TV emulator at my work with a mostly independent agentic loop, because we have a lot of tests to examine a smart TVs APIs. The agents mostly just need to make the tests pass.
__natty__ 17 hours ago
For me, what is interesting in this project is it's git history.
heliosAtwork 16 hours ago
Repo has 29,684 Commits!
Code frequency pages shows:
"There are too many commits to generate this graph."
stanac 16 hours ago
First commit two weeks ago. Insane number of commits, even for AI agents. They must be using large fleet of agents.
nodesocket 15 hours ago
Does this have pricing data? So you can see how much deployed resources cost?
mdaniel 14 hours ago
They wouldn't include it otherwise the binary would be comically large since (as one might guess) there are a lot of knobs involved in pricing AWS things. Just downloading it takes several minutes, served from S3
https://github.com/opencost/opencost/blob/v2.5.3/pkg/cloud/a... is the source URL, and while I haven't been in the opencost ecosystem for a while, I'd guess there's a non-zero chance you could legitimately just ask it to price your aws-emulator resources. I am pretty sure there is a terraform/opentofu integration, too, although I don't this second know if it is within opencost or is a separate project
MisterMunchkin 15 hours ago
Oh fuck yeah. I was really annoyed by companies wanting you to pay just to use a simple offline emulator which doesn’t cost them anything.
ChrisArchitect 17 hours ago
ggcr 17 hours ago
Will it be maintained? Or was it more of a toy-project for its large scale agentic blogpost? [0]
[0] https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent...
xyos 16 hours ago
it's going to be maintained, official product
forgotpwd16 18 hours ago
~30K commits in 3w; quality software for sure. Is someone trying to get promotion by tokenmaxxing? Ironic or unlucky coincidence or competitor(s) misdirection, that, only 2w ago, Amazon published memo discouraging AI abuse?
enowapi 3 hours ago
That’s cute. I wrote an AWS emulator 10 years ago. A few days, zero tokens, and it actually worked and it didn’t “bleed” requests. It alerted the developers
sebmellen 18 hours ago
RIP LocalStack… can’t say I’d be unhappy to see it go though.
microflash 17 hours ago
> AWS Emulator is configured to collect and report usage data to AWS, to gain insight into how AWS Emulator is used. Telemetry is on by default.
They can't help themselves, can they?
I'll stick with Floci and Testcontainers.
tangotaylor 8 hours ago
> AWS Emulator is a local emulator of the AWS APIs. You use it to test your software without calling AWS, on your own machine, on a development server, or in continuous integration (CI).
Underrated README intro. Gets straight to the point of what it is, and why I should use it. I'm guessing an AI didn't write it.
enowapi 3 hours ago
That’s cute. I wrote an emulator single about 5 years ago. It was about 1000 lines and didn’t take $100k in resources
prescriptivist 15 hours ago
It's funny to read AI-generated documentation that is the result of a prompt instructing the LLM to be as terse and straightforward as reasonably possible. The agent was probably told to conform to ASD-STE100.
It's better than a lot of AI-generated documentation, but it also comes across as a gruff LLM that it is annoyed that it has to write the documentation at all.
zmmmmm 13 hours ago
I spent a good 10 mins clicking in circles trying to find out which services are supported, surely one of the most critical pieces of information anybody would probably want to know. I gave up.
xlayn 13 hours ago
I know one day it will be revealed and I'll be proved right, that AI was built just to understand how the heck you get anything done in AWS.
InsidiousWombat 17 hours ago
Seems like the bunch of AI induced failures they had "paid off" in getting this done
toenail 17 hours ago
Mh, no transfer family service... I wonder what else is missing..
st3fan 15 hours ago
29000 commits and no contributors
BorisMelnik 18 hours ago
ok who's gonna build the GUI / web console on top of it?
nnucera 15 minutes ago
StackPort ;)
mdaniel 14 hours ago
I was reminded of https://github.com/localstack/local-surf but two things materialized out of trying it out against my local aws-emulator build: AWS Console uses a proxy endpoint just for their console, and is not implemented 100% in terms of "public" AWS api endpoints; and the other is that aws-emulator (as of v1.0.322 anyway) does not expose CORS headers which is fatal to trying to have the extension contact localhost
So, it's possible that some things would work after patching aws-emulator to cough up CORS headers, but I don't know what the state of affairs is for any reverse engineering of their console proxy endpoint. Likely it's available in localstack somewhere, given who made the extension, but I didn't go digging
awestroke 18 hours ago
For what? Use the APIs.
mystifyingpoi 17 hours ago
I could see this being useful. Just let Console pick the localhost:xxxx endpoints for everything, boom, my "own" fake AWS.
fschuett 17 hours ago
Can it emulate billing too, i.e. "rand().powf(rand()) % downtime"?
BatchJob 11 hours ago
Headlines say written by agents, no humans.
No thanks.
jen20 13 hours ago
This looks great, I'm looking forward to using it!
That said, I don't like using Docker for things, and I run macOS on my desktop. Here's a patch that gets it all building on macOS [1] - though there's no good way to upstream it!
[1]: https://github.com/jen20/aws-emulator/tree/jen20/macos-build
aussieguy1234 14 hours ago
Personally, i've done away with all of these managed services and just run everything on NixOS.
Cloud provider neutral. Tear it up and tear it down with 100% reproducibility.
If I want to test it locally, I can boot it all up in a disposable VM.
mdaniel 9 hours ago
I would for sure read your nix implementation of an auto-scaling group, because I'd enjoy seeing how nix routes traffic to those new instances from your nix network load balancer
nunez 16 hours ago
annoying that it took AI happening for AWS to finally deliver on this though I'm glad they did
ironically localstack is solid enough to probably not need this for most things
swiftcoder 18 hours ago
I guess they didn't decide this was worth it till they needed it to train an LLM, huh? Not like everyone (inside and outside of AWS) has needed such a test harness for years...
dboreham 17 hours ago
After waiting for years for this kind of thing I ended up working around the issue by: using the real service. With Claude's help I have many projects now that test against live hosting providers using accounts maintained exclusively for testing. It ends up costing $50 or so a month in fees but well worthwhile for the assurance things really work.
tonymet 18 hours ago
A mere 20 years too late. Now it’s faster to have AI mock your APIs for you. AI has been a boon for test coverage.
Cthulhu_ 18 hours ago
Which is why they used AI to mock these APIs for you... too? I'd expect Amazon to feed it a lot of internal information so it has more to work with than anything someone else can cook up.
https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent...
tonymet 17 hours ago
it takes more time for my AI to learn their "emulator" . And I end up with far fewer dependencies on my own.
I've been prompting the agents to build everything using stdlib
jjice 17 hours ago
myworkaccount2 14 hours ago
If this does not kill you ec2 instances randomly its not emulating shit lol
andreadito 17 hours ago
Finally!
cxr 18 hours ago
No idea why there's so much of this lately, but there are way too many editorialized submission titles hitting the front page recently. Please stop doing this.
mh- 18 hours ago
Almost every large thread has upvoted comments that violate the comment guidelines, now, too. In both cases, not enough people flagging them, I guess.
varispeed 17 hours ago
Just a little bit more to keep you hooked. You should do your best to stay away from these parasites. Especially if they don't respect your country and your people by not paying the right amount of tax.