{"id":13497,"date":"2023-04-11T12:35:39","date_gmt":"2023-04-11T07:05:39","guid":{"rendered":"https:\/\/opstree.com\/blog\/\/?p=13497"},"modified":"2023-04-11T12:35:39","modified_gmt":"2023-04-11T07:05:39","slug":"lambda-function-trigger-enabled-using-code-pipeline","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2023\/04\/11\/lambda-function-trigger-enabled-using-code-pipeline\/","title":{"rendered":"Lambda Function Trigger Enabled Using Code Pipeline."},"content":{"rendered":"\n

Why are you doing a lambda function trigger enabled using pipeline?<\/strong><\/h4>\n\n\n\n

For the AWS service to invoke your function directly, you need to create a trigger using the Lambda console. A trigger is a resource you configure to allow another AWS service to invoke your function when certain events or conditions occur. Your function can have multiple triggers. Each trigger acts as a client invoking your function independently, and each event that Lambda passes to your function has data from only one trigger. By using the code pipeline we enabled our lambda function trigger when we needed it. <\/p>\n\n\n\n

What is the benefit?<\/strong><\/h4>\n\n\n\n

People don\u2019t need to add lambda function roles permission manually and don\u2019t need to enable trigger manually because, after policy gets attached to the particular roles then we can enable trigger and it happens by using pipeline whenever we need every time automation happens.<\/p>\n\n\n\n\n\n\n\n

My Personal Experience<\/strong><\/h4>\n\n\n\n

Whenever I got the task to enable trigger on lambda function so, every time I did it manually because in my client side server less computing works that\u2019s why there are so many  lambda functions. And, Every time I did it manually, I discussed this issue with my manager and after referring to some documentation on google I got a solution for that and I created the pipeline for that. <\/p>\n\n\n\n

First, we need to create a <\/strong>code pipeline and add the required stage In my code pipeline for the Lambda function trigger enabled I added six stages.<\/strong><\/p>\n\n\n\n


The first stage<\/strong> is required.
1] We need to create S3 bucket and in the bucket, we need to upload some objects.<\/p>\n\n\n\n

2] In my scenario, I took the source as a S3 bucket. Mentioned bucket name and also mention object name in the pipeline first stage.<\/p>\n\n\n\n

3] Upload the env file as an s3 object because, We have different types of environments so, according to the env file pipeline will work.<\/p>\n\n\n\n

4] Once we uploaded an env file as an object on s3 bucket the pipeline automatically triggered.<\/p>\n\n\n\n

5] For automatically triggered purpose I mentioned output artifacts as a keyword “latestEnv”<\/p>\n\n\n\n

The second stage required.<\/strong>
<\/p>\n\n\n\n

1] We already created the s3 bucket in the first stage, the same bucket we need to use to run the cloud formation template.<\/p>\n\n\n\n

2] In the second stage we need to upload one object as a source in the .zip file format and in the .zip file we have cloudformation template source code for permission on the lambda function roles.<\/p>\n\n\n\n

3] In my scenario, I mentioned output artifacts as a keyword “templates.zip” <\/p>\n\n\n\n

The third stage<\/strong> required<\/strong>. <\/p>\n\n\n\n

1] In the third stage we need an export environment for the lambda function because we have different types of lambda functions.<\/p>\n\n\n\n

2] Mentioned some requirement fields like lambda region, Input artifacts as a “latestEnv”, Function name.<\/p>\n\n\n\n

The fourth stage required.<\/strong><\/p>\n\n\n\n

1] In the fourth stage we need to create some tags for the lambda function because, sometimes after adding tags it will work for the user.<\/p>\n\n\n\n

2] Mentioned some requirement fields like lambda region, Input artifacts as a “latestEnv”, Function name.<\/p>\n\n\n\n

The fifth stage required<\/strong>. <\/p>\n\n\n\n

1] In the fifth stage we need to deploy cloud formation source code for creating a stack regarding assigning policy to particular lambda roles.<\/p>\n\n\n\n

2] For that we need a Mention action provider as a “AWS cloudformation”, region for stack creation, Input artifacts like templates.<\/p>\n\n\n\n

