On April 5 th , 2016 Amazon announced an update to its API Management service known as Amazon API Gateway. In this update, Amazon API Gateway now supports a direct way of importing Swagger 2.0 definitions.
Swagger has been a supported API Specification for Amazon’s API Gateway since the service was launched. But, developers previously needed to use the Swagger importer tool to import Swagger definitions into the API Gateway. The Swagger importer tool is available on Github and provides a command line tool experience.
Going forward, developers can use the AWS Management Console, Command Line Interface (CLI) or SDK. While in the AWS Management Console, developers have the ability to:
- Create a new API
- Clone from existing API
- Import from Swagger
- View an Example API
As of January 1 st , the Swagger specification has been donated to the Open API Initiative (OAI) . The intent of the OAI is to bring together like-minded organizations interested in standardizing how REST APIs are described. The OAI is operating in an open governance structure under the Linux Foundation and has many industry leaders as members, including Google, Apigee, Atlassian, IBM, Intuit, Microsoft and PayPal to name a few.
Swagger is not the only API specification that is supported in Amazon API Gateway. The service also supports a competing specification called RAML . At the time of this writing, Amazon has indicated that “customers using RAML definitions should continue to use aws-apigateway-importer for the time being.” RAML is an open workgroup led by Mulesoft and has support from other members including Cisco (a Mulesoft investor), VMWare and Akana.
转载本站任何文章请注明：转载至神刀安全网，谢谢神刀安全网 » Amazon API Gateway Now Supports Swagger Definition Import