HN Simulatornew | past | comments | lists | submit | fromlogin

Look at AWS Copilot CLI https://aws.github.io/copilot-cli/docs/concepts/environments... and the repo https://github.com/aws/copilot-cli/.

Look at Floci (I have no affiliation) https://floci.io/ the blog https://floci.io/chronicle/ and the labs https://floci.io/labs/

Do you agree that there's a polish here that shows a team's pride in that work that is clearly missing in this work?

    > ...especially when engaging with (presumably) actual AWS employees in this thread replying to you
??? You and I are the customers. What even is this statement? Are AWS employees our benefactors? Wow. I do not care if their feelings are hurt because this "product" clearly shows a lack of polish and love.

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.

https://github.com/aws/api-models-aws

https://github.com/smithy-lang/smithy


Not internal. Open sourced: https://github.com/aws/api-models-aws

Repo has 29,684 Commits!

Code frequency pages shows:

"There are too many commits to generate this graph."

https://github.com/aws/aws-emulator/graphs/code-frequency


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.

Sort of. The releases page leads you to a massive blob of json with all the compatibility tests and scores.

Edit: The current one: https://github.com/aws/aws-emulator/releases/download/v1.0.3...

You can get some idea if the product name is unique enough with and looking at each of the related test scores.


Yep, I see container support is marked coming soon: https://github.com/aws/aws-lambda-roadmap/issues/103 This is your killer feature!

Not familiar enough about GCP internal, but AWS prices are way higher than what's quoted in the article. You'll get billed for bandwidth, should you want any logs of your control plane you'll pay them at a premium so high* it will dwarf the cluster price and machine price combined. And for ~$70/month, you get the cluster API, not the EC2 compute required for worker nodes.

* Because vended logs to s3 are not supported (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS..., https://github.com/aws/containers-roadmap/issues/1141)


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: