Files
aitbc/infra/terraform
aitbc 3897bcbf24
Some checks failed
CLI Tests / test-cli (push) Failing after 4s
Deploy to Testnet / deploy-testnet (push) Successful in 1m40s
Documentation Validation / validate-docs (push) Failing after 12s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Integration Tests / test-service-integration (push) Successful in 2m42s
Package Tests / Python package - aitbc-agent-sdk (push) Failing after 34s
Package Tests / Python package - aitbc-core (push) Successful in 27s
Package Tests / Python package - aitbc-crypto (push) Successful in 13s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 8s
Package Tests / JavaScript package - aitbc-token (push) Successful in 18s
Python Tests / test-python (push) Failing after 50s
Security Scanning / security-scan (push) Failing after 43s
Multi-Node Stress Testing / stress-test (push) Successful in 12s
Cross-Node Transaction Testing / transaction-test (push) Successful in 9s
refactor: move version to separate module and improve logging
- Created aitbc/_version.py with centralized version definition
- Updated aitbc/__init__.py to import __version__ from _version module
- Updated constants.py to use __version__ for PACKAGE_VERSION
- Replaced print() calls with logger in decorators.py, events.py, queue_manager.py, and state.py
- Added logger initialization using get_logger(__name__) in config.py, decorators.py, events.py, queue_manager.py, and state.py
- Added cli/commands
2026-05-11 20:12:01 +02:00
..

AITBC Terraform Infrastructure

This directory contains Terraform configurations for deploying AITBC infrastructure on AWS.

Current Scope

ECS-focused with partial Kubernetes support

The Terraform configuration is primarily focused on ECS deployment with some Kubernetes modules. Current coverage includes:

  • ECS: Task definitions, services, and cluster configuration
  • Kubernetes: Partial support through modules/kubernetes/
  • Missing components: Full VPC, RDS, and IAM modules are not yet implemented

This is a partial implementation suitable for current ECS-based deployment.

Prerequisites

  • Terraform >= 1.0
  • AWS CLI configured with appropriate credentials
  • S3 bucket for Terraform state (configured in backend)
  • DynamoDB table for state locking (configured in backend)

Directory Structure

terraform/
├── main.tf              # Main Terraform configuration
├── provider.tf          # Provider configuration
├── variables.tf         # Infrastructure variables
├── outputs.tf           # Infrastructure outputs
├── ecs.tf               # ECS task definitions and services
├── ecs_variables.tf     # ECS-specific variables
└── README.md            # This file

Usage

Initialize Terraform

terraform init

Plan Infrastructure

terraform plan -var-file=dev.tfvars

Apply Infrastructure

terraform apply -var-file=dev.tfvars

Destroy Infrastructure

terraform destroy -var-file=dev.tfvars

Variables

Create a dev.tfvars, staging.tfvars, or prod.tfvars file with environment-specific variables:

environment          = "dev"
aws_region           = "us-east-1"
db_username          = "aitbc"
db_password          = "your-secure-password"
database_url         = "postgresql://..."
redis_url           = "redis://..."
jwt_secret           = "your-jwt-secret"
acm_certificate_arn  = "arn:aws:acm:..."

Infrastructure Components

Networking

  • VPC with public and private subnets
  • NAT Gateway for private subnet internet access
  • Security groups for different services

Compute

  • ECS Fargate cluster
  • ECS task definitions for API services
  • Application Load Balancer
  • Auto-scaling capabilities

Databases

  • RDS PostgreSQL for application data
  • ElastiCache Redis for caching

Storage

  • S3 bucket for data storage
  • Versioning and encryption enabled

Monitoring

  • CloudWatch Log Groups
  • ECS CloudWatch Container Insights

State Management

Terraform state is stored in S3 with DynamoDB locking:

  • State bucket: aitbc-terraform-state
  • Lock table: aitbc-terraform-locks

Security

  • All resources are tagged with project and environment
  • Security groups restrict access by CIDR blocks
  • RDS and Redis are in private subnets
  • Secrets stored in AWS Secrets Manager
  • S3 encryption enabled
  • RDS encryption enabled

Cost Optimization

  • Use appropriate instance sizes for environment
  • Enable auto-scaling for production
  • Monitor costs with AWS Cost Explorer
  • Use reserved instances for predictable workloads

Outputs

After applying the configuration, Terraform outputs:

  • VPC and subnet IDs
  • ECS cluster ID and ARN
  • ALB DNS name
  • Database and Redis endpoints
  • S3 bucket name

Troubleshooting

State Lock Issues

If you encounter state lock issues:

terraform force-unlock <LOCK_ID>

Resource Already Exists

If resources already exist outside Terraform, import them:

terraform import aws_vpc.this vpc-xxxxx

Permission Errors

Ensure your AWS credentials have the necessary permissions:

  • EC2 (VPC, subnets, security groups)
  • ECS (clusters, task definitions, services)
  • ELB (load balancers, target groups)
  • RDS (database instances)
  • ElastiCache (Redis clusters)
  • S3 (buckets)
  • Secrets Manager (secrets)