Need help with deploying Production Corteza on aws

🚧 Installation
#1

Hi, i wanna to deploy corteza on aws on ec2.

I created a production instance.
I configured Nignx.
i have done this in AWS.

But how do i forword this to any Ip or domain address.

i have domains on godaddy, how can i add/ connect it to this instance.

what changes would i need to make in .env file.

#2

.env file

########################################################################################################################
# docker-compose supports environment variable interpolation/substitution in compose configuration file
# (more info: https://docs.docker.com/compose/environment-variables)

########################################################################################################################
# General settings
DOMAIN=app.example.org
VERSION=2022.9

########################################################################################################################
# Database connection

DB_DSN=postgres://corteza:corteza@db:5432/corteza?sslmode=disable

########################################################################################################################
# Server settings

# Serve Corteza webapps alongside API
HTTP_WEBAPP_ENABLED=true

# Send action log to container logs as well
# ACTIONLOG_DEBUG=true

# Uncomment for extra debug info if something goes wrong
# LOG_LEVEL=debug

# Use nicer and colorful log instead of JSON
# LOG_DEBUG=true

########################################################################################################################
# Authentication

# Secret to use for JWT token
# Make sure you change it (>30 random characters) if

does the domain have to be this, then I change the a records in godaddy with Name as “app.example.org” and value as the “ip address of the instance” like->

dns a record
dns a record1275Ă—335 8.38 KB

docker-compose.yaml file

version: '3.5'

services:
  server:
    image: cortezaproject/corteza:${VERSION}
    networks: [ proxy, internal ]
    restart: always
    env_file: [ .env ]
    depends_on: [ db ]
    volumes: [ "./data/server:/data" ]
    environment:
      # VIRTUAL_HOST helps NginX proxy route traffic for specific virtual host to
      # this container
      # This value is also picked up by initial boot auto-configuration procedure
      # If this is changed, make sure you change settings accordingly
      VIRTUAL_HOST: ${DOMAIN}
      # This is needed only if you are using NginX Lets-Encrypt companion
      # (see docs.cortezaproject.org for details)
      LETSENCRYPT_HOST: ${DOMAIN}

  db:
    # PostgreSQL Database
    # See https://hub.docker.com/_/postgres for details
    image: postgres:13
    networks: [ internal ]
    restart: always
    healthcheck: { test: ["CMD-SHELL", "pg_isready -U corteza"], interval: 10s, timeout: 5s, retries: 5 }
    environment:
      # Warning: these are values that are only used on 1st start
      #          if you want to change it later, you need to do that
      #          manually inside db container
      POSTGRES_USER:     voltsapp
      POSTGRES_PASSWORD: voltsapp

networks:
  internal: {}
  proxy: { external: true }
#3

If anybody can help, please letme know,
I can pay you for you work.

#4

You’ll need to add DNS records from within godaddy to point to your AWS public ip address (and make sure that your security group attached to the EC2 instance allows for access to port 80 and 443)