Skip to content

fix for CKV_AWS_355 #162

fix for CKV_AWS_355

fix for CKV_AWS_355 #162