π§ AWS Lambda Function is not in multiple Availability Zones - prod.logic.yamlπ’
- Contextual name: π§ prod.logic.yamlπ’
- ID:
/ce/ca/aws/lambda/function-multi-az/prod.logic.yaml - Tags:
- π’ Logic test success
- π’ Logic with extracts
- π’ Logic with test data
Usesβ
Test Results π’β
Generated at: 2026-01-17T12:02:54.415433440Z Open
| Result | Id | Condition Index | Condition Text | Runtime Error |
|---|---|---|---|---|
| π’ | test1 | βοΈ 99 | βοΈ isDisappeared(CA10__disappearanceTime__c) | βοΈ null |
| π’ | test2 | βοΈ 199 | βοΈ CA10__AWS_Lambda_Function_Versions__r.has(COMPLIANT) | βοΈ null |
| π’ | test3 | βοΈ 299 | βοΈ CA10__vpcId__c.isEmpty() | βοΈ null |
| π’ | test4 | βοΈ 399 | βοΈ CA10__AWS_Lambda_Function_Subnet_Links__r.count(COMPLIANT) < number(2.0) | βοΈ null |
| π’ | test5 | βοΈ 400 | βοΈ otherwise | βοΈ null |
Generation Bundleβ
| File | MD5 | |
|---|---|---|
| Open | /ce/ca/aws/lambda/function-multi-az/policy.yaml | 4C8F353219B32A635DFD6D19A6A04FCA |
| Open | /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml | 9F6105ACEDF004882CA998D4241BA05C |
| Open | /ce/ca/aws/lambda/function-multi-az/test-data.json | 7A2F4B5F37D7F424309C12BC54FBA1D9 |
| Open | /types/CA10__CaAwsLambdaFunction__c/object.extracts.yaml | AC42D0E20DDB5A13477C5EE7A9A969D6 |
Available Commandsβ
repo-manager policies generate FULL /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml
repo-manager policies generate DEBUG /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml
repo-manager policies generate CAPTURE_TEST_DATA /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml
repo-manager policies generate TESTS /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml
# Execute tests
repo-manager policies test /ce/ca/aws/lambda/function-multi-az/prod.logic.yaml
Contentβ
---
inputType: "CA10__CaAwsLambdaFunction__c"
importExtracts:
- file: "/types/CA10__CaAwsLambdaFunction__c/object.extracts.yaml"
testData:
- file: "test-data.json"
conditions:
- status: "INAPPLICABLE"
currentStateMessage: "Lambda@Edge functions do not support VPC association."
check:
RELATED_LIST_HAS:
status: "COMPLIANT"
relationshipName: "CA10__AWS_Lambda_Function_Versions__r"
- status: "INAPPLICABLE"
currentStateMessage: "The Lambda function is not associated with a VPC."
check:
IS_EMPTY:
arg:
FIELD:
path: "CA10__vpcId__c"
- status: "INCOMPLIANT"
currentStateMessage: "The Lambda function is associated with only one Availability Zone."
remediationMessage: "Update the Lambda function configuration to include subnets in at least two different AZs."
check:
LESS_THAN:
left:
RELATED_LIST_COUNT:
status: "COMPLIANT"
relationshipName: "CA10__AWS_Lambda_Function_Subnet_Links__r"
right:
NUMBER: 2.0
otherwise:
status: "COMPLIANT"
currentStateMessage: "The Lambda function is associated with a VPC."
relatedLists:
- relationshipName: "CA10__AWS_Lambda_Function_Versions__r"
conditions:
- status: "COMPLIANT"
currentStateMessage: "This is Lambda@Edge function."
check:
RELATED_LIST_HAS:
status: "COMPLIANT"
relationshipName: "CA10__AWS_CloudFront_Lambda_Func_Associations__r"
otherwise:
status: "INAPPLICABLE"
currentStateMessage: "This function version does not have an association with CloudFront."
relatedLists:
- relationshipName: "CA10__AWS_CloudFront_Lambda_Func_Associations__r"
conditions: []
otherwise:
status: "COMPLIANT"
currentStateMessage: "This is Lambda@Edge function."
- relationshipName: "CA10__AWS_Lambda_Function_Subnet_Links__r"
conditions: []
otherwise:
status: "COMPLIANT"
currentStateMessage: "This is a subnet attached to the function."