Skip to main content

​
Self Hosting Taxga.me

  1. Create an AWS account here.
  2. Install NodeJS here.
  3. Install AWS SAM here.
  4. Install AWS CDK here.
  5. Create access keys for your specified AWS user, preferably using an service account. You can view a guide here.
  6. Put the code from the submission.zip into an AWS Codecommit repository. You can follow this guide on how to get it all setup. Using AWS Codecommit will stream the process, but you can upload each file manually, especially in the case of AWS Amplify.
  7. Setup and link the client folder to AWS Amplify, and make sure you have the following as environmental variables. You can follow this guide to setup NextJS on AWS Amplify.
URL=website_url
API_URL=api_url
WS_URL=websocket_service_url
SESSION_SECRET=make_up_a_session_secret
NEXTAUTH_SECRET=your_secret_here
GOOGLE_CLIENT_ID=your_google_client_id_here
GOOGLE_CLIENT_SECRET=your_google_client_secret_here
  1. Create a .env. in the folder server with the following:
AWS_ACCESS_KEY=aws_access_key
AWS_SECRET_ACCESS=aws_secret_access
AWS_REGION=eu-central-1
OPENAI=openai_api_key
REDIS=aws_elasticache_instance_url
  1. In the server folder, run the command cdk deploy --all to deploy all stacks to AWS.
  2. Setup your EC2 and ElastiCache instances. You can follow this guide on how to do this.
  3. Once that has completed, you will need to visit AWS DynamoDB, get the table names and populate DATABASE_TABLES variable in server/lambda/index.ts, line 36.
  4. You will also need to populate the Lambda functions with the OPENAI and REDIS environmental variables. These can be added on the Lambda function, configuration, environmental variables. You can read this guide on how to do this.
  5. If you wish to add a custom domain, read this guide on how to add it and link to your AWS services. AWS Amplify has a step-by-step guide GUI on how to do this, to be sure to follow that.

​
Common Issues

​
Not communicating between networks

There might be an issue where your AWS services are not talking to each other. You need to ensure that all your AWS Lambda functions (both for the RESTful and Web Socket service) are on the same VPC (Virtual Private Cloud) as your EC2 instance that holds the Redis instance. Connect your Lambda functions to the VPC, you can follow this guide, and it should resolve all your issues.