996 points by super_linear 9 days ago | 266 comments | View on ycombinator
CharlieDigital 9 days ago |
scriptsmith 8 days ago |
> 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...
wg0 9 days ago |
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.
morelandjs 9 days ago |
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!
Shakahs 9 days ago |
Waterluvian 9 days ago |
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.
super_linear 9 days ago |
jbmchuck 9 days ago |
fergie 8 days ago |
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.
MiroslavPokorny 8 days ago |
100GB !??!?!
schonfinkel 9 days ago |
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.
pprotas 8 days ago |
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.
resters 8 days ago |
yevmiyeci 9 days ago |
ChrisArchitect 9 days ago |
tptacek 9 days ago |
gateauxd 9 days ago |
OptionOfT 9 days ago |
Now doing the math I feel old.
JoshTriplett 8 days ago |
Spinifex (https://github.com/mulgadc/spinifex/) seems more promising than this, because its RunInstances actually launches VMs.
gosen 9 days ago |
mooreds 8 days ago |
If you have a product that has APIs and can be verified, anyone can copy the APIs and the features. By the way, you absolutely want to offer APIs so your product can be used by agents.
This means you need to compete on aspects other than features.
Just because you can emulate all the APIs doesn't mean you can build AWS.
Availability, reputation, performance, domain expertise, price: all of these become critical in a world where features can be copied.
jen20 8 days ago |
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
Thaxll 8 days ago |
dboreham 9 days ago |
paavohtl 9 days ago |
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...
OJFord 9 days ago |
> 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 9 days ago |
I’ve been having it build local mock APIs for any service that exposes its OpenAPI spec. Works like a charm.
stuff4ben 9 days ago |
dblock 7 days ago |
undefined 9 days ago |
aussieguy1234 8 days ago |
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.
bdparrish 7 days ago |
nodesocket 8 days ago |
ontouchstart 7 days ago |
Today I gave my underpowered Gemma 4 12B a try to bootstrap a docker-compose version of aws-emulator based on the official image and CLI documentation.
I didn’t go with full agentic or use the recommended skills. One of the reasons is that my context window is tiny compared to subscriptions. But I want to push the limits of local model spend more time reading the code and CoT. I feed the docs to the model, ask critical questions and give suggestions, copy and paste code to the editor and save (never edit the code myself.) Then I run the code with Makefile, feed the log back to the model. Most of the work is completely offline except for building the docker image and pushing to GitHub to trigger CI. This forced me and the LLM work in small increments. At the end of the day, I feed GitHub CI logs to the model and let LLM do the summary.
I leaned a lot about docker and AWS with this process and will do more experiments in the future.
It is a wonderful learning and research lab for systems architects.
toddyholiday 8 days ago |
noeleon 8 days ago |
ppcdeveloper 8 days ago |
tormeh 8 days ago |
thatslast 8 days ago |
chaz6 8 days ago |
cypherpunk666 8 days ago |
seshness 8 days ago |
hollowturtle 9 days ago |
weitzj 9 days ago |
Is AWS offering such a lock service for its costumers ? Multi regional?
asdfman123 9 days ago |
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.
undefined 9 days ago |
__natty__ 9 days ago |
dmtroyer 8 days ago |
ggcr 9 days ago |
[0] https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent...
forgotpwd16 9 days ago |
sebmellen 9 days ago |
microflash 9 days ago |
They can't help themselves, can they?
I'll stick with Floci and Testcontainers.
prescriptivist 8 days ago |
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.
firstSpeaker 8 days ago |
zmmmmm 8 days ago |
xlayn 8 days ago |
hbcdbff 9 days ago |
Claudeslop snuck in at the very end
enowapi 8 days ago |
tonymet 9 days ago |
InsidiousWombat 9 days ago |
tangotaylor 8 days ago |
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.
toenail 9 days ago |
4ndrewl 9 days ago |
I mean that's a job, but in many orgs it's been done by (cheaper) non-engineers (business analysts, QA professionals) for decades. So what does an engineer do?
enowapi 8 days ago |
ram_rattle 8 days ago |
BatchJob 8 days ago |
No thanks.
st3fan 8 days ago |
undefined 8 days ago |
BorisMelnik 9 days ago |
MisterMunchkin 8 days ago |
fschuett 9 days ago |
swiftcoder 9 days ago |
nunez 9 days ago |
ironically localstack is solid enough to probably not need this for most things
andreadito 9 days ago |
myworkaccount2 8 days ago |
undefined 9 days ago |
cxr 9 days ago |
Ploutosai 6 days ago |
allixsenos 8 days ago |
urios 3 days ago |
arbor-group 8 days ago |
dharmasthan 8 days ago |
ojhhhh 8 days ago |
urios 7 days ago |
lukisk 9 days ago |
ravivarmat 8 days ago |
gvieira 9 days ago |
toasteddonut 8 days ago |
kadharmfn 9 days ago |
WithHighProb 9 days ago |
ath3nd 9 days ago |
undefined 9 days ago |
undefined 9 days ago |
varispeed 9 days ago |
eloto333 8 days ago |
rfgplk 9 days ago |
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).
[0] https://floci.io/
[1] https://testcontainers.com/modules/floci/