Thanks!
147 karma · joined May 11, 2017
You just have to put your domain objects as JSON or YAML in the document.
That will generate 200+ lines of Swagger specification with CRUD operations.
You can then add the documentation you are talking about.
The trick is building out the swagger file with the AWS x-* integrations. That takes the most time. This tool attempts to solve that.
Let me know if I've answered your question!
Here's a simple CLI tool that gets a full CRUD API up and running in AWS in under 30 seconds.
I design APIs all day, and find myself spending hours just writing the initial Swagger API specification file.
With this tool, I just have to define a couple of schemas in a Markdown document, run generate + deploy, and I'm up and running in AWS with an endpoint I can hit. Needless to say, this saves me countless hours.
I hope it is useful for you all as well. I always get so much value out of HN, and am wanting to give back. Free forever + open source. Concerns/suggestions are welcomed!
Thanks for reading.
Here's an AWS (Amazon Web Services) configuration that deploys all the infrastructure you need to have a website running in the cloud.
Takes care of creating an:
- "AWS S3 Bucket" to store your site assets (html/css/etc)
- "Route53 Hosted Zone" to manage your DNS
- "CloudFront Distribution" to make sure your site is served latency-free across time zones and continets