VilnaCRM-Org/crm-infrastructure

Create infrastructure for CRM system using terraform

Open

#1 opened on Mar 31, 2025

View on GitHub
 (0 comments) (0 reactions) (1 assignee)HCL (0 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Set up the infrastructure for the CRM system on AWS using Terraform. The CRM will be deployed on: Production: app.vilnacrm.com Testing: app.vilnacrmtest.com

This infrastructure should be similar to the existing website deployment but tailored for CRM-specific resources, including: S3 for hosting CloudFront for CDN and caching Route 53 for domain management IAM roles and policies Any additional required AWS services

Tasks

  • Set up Terraform module structure for CRM infrastructure
  • Configure S3 buckets for CRM
  • Set up CloudFront distribution for CRM
  • Configure Route 53 records for subdomains
  • Define IAM roles and policies
  • Implement Terraform backend and state management
  • Test deployment process

Acceptance Criteria

  • Terraform code is structured and modular
  • CRM is accessible via app.vilnacrm.com and app.vilnacrmtest.com
  • CloudFront distribution is correctly linked to S3 or another backend
  • DNS resolution via Route 53 is properly configured
  • IAM policies follow security best practices
  • Deployment is automated and reproducible

Contributor guide

Research direction
Review the existing website deployment infrastructure in the same repository to understand the Terraform module structure. Then adapt it for CRM, creating S3 buckets, CloudFront distributions, Route53 records, and IAM roles. Use Terraform state management and test the deployment.
Tech stack
aws
Domain
devops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TerraformAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30