AWS Compute Blog
Category: Amazon API Gateway
Monetize your APIs in AWS Marketplace using API Gateway
Shiva Krishnamurthy, Sr. Product Manager Amazon API Gateway helps you quickly build highly scalable, secure, and robust APIs. Today, we are announcing an integration of API Gateway with AWS Marketplace. You can now easily monetize your APIs built with API Gateway, market them directly to AWS customers, and reuse AWS bill calculation and collection mechanisms. […]
Generate Your Own API Gateway Developer Portal
Shiva Krishnamurthy, Sr. Product Manager Amazon API Gateway helps you quickly build highly scalable, secure, and robust APIs. Developers who want to consume your API to build web, mobile, or other types of apps need a site where they can learn about the API, acquire access, and manage their consumption. You can do this by […]
Introducing Simplified Serverless Application Deployment and Management
Orr Weinstein, Sr. Product Manager, AWS Lambda Today, AWS Lambda launched the AWS Serverless Application Model (AWS SAM); a new specification that makes it easier than ever to manage and deploy serverless applications on AWS. With AWS SAM, customers can now express Lambda functions, Amazon API Gateway APIs, and Amazon DynamoDB tables using simplified syntax that is […]
Binary Support for API Integrations with Amazon API Gateway
Masuo Gates, Software Development Manager A year ago, the Microservices without the Servers post showed how Lambda can be used for creating image thumbnails. This required the client to Base64 encode the binary image file before calling the image conversion API as well as Base64 decode the response before it could be rendered. With the […]
Build Serverless Applications in AWS Mobile Hub with New Cloud Logic and User Sign-in Features
Last month, we showed you how to power a mobile back end using a serverless stack, with your business logic in AWS Lambda and the resulting cloud APIs exposed to your app through Amazon API Gateway. This pattern enables you to create and test mobile cloud APIs backed by business logic functions you develop, all […]
Going Serverless: Migrating an Express Application to Amazon API Gateway and AWS Lambda
Brett Andrews Software Development Engineer Amazon API Gateway recently released three new features that simplify the process of forwarding HTTP requests to your integration endpoint: greedy path variables, the ANY method, and proxy integration types. With this new functionality, it becomes incredibly easy to run HTTP applications in a serverless environment by leveraging the aws-serverless-express […]
Easier integration with AWS Lambda and Amazon API Gateway
This week, Amazon API Gateway announced three new features that make it easier for you to leverage API Gateway and AWS Lambda to build your serverless applications. First, we now support catch-all path variables. You can define routes such as /store/{proxy+}, where the + symbol tells API Gateway to intercept all requests to the /store/* […]
Techniques and Tools for Better Serverless API Logging with Amazon API Gateway and AWS Lambda
Ryan Green @ryangtweets Software Development Engineer, API Gateway Developing, testing, and operating Serverless APIs using Amazon API Gateway and AWS Lambda can be made much easier with built-in support for Amazon CloudWatch Logs. In Lambda functions, you can use log statements to send log events to CloudWatch log streams, and API Gateway automatically submits log […]
Migrating a Native JAVA REST API to a Serverless Architecture with the Lambada Framework for AWS
NOTE: Newer guidance on the topic of migrating Java based applications to AWS Lambda can be found here: Replatforming Java based applications to AWS Lambda. This is a guest post by Çağatay Gürtürk, the creator of the Lambada framework Serverless computing has become a hot topics since AWS Lambda and Amazon API Gateway started to […]
Redirection in a Serverless API with AWS Lambda and Amazon API Gateway
Ronald Widha @ronaldwidha Partner Solutions Architect Redirection is neither a success nor an error response. You return redirection when the requested resource resides either temporarily or permanently under a different URI. The client needs to issue subsequent calls to the new location in order to retrieve the requested resource. Even though you typically see 302 […]