upvote

points

by dogleash18 hours ago |
comments
upvoteby ke4qqq18 hours ago|
next
[-]
I don’t take it personally; I realize you don’t know me, and a sentence on HN isn’t much of a guarantee.

That said, it’s been announced publicly here: https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent...

Additionally Swami, our SVP of AI blogged about it separately and our CTO is tweeting about it - which is more than a number of products get in terms of coverage.

reply
upvoteby dogleash17 hours ago|
parent|
[-]
I didn't mean announcing the tool, I meant an announcement committing to the maintenance/support that users like the GP poster were looking for. My bad on describing that clearly, I'm gonna get clowned on in the comments and I'm not turning this around.
reply
upvoteby iceboundrock16 hours ago|
parent|
next
[-]
It has its official document page: https://docs.aws.amazon.com/emulator/latest/userguide/gettin... and it lives in https://github.com/aws/ org. I think AWS is pretty committed.
reply
upvoteby ke4qqq17 hours ago|
parent|
prev|
[-]
I understood what you meant. I was just trying to add evidence to support my claim that it was a real product and would be maintained. And yeah, votes on comments can be fickle.
reply
upvoteby Eridrus17 hours ago|
parent|
[-]
I think one thing that concerns many people is that this looks like AI slop, which it clearly is according to the blog post.

I think this is a super interesting direction, but how can we trust the accuracy of this simulator? Agentic loops are great and all, but they can still miss plenty of things.

Or maybe a better question: where is the accuracy of this simulator going to be guaranteed enough that we should trust it?

reply
upvoteby NewsaHackO16 hours ago|
parent|
next
[-]
To me, something like this is actually what vibe coding thrives the best at; tight, looped, easily verifiable, test-driven dev work. In fact, this is probably the field it can do with little or no intervention, if you're willing to waste tokens.
reply
upvoteby Eridrus16 hours ago|
parent|
[-]
Is it? How is it verified that this catches all the potential edge cases of interacting with AWS? Or is handling all the edge cases of AWS not in scope?

Like, what am I actually getting here? Is it just happy path operations being correct here?

reply
upvoteby cherioo16 hours ago|
parent|
[-]
For real edge cases, it will be like any other software. Users get to be the guinea pigs and report bugs as they find them.

Hopefully AWS has had enough internal guinea pigs before they published this!

reply
upvoteby ontouchstart15 hours ago|
parent|
[-]
In the near future, every case will be a real edge case and every one will be a guinea pig.

The border between AWS and AWS emulator becomes fuzzy. And the users of AWS will be agents as well. A completely offline emulator will save a lot of resources and could be a great training ground for more focused (offline) models.

reply
upvoteby hluska15 hours ago|
parent|
prev|
[-]
Back in the day, we assumed that when a major company open sourced code, that code would have problems. We invented all these things like ‘issues’ to deal with this.
reply
upvoteby Cthulhu_18 hours ago|
prev|
[-]
https://www.aboutamazon.com/news/aws/how-autonomous-ai-agent... ?
reply
upvoteby 18 hours ago|
parent|
next
[-]
deleted
reply
upvoteby forgotpwd1617 hours ago|
parent|
prev|
[-]
GP statement still stands, actually being strengthened. This blog post doesn't even mention nor seems to care about maintainability or long-term support or anything that users will care about. Only talks about how cool the team is and how amazing they're at using AI, multi-agent workflows, and this kind of bs. It's funny how author talks so much about testing when they themselves also boast how they haven't written or reviewed any of the code.
reply
upvoteby CharlieDigital16 hours ago|
parent|
[-]
Also doesn't mention any benchmarks or compatibility matrix.

This feels like table stakes for an emulator.

reply