In this video tutorial, we’ll cover CloudWatch Log Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll build a Jets project from scratch with the log_event declaration. We’ll deploy the application and test the CloudWatch Log event. We’ll show you how simple it is to get started with Ruby on Jets and CloudWatch Log Events.
In this video tutorial, we’ll cover DynamoDB Stream Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll build a Jets project from scratch with the dynamodb_event declaration. We’ll deploy the application and test the DynamoDB event. We’ll show you how simple it is to get started with Ruby on Jets and DynamoDB Stream Events.
In this video tutorial, we’ll cover Kinesis Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll build a Jets project from scratch with the kinesis_event declaration. We’ll deploy the application and test the Kinesis event. We’ll show you how simple it is to get started with Ruby on Jets and Kinesis Events.
In this video tutorial, we’ll cover SNS Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll explain what SNS Event are. Then we’ll build a Jets project from scratch with the sns_event declaration. We’ll deploy the application and test the SNS event. We’ll show you how simple it is to get started with Ruby on Jets and SNS Events.
In this video tutorial, we’ll cover SQS Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll build a Jets project from scratch with the sqs_event declaration. Essentially creating an autoscaling worker processing tier. We’ll deploy the application and test the SQS event. We’ll show you how simple it is to get started with Ruby on Jets and SQS Events.
In this video tutorial, we’ll cover S3 Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll explain what S3 Events are. We’ll discuss the design approach that Jets took by adding an SNS topic to the flow. Then we’ll build a Jets project from scratch with the s3_event declaration. We’ll deploy the application and test the s3 event. We’ll show you how simple it is to get started with Ruby on Jets and S3 Events.
In this video tutorial, we’ll cover IoT Events and how to connect them up to AWS Lambda Functions with Ruby on Jets. We’ll explain what IoT Events are and then build a Jets project from scratch and add a Jets iot_event declaration. We’ll use a real physical AWS IoT Button and have the button send a text message to a phone. We’ll show you how simple it is to get started with Jets and IoT Event rules.
In this video, we’ll create several hello world examples with Jets code. We’ll create a simple function, controller function, and a job function. We’ll also walk through the Lambda console and test each one by invoking it. This post is a part of an introductory series for people who are new to AWS Lambda and Serverless.
In this video, we’ll walk through creating a CloudWatch Event Rule with the CloudWatch console. Simply getting familiar with the CloudWatch console is a really good way to learn how simple it is for those who are new to CloudWatch and are trying it out for the first time. We talk about how a Jets Job essentially creates the CloudWatch even rule for you. This post is a part of an introductory series for people who are new to CloudWatch, AWS Lambda, and Serverless.
In this video, we’ll walk through creating an API Gateway REST API from scratch manually. Just getting familiar with the API Gateway console is an excellent way to learn how simple it is for those who are new to API Gateway and trying it out for the first time. We talk a little bit about Jets and how config/routes.rb essentially maps to API Gateway resources, but the focus is really on API Gateway console. This simple exercise will help understand what Jets does for you. This post is a part of an introductory series for people who are new to API Gateway and Serverless.
In this video, we’ll walk through creating a Lambda Function with the Lambda console. Simply getting familiar with the AWS Lambda console is an excellent way to learn how simple AWS Lambda is for those who are new to AWS Lambda and trying it out for the first time. We do not talk much about Jets in this video, but this simple Lambda Console exercise will help understand what Jets does for you. This post is a part of an introductory series for people who are new to AWS Lambda and Serverless.
This post will detail the steps to get a serverless slack command running on AWS Lambda using the Jets Serverless Ruby framework. We’ll make something fun: a command that takes in a URL, scrapes all the images on the page, filters the images using AWS image recognition, and posts the filtered images to the current slack channel. For example:
In this blog post, I’ll cover how to build a simple API service on AWS Lambda with the Jets Ruby Serverless Framework.
A great use case for AWS Lambda is running Cron Jobs. Instead of setting up a special one-off Cron server to run a simple task, we can just run the task on serverless nowadays. In this blog post, we’ll go over how to build a simple Cron Job with Jets, the Ruby Serverless Framework. As a useful practical example, we’ll create a job that backs up route53 records. This is quite handy when if you ever need it!
I created Jets, the Ruby Serverless Framework, over a year ago – way before AWS officially released Ruby Support for AWS Lambda. Although it would have been nice to have official Ruby support back then, it was all for the best because I was forced to learn a lot about AWS Lambda and Serverless in general – its strengths, weaknesses, and the challenges that one typically encounters.
In this post and video, we’ll cover how to deploy a Rails application to AWS Lambda Serverless in a few minutes. With Jets Afterburner, you don’t have to make any changes to your Rails application to get it on AWS Lambda. 🎉
AWS released A1 Instance Types at re:Invent 2018. Honestly, I didn’t think much about this announcement. I would see the ads for them when logging into the AWS console, and folks seem to be excited about them. So I started digging into what this whole A1 Instance type was all about. It didn’t take long to realize why it is a big deal. The A1 Instances will mean more server choices. More choices mean more competition, which is always better for consumers. This means faster, less expensive, and even better servers for us.
Jets, a Ruby Serverless Framework, makes use of API Gateway Binary Support to make uploading images and files from AWS Lambda a straightforward task. We’ll cover how to upload images or any file with Jets and Carrierwave in this tutorial guide. Note, please use Jets v1.3.1 and above for this tutorial guide as the jets new generator was updated for it. Here’s the Live Demo of this tutorial. The full source code is on Github: tongueroo/jets-example-upload.
Ever since AWS released official Ruby support for AWS Lambda on Nov 29 at re:Invent, I’ve been super excited about switching Jets over to the official AWS version of Ruby. Happy to say that Jets is now on the official AWS Ruby runtime. Knew it was going to be interesting to learn about AWS Lambda Custom Runtimes and Lambda Layers as part of this Jets update.
This video tutorial demos the jets delete command. Since all the infrastructure is codified, deleting a Jets application is a straightforward process. What’s more interesting is that it is also easy to recreate the entire environment.
jets delete
For more info on the jets delete command, refer to its CLI reference.
Update 12/21/2018: An improved way to run Rails on AWS Lambda is now supported that is effortless. This blog post covers it: Jets Afterburner: Serverless Rails on AWS Lambda in 5 Minutes. It is also documented here: Jets Rails Support. It is recommended you use Jets Afterburner for simple cases.
In the previous post: Jets Mega Mode: Run Rails on AWS Lambda, I covered how to get Rails running on AWS Lambda with Jets. In this video tutorial, I show you how to use the --submodule option for the same command we used to set things up previously: jets import:rails. Example:
jets import:rails http://github.com/tongueroo/demo-rails.git --submodule
Importing the Rails application as a submodule allows you to keep the Rails project in a separate repo. This allows you to manage the Rails project with a separate history and sync it with a Jets project when you want to. This is a useful setup if you are testing Jets Mega Mode Rails Support for an extended period of time.
Update 12/21/2018: An improved way to run Rails on AWS Lambda is now supported that is effortless. This blog post covers it: Jets Afterburner: Serverless Rails on AWS Lambda in 5 Minutes. It is also documented here: Jets Rails Support. It is recommended you use Jets Afterburner for simple cases.
Jets allows you to run Rails applications on AWS Lambda via Mega Mode. The name reminds me of a few things:
Mega Mode combines a Jets app and a Rack app together to allow you to run Rails on AWS Lambda with little effort. The docs for Rails Support are on the Ruby On Jets site. Here’s a Live Mega Mode Demo. We’ll go through an example of Mega Mode and get a Rails application running on AWS Lambda in this post.
Jets supports writing simple AWS Lambda functions with Ruby. You define them in the app/functions folder. A function looks like this:
app/functions/simple.rb:
def lambda_handler(event:, context:)
puts "hello world"
end
In the previous post, AWS Config was introduced. We talked about how it can be used to obtain continuous compliance with your AWS account. In this post, we’ll implement a working example solution.
AWS is one of the greatest things since sliced bread. It empowers engineers to get things done quickly by enabling them to take control of the steering wheel and drive. With a simple AWS account, engineers can create resources, update security groups, and deploy their applications in rapid-fire fashion. The ease and power of AWS might make it seem like a security nightmare, but it’s actually the opposite. AWS provides the tools and controls to ensure everyone is following best practices, allows to you achieve a hardened security posture, and take compliance to a level that was never even thought possible before AWS: continuously.
subscribe to Blog via RSS