New serverless pattern - EventBridge Scheduler to invoke Step Functions to get the List of Inactive Lambda functions #2533
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcojahn
requested changes
Dec 30, 2024
| @@ -0,0 +1,85 @@ | |||
| # EventBridge scheduler to invoke step function to get the list of inactive lambda functions | |||
There was a problem hiding this comment.
Suggested change
| # EventBridge scheduler to invoke step function to get the list of inactive lambda functions | |
| # Amazon EventBridge Scheduler to invoke an AWS Step Function to get the list of inactive AWS Lambda functions |
| @@ -0,0 +1,85 @@ | |||
| # EventBridge scheduler to invoke step function to get the list of inactive lambda functions | |||
|
|
|||
| This pattern will create a one time schedule in EventBridge scheduler with state machine as target & invoke the lambda ListFunctions & GetFunction API using the SDK integration in step functions and publish the list of inactive functions to SNS Topic. | |||
There was a problem hiding this comment.
Suggested change
| This pattern will create a one time schedule in EventBridge scheduler with state machine as target & invoke the lambda ListFunctions & GetFunction API using the SDK integration in step functions and publish the list of inactive functions to SNS Topic. | |
| This pattern will create an Amazon EventBridge Scheduler rule targeting an AWS Step Function state machine. The Step Function invokes an AWS Lambda using `ListFunctions` and `GetFunctions` API using the SDK integration in Step Functions. It publishes the list of inactive functions to an Amazon SNS Topic. |
|
|
||
| 6. Note the outputs from the SAM deployment process. These contain the resource names and/or ARNs which are used for testing. | ||
|
|
||
| 7. **Imp** : Once the SNS topic & subscription is created, verify the subscription by clicking the 'Confirm subscription' link received on your email. |
There was a problem hiding this comment.
Suggested change
| 7. **Imp** : Once the SNS topic & subscription is created, verify the subscription by clicking the 'Confirm subscription' link received on your email. | |
| 7. **Important** : Once the SNS topic & subscription is created, verify the subscription by clicking the 'Confirm subscription' link received on your email. |
"Imp" means "important"?
|
|
||
| ## How it works | ||
|
|
||
| 1. When the stack is deployed it creates a state machine, an eventBridge scheduler,a SNS topic with email subscription, a Lambda Function and required IAM roles. |
There was a problem hiding this comment.
Suggested change
| 1. When the stack is deployed it creates a state machine, an eventBridge scheduler,a SNS topic with email subscription, a Lambda Function and required IAM roles. | |
| 1. When the stack is deployed it creates a state machine, an Event Bridge Scheduler, an SNS topic with email subscription, a Lambda function and required IAM roles. |
|
|
||
| 1. When the stack is deployed it creates a state machine, an eventBridge scheduler,a SNS topic with email subscription, a Lambda Function and required IAM roles. | ||
|
|
||
| 2. Event Bridge scheduler invokes the State machine on defined schedule, Default schedule invokes the state machine daily at 00::00 UTC with the below mentioned payload. Modify the schedule as per your requirement. |
There was a problem hiding this comment.
Suggested change
| 2. Event Bridge scheduler invokes the State machine on defined schedule, Default schedule invokes the state machine daily at 00::00 UTC with the below mentioned payload. Modify the schedule as per your requirement. | |
| 2. Event Bridge Scheduler invokes the state machine with a defined schedule. The default schedule invokes the state machine daily at 00:00 UTC with the below mentioned payload. Modify the schedule as per your requirement. |
|
|
||
| 3) In state machine, the 1st step is to get the list of all lambda functions in the current region using the ListFunctions API, ListFunctions API is called multiple times as it returns max 50 functions list in a single API call along with NextMarker pagination parameter. Using NextMarker token state machine retrieves list of all the function ARN's. | ||
|
|
||
| 4) Lambda Invoke Combine data Step : This a custom lambda function python script to create a combined json array of Lambda function ARN's retrieved in step 1. |
There was a problem hiding this comment.
Suggested change
| 4) Lambda Invoke Combine data Step : This a custom lambda function python script to create a combined json array of Lambda function ARN's retrieved in step 1. | |
| 4) Lambda Invoke Combine data Step : This a custom Lambda function python script to create a combined JSON array of Lambda function ARNs retrieved in step 1. |
|
|
||
| 4) Lambda Invoke Combine data Step : This a custom lambda function python script to create a combined json array of Lambda function ARN's retrieved in step 1. | ||
|
|
||
| 5) Map - Loop Functions State : In this state, GetFunction API is called for each Lambda ARN taken as input from previous step & status of each function is checked and appended to the output. |
There was a problem hiding this comment.
Suggested change
| 5) Map - Loop Functions State : In this state, GetFunction API is called for each Lambda ARN taken as input from previous step & status of each function is checked and appended to the output. | |
| 5) Map - loop functions state: In this state, the GetFunction API is called for each Lambda ARN taken as input from the previous step, and the status of each function is checked and appended to the output. |
|
|
||
| 5) Map - Loop Functions State : In this state, GetFunction API is called for each Lambda ARN taken as input from previous step & status of each function is checked and appended to the output. | ||
|
|
||
| 6) Filter Inactive Functions State : This filters out the Active functions from the Json array and passes only the Inactive functions list to the next step. |
There was a problem hiding this comment.
Suggested change
| 6) Filter Inactive Functions State : This filters out the Active functions from the Json array and passes only the Inactive functions list to the next step. | |
| 6) Filter inactive functions state: This filters out the active functions from the JSON array and passes only the list of inactive functions to the next step. |
|
|
||
| 6) Filter Inactive Functions State : This filters out the Active functions from the Json array and passes only the Inactive functions list to the next step. | ||
|
|
||
| 7) SNS Publish : List of Inactive functions is published to the SNS Topic. |
There was a problem hiding this comment.
Suggested change
| 7) SNS Publish : List of Inactive functions is published to the SNS Topic. | |
| 7) SNS publish : List of inactive functions is published to the SNS Topic. |
| 2. Also, you have to manually delete any schedules you created if required. | ||
|
|
||
| ---- | ||
| Copyright 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved. |
There was a problem hiding this comment.
Suggested change
| Copyright 2022 Amazon.com, Inc. or its affiliates. All Rights Reserved. | |
| Copyright 2024 Amazon.com, Inc. or its affiliates. All Rights Reserved. |
|
Hello @sahilk225579, I've requested a few changes. After applying the PR can be processed further. |
|
added all the changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
added all the required SAM template, lambda function code & state machine defination.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.