openclaw/workers/clawdbot-aws/.env.example
Shunsuke Hayashi 8ffe18aaee feat(aws): migrate Discord token to Secrets Manager and fix infrastructure
- Add Secrets Manager integration for Discord bot token
- Add aws_account_id and discord_token_secret_name variables
- Update ECS task definition to use Secrets Manager
- Add IAM policy for Secrets Manager access
- Fix Dockerfile .buildstamp generation for Linux compatibility
- Change VPC CIDR to 100.64.0.0/16 to avoid conflicts
- Add deployment documentation and .env.example

Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-26 13:08:57 +09:00

34 lines
1.0 KiB
Plaintext

# AWS Terraform Variables for Clawdbot ECS Fargate Deployment
# Copy this file to terraform.tfvars and fill in the values
# AWS Configuration
aws_region = "ap-northeast-1"
aws_account_id = "123456789012" # Your AWS account ID
# Environment
environment = "production"
project_name = "clawdbot"
# ECS Configuration
ecs_task_cpu = 256 # 0.25 vCPU
ecs_task_memory = 2048 # 2 GB
ecs_service_desired_count = 1
# Discord Token (DEPRECATED - Use Secrets Manager instead)
# discord_token = "your_bot_token_here" # DO NOT use in production
# Secrets Manager Secret Name for Discord Bot Token
discord_token_secret_name = "clawdbot/discord-token"
# Create the secret in AWS Secrets Manager before running Terraform:
# aws secretsmanager create-secret \
# --name clawdbot/discord-token \
# --secret-string "your_bot_token_here"
# DynamoDB Tables
sessions_table_name = "clawdbot-sessions"
artifacts_table_name = "clawdbot-artifacts"
# S3 Bucket
artifacts_bucket_name = "clawdbot-artifacts"
artifacts_bucket_ttl_days = 7