In the previous blog, we created the Lambda function automaticServiceCreation that provisions key AWS services. In this post, we’ll focus on how to trigger this function automatically or manually to ensure seamless deployment and management of your services. We will explore different methods to invoke this function, including using AWS CLI, AWS SDK, AWS CodePipeline, and more.
The following diagram illustrates Automatic deployment with AWS Lambda:
Triggering Lambda with AWS CLI
The simplest way to trigger your Lambda function is using the AWS CLI.
1. Install AWS CLI (if not already installed):
Download and install AWS CLI from here.
Configure the CLI with aws configure.
2. Invoke the Lambda Function: To manually trigger the automaticServiceCreation function, run this command:
aws lambda invoke --function-name "automaticServiceCreation" outputfile.txt
This will trigger the Lambda function and store the output in the outputfile.txt.
Triggering Lambda with AWS SDK
If you’re invoking the Lambda function programmatically from another application or Lambda function, you can use the AWS SDK for Node.js.
Here’s how to invoke it from another Lambda function:
const AWS = require('aws-sdk');
const lambda = new AWS.Lambda();
const params = {
FunctionName: 'automaticServiceCreation', // Lambda function name
InvocationType: 'Event', // Asynchronous invocation
};
lambda.invoke(params, (error, data) => {
if (error) {
console.error('Error invoking Lambda:', error);
} else {
console.log('Lambda invoked successfully:', data);
}
});
This will invoke the Lambda function asynchronously, meaning it won’t block the calling process.
Automating Deployment with AWS CodePipeline
To automate the deployment and trigger the Lambda function as part of a continuous integration/continuous delivery (CI/CD) pipeline, you can integrate AWS Lambda with AWS CodePipeline.
1. Create a New Pipeline:
Go to AWS CodePipeline and create a new pipeline.
Set up a Source Stage (e.g., GitHub or CodeCommit).
Add a Build Stage using AWS CodeBuild (optional for testing or packaging).
In the Deploy Stage, add a Lambda Action that invokes the automaticServiceCreation function.
2. Configure Trigger:
Set the pipeline to trigger whenever a change is made to your source repository.
Using AWS EventBridge for Triggering
If you want to trigger the automaticServiceCreation Lambda function based on specific events, you can use AWS EventBridge.
For instance, you can trigger the Lambda when new code is committed to a repository or a custom event is generated:
{
"Source": ["aws.codecommit"],
"DetailType": ["CodeCommit Repository State Change"],
"Detail": {
"event": "push"
},
"Targets": [
{
"Arn": "arn:aws:lambda:your-region:your-account-id:function:automaticServiceCreation",
"Id": "LambdaTarget"
}
]
}
This rule will automatically trigger the Lambda function whenever there is a push event in the CodeCommit repository.
Manual Trigger via the AWS Console
If you prefer to manually invoke the Lambda function, you can do so directly from the AWS Lambda Console:
1. Open the Lambda Console.
2. Select the "automaticServiceCreation" function from the list.
3. Click on Test.
4. Configure the event (optional), then click Invoke.
---
Conclusion
In this two-part series, we’ve covered the entire process of creating and triggering an AWS Lambda function for automated service creation. From setting up the function, writing the code, and deploying it, to invoking the function using AWS CLI, SDK, CodePipeline, and EventBridge, you now have a comprehensive guide to automate your cloud service deployments using Lambda. This approach streamlines your deployment processes, making it easier to manage cloud infrastructure as part of your CI/CD pipeline
Tags
Cloud Computing