Garrison Agent that provides AWS Lambda compliance checks
10K+
This is a part of the Garrison security project. This agent provides various AWS Lambda compliance checks.
| Function Name | Description |
|---|---|
check_dead_letter | Alerts if a Lambda function has no dead letter config. |
check_encryption_at_rest | Alerts if a Lambda function is not using a customer master key (AWS KMS CMK) for encryption at rest. |
check_runtime_deprecations | Alerts if a Lambda function is using a deprecated runtime. |
Docker Hub - https://hub.docker.com/r/forward3d/garrison-agent-aws-lambda/
docker pull forward3d/garrison-agent-aws-lambda
docker run --rm -e "GARRISON_URL=https://garrison.internal.acme.com" forward3d/garrison-agent-aws-lambda check_runtime_deprecations
These are additional specific configuration options for this agent. Global agent configurations still apply.
| Environmental Variable | Default | Expects |
|---|---|---|
GARRISON_AWS_REGIONS | all [1] | Comma Separated Strings eg. eu-west-1,us-west-2 |
As this requires access to the AWS API you will need this IAM policy as a minimum for it to operate correctly.
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"lambda:ListFunctions"
],
"Resource": "*",
"Effect": "Allow"
}
]
}
We recommend using EC2/ECS Task roles so that you don't need to send credentials into the container, however if you can't use those or want to send in specific Access Keys and Secret keys, please see the AWS Documentation as to how you do that.
STS AssumeRole)If you run Garrison agents in one account, and want to reach into other AWS accounts you need to send in extra environmental variables to support that.
| Environmental Variable | Value |
|---|---|
AWS_ACCOUNT_ID | Not used as part of authentication, but to override the tag set on any alerts |
AWS_ASSUME_ROLE_CREDENTIALS_ARN | Arn of the role (in the other account) you wish to assume |
Content type
Image
Digest
Size
27.1 MB
Last updated
over 5 years ago
docker pull forward3d/garrison-agent-aws-lambda