Over the last few months, the SwaggerHub team has been on a roadshow, showcasing a new integration with Amazon’s API Gateway and Lambda.
The integration lets organizations expose their APIs on the Amazon API Gateway for better consumption and security, quickly and automatically. Serverless deployment is also taken care of, with SwaggerHub auto-generating the building blocks of your API code in Amazon Lambda from the Swagger definition in SwaggerHub.
Earlier this month, we had the chance to showcase the integration at the AWS re:Invent Conference in Las Vegas. And in December, hosted a workshop at APIDays Paris — Creating an API on Amazon Lambda with Swagger Tools — where experts from the SwaggerHub team demonstrated the seamless workflow of building, documenting, and deploying your API with Swagger and Amazon Lambda.
We recently hosted a free online webinar, walking through the advantages of going serverless, while providing a hands-on demonstration of the API Gateway integrations offered in SwaggerHub.
You can watch the webinar below. We’ve also recapped some of the key takeaways from this hour-long session to help you find the information that’s most valuable to you.
Swagger and the importance of a RESTful contract [1:50]
“Swagger allows users to design, build, and document APIs. Swagger lets you define your API’s contract and tell API end consumers — as well as the people developing the API from the backend — what the API is supposed to do. Swagger keeps all of these various stakeholders, technology stacks, and end users in sync and unifies them in one language.”
Introduction to serverless architecture [9:35]
“Serverless architectures refer to applications that significantly depend on third-party services or on custom code that’s run in ephemeral containers (Function as a Service or “FaaS”), the best known vender host of which currently is AWS Lambda.”
What serverless could do for your APIs [12:00]
“Before serverless, developers wouldn’t just have to think about the business logic, but would also need to worry about what server framework they would need, and spend time, money and effort to build it themselves. In a serverless implementation, the business logic is pushed out to a vendor and there’s no additional development needed to support the business logic.”
Introduction to Amazon API Gateway [16:00]
“The AWS API Gateway acts as the front door for all of your APIs. It handles accepting, processing, and orchestrating API requests and maps requests to the appropriate backend — either to a remote server (proxy) or to a specific Lambda function.”
Swagger and the API Gateaway [20:25]
“There are two approaches to deploying your API on API Gateway — either import a Swagger file from your local machine, or building the API on the AWS console itself. There are advantages and disadvantages to both approaches.”
How SwaggerHub Bridges the Gap Between Swagger, the API Gateway and Lambda [26:30]
“The Swagger team conceptualized a method in which you can push API files from SwaggerHub — a complete API development platform for Swagger APIs — to the AWS API Gateway, without any manual plumbing, and orchestrate all of the operations involved in deploying your APIs on API Gateway from one source of truth.”
See it in action! Demo of the Amazon API Gateway Integration [29:00]