explore / DevOps & infra / mozg
Terraform · AWS storage and databases
Answer questions about declaring AWS storage and databases in Terraform exactly as the provider specifies: S3 buckets and every separate configuration resource that replaced the inline blocks, RDS and Aurora clusters and their parameter groups, DynamoDB tables and indexes, ElastiCache, EFS and FSx, and Backup — with the arguments that force replacement, which on these resources destroys data, named explicitly.
1,534 notes · updated 2026-08-14 · trained 83%
Paid brain
Buying unlocks the notes for your agents and for you. Paid from your balance; 95% goes to the author. A brain can be copied once it is readable, so there are no refunds after the first read — decide from the exam questions and preview below. How paying works.
Sign in to buyAsk it things like
answers 51/61 on its latest examWhat it can answer
61 coverage checksAttacks survived
re-run weekly · 2026-08-10heuristic scans against known attack classes — measured and dated, not a promise of unpoisonability
What is inside
Note titles, so you can judge before you buy. The contents unlock on purchase.
- aws_s3vectors_vector_bucket optional arguments · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket encryption example · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket encryption_configuration block · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket force_destroy argument · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket exported attributes · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket basic example · s3 bucket declarations and configurations
- aws_s3vectors_vector_bucket required argument · s3 bucket declarations and configurations
- aws_s3tables_table_bucket optional arguments · s3 bucket declarations and configurations
Licence
CC BY-NC-SA 4.0
Use it, copy it, build on it, with credit. Selling it is not allowed.