3] Action mode we need to take ” Create or update stack” because, everytime pipeline is run, according to the cloudformation template code it will create a new stack or update a new requirement.<\/p>\n\n\n\n

4] Stack Name we need Mention so according environment name stack will be create like “kinesis-#{export.envName}”<\/p>\n\n\n\n

5] template source code file name we need to mention for code create and update new stack like “kinesis-stream.yaml”<\/p>\n\n\n\n

6] I am using below source code with yaml format to run the stack. <\/p>\n\n\n\n

AWSTemplateFormatVersion: \"2010-09-09\"\nDescription: \"This template gives step function access to dsl-platform users.\"\nParameters:\n  EnvName:\n    Type: String\nResources:\n  SCMIMOSFNP:\n    Type: \"AWS::IAM::Policy\"\n    Properties:\n      PolicyName: \"kinesis-policy\"\n      PolicyDocument:\n        Version: \"2012-10-17\"\n        Statement:\n          - Effect: \"Allow\"\n            Action:\n              - \"kinesis:*\"\n            Resource: [\n              \"*\"\n            ]\n      Roles:\n        - !Sub \"rolename-${EnvName}.mumbai\"\n        - !Sub \"rolename-${EnvName}.mumbai\"\n<\/code><\/pre>\n\n\n\n
The sixth stage<\/strong> required<\/strong>. <\/p>\n\n\n\n
1] In that stage we need to create a one step function to enable the lambda function.<\/p>\n\n\n\n
2] I am used the below source code with for enable the lambda function.<\/p>\n\n\n\n
{\n    \"StartAt\": \"UpdateKinesisEventSourceMappingOne\",\n    \"States\": {\n      \"UpdateKinesisEventSourceMappingOne\": {\n        \"Type\": \"Task\",\n        \"Resource\": \"arn:aws:states:::aws-sdk:lambda:updateEventSourceMapping\",\n        \"Parameters\": {\n          \"FunctionName\": \"lambda-envname-mumbai\",\n          \"Uuid\": \"6d29bbfa-8221-47a3-9b01-f55a7d5894ee3\",\n          \"Enabled\": true\n        },\n        \"Next\": \"UpdateKinesisEventSourceMappingTwo\"\n      },\n      \"UpdateKinesisEventSourceMappingTwo\": {\n        \"Type\": \"Task\",\n        \"Resource\": \"arn:aws:states:::aws-sdk:lambda:updateEventSourceMapping\",\n        \"Parameters\": {\n          \"FunctionName\": \"lambda-envname-mumbai\",\n          \"Uuid\": \"38059928-9083-4c66-87cf-de3f1714567bf\",\n          \"Enabled\": true\n        },\n        \"End\": true\n      }\n    }\n  }\n<\/code><\/pre>\n\n\n\n
3] We need to mention Action name as like “Enable-Kinesis-Stream”, Action provider as a AWS Step Function, Region of step function and Input artifacts “latestEnv”<\/p>\n\n\n\n
4] State machine ARN we need to mention that we already created. <\/p>\n\n\n\n
Conclusion<\/strong> <\/p>\n\n\n\n
In <\/strong>conclusion, it is easy to enable the lambda function by using code pipeline every time just upload an env file on a bucket and it triggers automatically. We are not doing this manually because automation reduces the time and above steps we are using each and every lambda function enabled. <\/p>\n\n\n\n
References<\/strong><\/p>\n\n\n\n
https:\/\/repost.aws\/knowledge-center\/cloudformation-attach-managed-policy<\/a> https:\/\/docs.aws.amazon.com\/step-functions\/latest\/dg\/connect-lambda.html<\/a>  <\/p>\n\n\n\n
Blog Pundits: Bhupender Rawat<\/a> and Sandeep Rawat<\/a><\/strong><\/p>\n\n\n\n
OpsTree<\/a> is an End-to-End DevOps Solution Provider.<\/strong><\/p>\n\n\n\n
\n
Contact Us<\/a><\/div>\n<\/div>\n\n\n\n
Connect with Us<\/strong><\/p>\n\n\n\n