Cloud-Resume-Backend

This Terraform setup uses the ansraliant/s3-state/aws module to configure a remote backend with S3 and DynamoDB for storing the Terraform state remotely.

Click here for 👉 Cloud Resume Frontend.

Prerequisites for creating the cloud infrastructure with given code

• Terraform installed on your machine.
• AWS CLI configured for AWS credentials with sufficient permissions
  • After installing AWS CLI
  • RUN "aws configure"
  • Get Credentials: "right-click-on-AWS-profile -> security-credentials -> Create-Access-Keys.
• Google Cloud SDK for creating a Google Cloud storage bucket. Ensure you have an account with a project with billing enabled.
  • "gcloud init" -> "gcloud projects list" -> "gcloud config set project your_project_id"
  • Terraform requires gcloud's credentials or access_token refer 1 & 2. Set manually or run gcloud auth application-default login.

Option 1) Create infrastructure from the console and import it to Terraform to recreate a similar code structure and avoid massive code changes:

• First, define the basic terraform code for your resources (without any additional arguments like name, etc.) then:
  • Run "terraform init"
  • ''terraform validate"
  • ''terraform import resource.resource_name resource_identifier"
  • "terraform scan"
    • Find and copy the imported code block for your resource.
    • Replace the code with the basic code in your Terraform files.
  • "terraform validate" to know which code lines we need to remove from our Terraform files.
  • Refine the code by replacing deprecated code blocks to resolve the warnings (if any) seen upon running "terraform plan" with the respective resource blocks.
  • "terraform plan" or "terraform apply" might show that it creates new resources. This is normal since Terraform considers separate resource policy blocks as individual resources. However, it shall not affect your existing infrastructure if you have used the original code or carefully resolved the "terraform plan" warnings.

Usage of existing code

1. Clone this repository:

   git clone [email protected]:deepansharya1111/cloud-resume-backend.git
   cd cloud-resume-backend/terraform/

2. Customisation: replace the highlighted texts with your desired globally unique names. Run terraform fmt to format if additional changes are made.

   • For Terraform Remote Backend with S3 and DynamoDB, change the bucket_name and dynamodb_table names in backend.tf.
   • For creating a GCP Storage bucket, change the project and name variables in gcp.tf.
   • AWS Resources:
     • For the S3 bucket to store the frontend code, change every deepansh_app_bucket and deepansh.app in aws.tf.
     • For CloudFront distribution and ACM Certificate: change every instance of your bucket name deepansh.app and domain *.deepansh.app or CNAME www.deepansh.app with your bucket_name, *your.domain, and your CNAME that is registered as a DNS record in your DNS.
     • (optional) For DynamoDB table and Lambda Function: customize lambda function name or iam policy names, etc, to your liking; else, leave it as it is.

3. Initialize Terraform:

   terraform init
   

4. Validate your Terraform configuration:

   terraform validate
   

5. Plan your Terraform configuration:

   terraform plan
   

6. Apply your Terraform configuration:

   terraform apply
   

7. See Google Cloud storage buckets:

   gsutil ls
   

8. See AWS DynamoDB tables

   aws dynamodb list-tables
   

9. See AWS S3 bucket

   aws s3 ls
   

Configuration Details

aws.tf: Contains the main AWS Terraform configuration.

backend.tf: Includes the ansraliant/s3-state/aws module for remote state configuration.

provider.tf: Contains the AWS provider configuration.

gcp.tf: Contains the GCP provider and Cloud Storage Bucket configurations for hosting static websites.

``backend.tf.json`: Backend configuration file with details for S3 bucket, key, region, and DynamoDB table.