AWS AppSync API caches should be encrypted in transit¶

This control checks whether an AWS AppSync API cache is encrypted in transit. The control fails if the API cache isn't encrypted in transit.

How to fix¶

Attribute transit_encryption_enabled of aws_appsync_api_cache must be true.

Implementation options¶

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources¶

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_appsync_api_cache.

resource "aws_appsync_graphql_api" "this" {
  name                = "pofix-example-api"
  authentication_type = "API_KEY"
}

resource "aws_appsync_api_cache" "this" {
  api_caching_behavior = "FULL_REQUEST_CACHING"
  api_id               = "abc123"
  ttl                  = 3600
  type                 = "SMALL"

  transit_encryption_enabled = true
}

Which option should I choose?

Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings¶

Use these identifiers to cross-reference this control across tools, reports, and evidence.

Compliance.tf (CTF) Control: appsync_graphql_api_cache_encryption_in_transit_enabled
AWS Config Managed Rule: APPSYNC_CACHE_CT_ENCRYPTION_IN_TRANSIT
Checkov Check: CKV_AWS_215
Powerpipe Control: aws_compliance.control.appsync_graphql_api_cache_encryption_in_transit_enabled