How jayshenkar07/terraform works
Project Components Identification
• Infrastructure Resources: Highlight the specific AWS resources being provisioned:
• EC2 Instances (under “Launch_EC2_Instance” and corresponding custom module in “Modules/ec2-instance_custom_module”)
• S3 Buckets (under “Create_S3_Bucket” and “Modules/s3_custom_module”)
• DynamoDB Tables (“DynamoDB_Table”)
• Custom Modules: Emphasize the reusable modules for EC2 and S3 (found in “Modules”) which abstract repetitive code.
• Providers Configuration: Include a component for provider configurations (found under “Providers”) that manages multiple providers and regions.
• Variables Management: Represent the variables (and conditional variables) that control dynamic behaviors (located in “Variables”).
• Remote Backends: Show the setup that manages Terraform state remotely (found under “Remote_Backends”).
Design Principles and Architectural Patterns
• Modularization: Emphasize that the project uses a modular design (reusable modules are in a dedicated folder) which helps in code reuse and maintainability.
• Environment Separation: With folders for variables and remote backends, indicate how different environments (or regions/providers) might be managed.
• Declarative Infrastructure as Code: Note that each Terraform configuration defines desired state for AWS resources.
Relevant Technologies, Frameworks, and Libraries
• Terraform, as the core technology.
• AWS as the targeted cloud provider (implied by the resource names like EC2, S3, and DynamoDB).
• Supporting Git-based storage for configurations (implied by the file tree structure).