chore: update lambda attacks to use the steadybit failure-lambda

actions/com.steadybit.extension_aws.lambda.denylist/summary.mdx

@@ -1,14 +1,14 @@
 # Introduction
 
-This action leverages [gunnargrosch/failure-lambda](https://github.com/gunnargrosch/failure-lambda) and the AWS Systems Manager API to deny connections to other hosts for an AWS Lambda.
+This action leverages [steadybit/failure-lambda](https://github.com/steadybit/failure-lambda) and the AWS Systems Manager API to deny connections to other hosts for an AWS Lambda.
 
 # Use Cases
 
 - Understand how a lambda behaves when an external dependency is unavailable.
 
 # Prerequisites
 
-The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/gunnargrosch/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
+The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/steadybit/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
 
 # Parameters
 

actions/com.steadybit.extension_aws.lambda.diskspace/summary.mdx

@@ -1,14 +1,14 @@
 # Introduction
 
-This action leverages [gunnargrosch/failure-lambda](https://github.com/gunnargrosch/failure-lambda) and the AWS Systems Manager API to fill the tmp disk of a lambda.
+This action leverages [steadybit/failure-lambda](https://github.com/steadybit/failure-lambda) and the AWS Systems Manager API to fill the tmp disk of a lambda.
 
 # Use Cases
 
 - Understand how a lambda behaves when it pollutes the tmp directory
 
 # Prerequisites
 
-The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/gunnargrosch/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
+The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/steadybit/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
 
 # Parameters
 

actions/com.steadybit.extension_aws.lambda.exception/summary.mdx

@@ -1,14 +1,14 @@
 # Introduction
 
-This action leverages [gunnargrosch/failure-lambda](https://github.com/gunnargrosch/failure-lambda) and the AWS Systems Manager API to inject exceptions into AWS Lambdas.
+This action leverages [steadybit/failure-lambda](https://github.com/steadybit/failure-lambda) and the AWS Systems Manager API to inject exceptions into AWS Lambdas.
 
 # Use Cases
 
 - Understand how other (e.g. upstream services, monitoring) behaves when the lambda is returning a failure.
 
 # Prerequisites
 
-The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/gunnargrosch/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
+The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/steadybit/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
 
 # Parameters
 

actions/com.steadybit.extension_aws.lambda.latency/summary.mdx

@@ -1,14 +1,14 @@
 # Introduction
 
-This action leverages [gunnargrosch/failure-lambda](https://github.com/gunnargrosch/failure-lambda) and the AWS Systems Manager API to inject latency into an AWS Lambda.
+This action leverages [steadybit/failure-lambda](https://github.com/steadybit/failure-lambda) and the AWS Systems Manager API to inject latency into an AWS Lambda.
 
 # Use Cases
 
 - Understand how other (e.g. upstream services, monitoring) behaves when the lambda is answering to slow.
 
 # Prerequisites
 
-The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/gunnargrosch/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
+The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/steadybit/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
 
 # Parameters
 

actions/com.steadybit.extension_aws.lambda.statusCode/summary.mdx

@@ -1,14 +1,14 @@
 # Introduction
 
-This action leverages [gunnargrosch/failure-lambda](https://github.com/gunnargrosch/failure-lambda) and the AWS Systems Manager API to return a fixed status code from an AWS Lambda.
+This action leverages [steadybit/failure-lambda](https://github.com/steadybit/failure-lambda) and the AWS Systems Manager API to return a fixed status code from an AWS Lambda.
 
 # Use Cases
 
 - Understand how other (e.g. upstream services, monitoring) behaves when the lambda is answering with abnormal status codes.
 
 # Prerequisites
 
-The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/gunnargrosch/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
+The AWS Lambda Function to attack must [be wrapped with the failure-lambda library](https://github.com/steadybit/failure-lambda#how-to-install-with-parameter-in-ssm-parameter-store).
 
 # Parameters
 

index.json

@@ -1,5 +1,5 @@
 {
-    "lastChange": 1724146284,
+    "lastChange": 1724331843,
     "templates": [
         "/templates/aws-ec2.ec2-restart/template.json",
         "/templates/aws-ecs.scale-cpu-stress/template.json",