Go to file
Peter Oehmichen 554f96700c bugfix logger 2023-06-29 11:05:19 +02:00
apps/cdh-maas bugfix logger 2023-06-29 11:05:19 +02:00
modules added base code for prepared layer. 2023-06-20 14:41:54 +02:00
.gitignore with dependency layer for Lambda 2023-06-09 15:20:49 +02:00
README.MD initial setup with base terraform structure 2023-06-07 16:38:36 +02:00
terraform.sh initial setup with base terraform structure 2023-06-07 16:38:36 +02:00

README.MD

MaaS-CDH Terraform IaC

Adding a main module

General structure:

  • terraform
    • apps
      • app #1
        • main module #1
        • main module #2
        • ...
      • ...
      • modules
        • module #1
          • submodule #1
        • module #2
        • ...
  • each main module is a subfolder under terraform/apps/<app>/<main module>
  • the corresponding modules are under terraform/modules

Manual test deployment

bash terraform.sh [project] [environment] [region] [main module] [terraform command]

Main Modules

Following main modules are currently provided:

  • init - terraform s3 state bucket and dynamodb lock table
  • main - all our app resources like db, redis, lambda, sqs, sns, opensearch, api gateway, ...

Useful resources

The following documents are a good source of information:

TF Module structure best practices

Orbit developed modules

Orbit developed modules should be working with the defined TF versions. It would be a good idea to keep also the TF code aligned. link

It is recommended scan code with checkov

Define a naming convention

Define a tagging convention

Walk through guide (useful for beginners)

Several Connected Drive examples

Requirements

No requirements.

Providers

No providers.

Modules

No modules.

Resources

No resources.

Inputs

No inputs.

Outputs

No outputs.