For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex CloudApplication Security

AWS App Flow connector profile does not use Customer Managed Keys (CMKs) misconfiguration detected i

Rule Details

Cortex AppSec Rule ID

APPSEC_AWS_264

Category - Subcategory

Storage - Encryption

Provider

AWS

Severity

LOW

Framework

Terraform

Impact

This rule identifies App Flow connector profile which are encrypted with default KMS keys and not with Keys managed by Customer. It is a best practice to use customer managed KMS Keys to encrypt your App Flow connector profile data. It gives you full control over the encrypted data.

How to Fix

[source,go]

resource "aws_appflow_connector_profile" "pass" { name = "example_profile" connector_type = "Redshift" connection_mode = "Public" kms_arn = aws_kms_key.example.arn

connector_profile_config {

connector_profile_credentials { redshift { password = aws_redshift_cluster.example.master_password username = aws_redshift_cluster.example.master_username } }

connector_profile_properties { redshift { bucket_name = aws_s3_bucket.example.name database_url = "jdbc:redshift://${aws_redshift_cluster.example.endpoint}/${aws_redshift_cluster.example.database_name}" role_arn = aws_iam_role.example.arn } } } }

Last updated

Was this helpful?