This is an example of creating a function that runs as a cron job using the serverless schedule event. With the usage of the AWS Lambda function, it creates a record to the DynamoDB each and every 30 minutes.
This is an example of creating a function that runs as a cron job using the serverless
schedule event. With the usage of the
AWS Lambda function, it creates a record to the
DynamoDB each and every 30 minutes. For more information on the
schedule event check out the Serverless docs on schedule.
npm install to install all needed packages.
In order to deploy the service run:
for deploying with a specific
profile (located in
~/.aws/credentials) you can simply use the command:
AWS_PROFILE=YOUR_PROFILE_NAME sls deploy
for deploying to the specific stage, let's say
sls deploy --stage staging
The expected result should be similar to:
Serverless: Packaging service... Serverless: Excluding development dependencies... Serverless: Clearing previous build ruby layer build [ '2.1' ] Serverless: Installing gem using local bundler Serverless: Zipping the gemfiles to aws-ruby-cron-with-dynamodb/.serverless/ruby_layer/gemLayer.zip Serverless: Configuring Layer and GEM_PATH to the functions Serverless: Creating Stack... Serverless: Checking Stack create progress... ........ Serverless: Stack create finished... Serverless: Uploading CloudFormation file to S3... Serverless: Uploading artifacts... Serverless: Uploading service aws-ruby-cron-with-dynamodb.zip file to S3 (1.45 KB)... Serverless: Uploading service gemLayer.zip file to S3 (2.64 MB)... Serverless: Validating template... Serverless: Updating Stack... Serverless: Checking Stack update progress... ........................... Serverless: Stack update finished... Service Information service: aws-ruby-cron-with-dynamodb stage: dev region: us-east-1 stack: aws-ruby-cron-with-dynamodb-dev resources: 10 api keys: None endpoints: None functions: create-meal-order: aws-ruby-cron-with-dynamodb-dev-create-meal-order layers: gem: arn:aws:lambda:us-east-1:862403288926:layer:aws-ruby-cron-with-dynamodb-dev-ruby-bundle:1
serverless.yml in functions section
functions: create-meal-order: handler: src/handlers/create_meal_order/handler.run events: - schedule: rate(30 minutes)
You can setup your own schedule for cron. The default value is setup for 30 minutes. For more information about cron syntax, please check the next section.
cron(Minutes Hours Day-of-month Month Day-of-week Year)
All fields are required and time zone is UTC only.
|Minutes||0-59||, - * /|
|Hours||0-23||, - * /|
|Day-of-month||1-31||, - * ? / L W|
|Month||1-12 or JAN-DEC||, - * /|
|Day-of-week||1-7 or SUN-SAT||, - * ? / L #|
|Year||192199||, - * /|
Read the AWS cron expression syntax docs for more info on how to setup cron.
After the deployment, there is no much to do on your end.
To see the newly created records based on schedule time, you can either go to the created dynamoDB table within your region:
Important: The DynamoDB table name is a combination of service name and stage. For the
dev stage it will be:
or via cloudwatch logs:
The log retention is setup for 30 days. To change it simply change the value of this attribute in
||All code for the project.|
||Each Lambda function has its own folder.|
||Space for common, reusable pieces of code.|
||Adapter for communication with DynamoDB with the usage of AWS SDK for Ruby. Only used for creating new records.|
||The service object pattern is widely used within ruby/rails developers. A class that is responsible for doing only one thing. In our case is creating a meal order to the DynamoDB.|
For this example, there are two serverless plugins used:
|serverless-ruby-layer||For bundling ruby gems from
|serverless-export-env||For exporting the environment variables defined in
||It's a part of the AWS SDK for Ruby. Used for DynamoDB, in the case of this example - creation of the new record.|
||For generating fake meal order name.|
Please keep in mind, that the service will create a record each and every 30 minutes, you don't want to necessarily make it happened for the example project. To remove the service do:
And the stack will be removed from the AWS.
Latest commit b2f54ec on Sep 24, 2017