OpenRules Decision Manager allows business analysts to deploy their decision models as AWS Lambda decision services without any coding. They can do it even directly from their local installation by one click on the provided batch file “deployAWS.bat“!
What is actually required for AWS Lambda deployment? We assume that you already have an active AWS account and created your security credentials (access key ID and secret access key) which should not be shared with anybody. Then you should define your AWS deployment settings in the provided file “settingsAWS.bat“. Here are the required settings:
Then (assuming you already built the decision model using “build.bat”) you simply click on the standard file “deployAWS.bat“. The model will be deployed and the console log will show the invoke URL for the deployed decision service (highlighted in the following example):
You may copy this URL and use it with POSTMAN or your own Java test-program as described in this tutorial.
But OpenRules goes even further! To simplify testing and to demonstrate how to invoke the deployed decision service, it generates the file “testAWS.bat” that already includes the above invoke URL. When you click on this file, it remotely executes all test cases defined in the Excel file “Test.xls” against just deployed AWS Lambda!
Additional AWS Settings
Optionally, you may use additional settings to specify more details about your AWS deployment preferences. For example, by default we use the word “test” (inside the invoke URL) as your deployment stage. But you may redefine it as “dev”, “prod”, or any similar word using this setting:
By default your deployed service will be publicly accessible, but it is possible to make it private.
Usually people keep their AWS Credentials (access key ID and secret access key) in the default file ~/.aws/credentials. However, alternatively you may define them directly in the file “settingAWS.bat”:
If you decide to undeploy your decision service and clean up your AWS, just click on the file “undeployAWS.bat“.