Terraform Demo - Provision Infrastructure

[juanpedromoreno]

🚀 Terraform Infrastructure

This PR adds the Terraform scripts to deploy the infrastructure in AWS. 🏆

📝 Type of change

• ✨ New feature (non-breaking change which adds functionality)

🔬 How Has This Been Tested?

• 🏠 Validating the scripts locally.

📜 Checklist:

• 🎨 My code follows the style guidelines of this project
• 👀 I have performed a self-review of my own code
• 📝 I have commented my code, particularly in hard-to-understand areas
• 📚 I have made corresponding changes to the documentation
• ⚠️ My changes generate no new warnings
• ✔️ I have added tests that prove my fix is effective or that my feature works
• 💚 New and existing unit tests pass locally with my changes

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-actions]

FormaLM has performed a code analysis and generated a report. Please check the Security report for more information.

[github-actions]

IaC Report

The project contains the following deployments:

TERRAFORM: src/main.tf

This deployment yaml describes an infrastructure on AWS. It includes an EC2 instance and an Elastic IP. The EC2 instance is based on the 'ami-0a8b4cd432b1c3063' image and is of type 't2.micro'. The instance has an encrypted root block device. The Elastic IP is associated with the EC2 instance.

graph LR
  EC2[EC2 Instance] --> EIP[Elastic IP]
  subgraph EC2
    EC2 -- AMI: ami-0a8b4cd432b1c3063
    EC2 -- Type: t2.micro
    EC2 -- Encrypted Root Block Device
  end

Loading

High severity misconfigurations

• aws_instance should activate session tokens for Instance Metadata Service.:
  IMDS v2 (Instance Metadata Service) introduced session authentication tokens which improve security when talking to IMDS.
  By default aws_instance resource sets IMDS session auth tokens to be optional.
  To fully protect IMDS you need to enable session tokens by using metadata_options block and its http_tokens variable set to required.

Medium severity misconfigurations

There are no misconfigurations of Medium severity.

[github-actions]

IaC Report

The project contains the following deployments:

TERRAFORM: src/main.tf

This deployment yaml describes an infrastructure in AWS. It includes an EC2 instance and an Elastic IP address. The EC2 instance is based on the 'ami-0a8b4cd432b1c3063' AMI and uses the 't2.micro' instance type. The EC2 instance has an encrypted root block device and requires HTTP tokens for metadata options. The Elastic IP address is associated with the EC2 instance.

graph LR
EC2_Instance[EC2 Instance] --> Elastic_IP[Elastic IP Address]

Loading

High severity misconfigurations

There are no misconfigurations of High severity.

Medium severity misconfigurations

There are no misconfigurations of Medium severity.

[github-actions]

FormaLM has performed a code analysis and generated a report. Please check the Security report for more information.