Make cloud instance sizes configurable

[SahilGupta2810]

Summary

This PR addresses issue #95 by making the default compute size configurable across all three cloud providers, while preserving the current default behavior.

Changes

• AWS
  • Added aws_instance_type variable with default t3.micro
  • Updated the EC2 instance resource to use var.aws_instance_type
• Azure
  • Added azure_vm_size variable with default Standard_B1s
  • Updated the VM resource to use var.azure_vm_size
• GCP
  • Added gcp_machine_type variable with default e2-micro
  • Updated the compute instance resource to use var.gcp_machine_type

Documentation

• Added TROUBLESHOOTING.md with beginner-friendly AWS guidance for:
  • region / endpoint / auth errors
  • quota / vCPU limit errors
  • SCP / explicit deny errors
• Added provider-specific command guides:
  • docs/AWS_COMMANDS.md
  • docs/AZURE_COMMANDS.md
  • docs/GCP_COMMANDS.md
• Updated provider READMEs to link to troubleshooting and command docs
• Updated the AWS README to guide users to check enabled regions first, then set aws_region before applying Terraform

Why

Issue #95 points out that fixed defaults for region and VM size can fail depending on account restrictions, quota, or provider availability. This change keeps the existing defaults intact while allowing users to override them without editing Terraform files directly.

Examples:

terraform apply -var="aws_instance_type=t3.small"
terraform apply -var="azure_vm_size=Standard_B2s"
terraform apply -var="gcp_machine_type=e2-small"

[SahilGupta2810]

@madebygps can you please review this ?

[Princeman2]

Hi @SahilGupta2810 and maintainers,

I just finished my first PR (#92). I'm familiar with Azure only.

I'd like to help improve the Azure part of this PR:

• Improve the Azure README with clearer beginner steps
• Add more troubleshooting for common Azure errors (quota, region, subscription)
• Test it on my Azure account

Is that okay? I will only touch Azure files.

[Copilot]

Pull request overview

This PR addresses issue #95 by making the default VM/instance size configurable for AWS, Azure, and GCP Terraform deployments (while keeping existing defaults), and adds troubleshooting / command-flow documentation to help users handle common provider/account constraints.

Changes:

• Add new Terraform variables for compute sizing (aws_instance_type, azure_vm_size, gcp_machine_type) and wire them into the corresponding instance/VM resources.
• Add root troubleshooting guidance (currently AWS-focused) plus provider-specific “copy/paste” command guides.
• Update provider READMEs to link to the new docs.

Show a summary per file

File	Description
aws/main.tf	Adds aws_instance_type variable and uses it for the EC2 instance.
azure/main.tf	Adds azure_vm_size variable and uses it for the VM size.
gcp/main.tf	Adds gcp_machine_type variable and uses it for the compute instance machine type.
aws/README.md	Updates AWS getting-started flow and links to command/troubleshooting docs.
azure/README.md	Links to the Azure command flow doc and troubleshooting doc.
gcp/README.md	Links to the GCP command flow doc and troubleshooting doc.
TROUBLESHOOTING.md	Adds beginner-facing troubleshooting guidance (AWS sections + placeholders for Azure/GCP).
docs/AWS_COMMANDS.md	Adds a guided command flow for selecting region/instance type and running Terraform.
docs/AZURE_COMMANDS.md	Adds a guided command flow for selecting subscription/region/VM size and running Terraform.
docs/GCP_COMMANDS.md	Adds a guided command flow for selecting project/region/zone/machine type and running Terraform.

Copilot's findings

• Files reviewed: 10/10 changed files
• Comments generated: 2

[SahilGupta2810]

Addressed the latest review feedback in .

Changes made:

• removed the early example from the AWS README so only appears after �[0m�[1mTerraform initialized in an empty directory!�[0m

The directory has no Terraform configuration files. You may begin working
with Terraform immediately by creating Terraform configuration files.�[0m

• added an explicit note in that the AWS Terraform commands assume you are running them from the directory

If there are any other adjustments needed, I can update the branch.

[SahilGupta2810]

@madebygps review changes are commited

Addressed the latest review feedback in commit 5312ec3.

Changes made:

• removed the early terraform apply example from the AWS README so apply only appears after terraform init
• added an explicit note in TROUBLESHOOTING.md that the AWS Terraform commands assume you are running them from the aws/ directory

If there are any other adjustments needed, I can update the branch.

[Copilot]

Copilot's findings

• Files reviewed: 10/10 changed files
• Comments generated: 1