Terraform AWS AppSync
GraphQL APIs with resolvers, data sources, API keys or IAM and Cognito authentication, logging, caching, custom domains, and fine grained access patterns.
Quick start
module "appsync" {
source = "eugmpannex11.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "iso27001.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "soc2.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "acscessentialeight.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "nis2.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "nistcsf.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}module "appsync" {
source = "pcidss.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
# ... your arguments here
}This module on the compliance.tf registry lists its versions, inputs and outputs. The Get Started guide and Registry Endpoints cover authentication and how to customize the module for your requirements.
Migration from upstream
Already using terraform-aws-modules? Change only the source URL:
module "appsync" {
source = "terraform-aws-modules/appsync/aws"
version = "~> 4.1"
}module "appsync" {
source = "soc2.compliance.tf/terraform-aws-modules/appsync/aws"
version = "~> 4.1"
}Same arguments. Same outputs. Controls are checked at terraform plan. The Migration Guide has the step-by-step version.
Reversibility
No lock-in. Switch back by reverting the source URL:
module "appsync" {
source = "terraform-aws-modules/appsync/aws"
}Run terraform init -upgrade. Terraform state is unchanged: same resource addresses, same provider, no compliance.tf-specific resources. Controls you already applied remain in AWS.
Controls enforced
Up to 4 controls are checked at terraform plan when this module comes from a compliance.tf endpoint. Which ones are active depends on the endpoint; see Framework coverage.
Mapped compliance frameworks
| Clause | Controls from this module |
|---|---|
| 12.1 Security | |
| 7.1 Data Storage - Damage Protection |
| Clause | Controls from this module |
|---|---|
| A.8.15 Logging | |
| A.8.24 Use of cryptography |
| Clause | Controls from this module |
|---|---|
| A1.2 The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and monitors environmental protections, software, data back-up processes, and recovery infrastructure to meet its objectives | |
| CC6.7 The entity restricts the transmission, movement, and removal of information to authorized internal and external users and processes, and protects it during transmission, movement, or removal to meet the entity's objectives |
| Clause | Controls from this module |
|---|---|
| ACSC-EE-ML2-7.7: Multi-factor authentication ML2 |
| Clause | Controls from this module |
|---|---|
| 11.10(d) Limiting system access to authorized individuals |
| Clause | Controls from this module |
|---|---|
| 3 Incident handling |
| Clause | Controls from this module |
|---|---|
| PR.PS-04 |
| Clause | Controls from this module |
|---|---|
| 10.2.1.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.3: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.4: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.5: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.6: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1.7: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.1: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.2.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events. | |
| 10.3.1: Audit logs are protected from destruction and unauthorized modifications. | |
| 10.6.3: Time-synchronization mechanisms support consistent time settings across all systems. | |
| 5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored. | |
| A1.2.3: Processes or mechanisms are implemented for reporting and addressing suspected or confirmed security incidents and vulnerabilities |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
| Control | SOC 2 | PCI DSS v4.0 |
|---|---|---|
| AppSync GraphQL APIs should not use API key authentication | Not active | Not active |
| AppSync API caches should have encryption at rest enabled | Not active | Not active |
| AppSync API caches should have encryption in transit enabled | Enforced | Not active |
| AppSync GraphQL APIs should have field-level logging enabled | Enforced | Enforced |
4 controls enforced with a source URL change.