Setting up Geocodes Services on AWS

Note

we decided against using both s3 and Neptune. each neptune instnace is one graph namespace, so at $95/month for an instance, that is a bit high. s3 works, but for testing we take buckets up and down, easier to manage in minio that AWS.

To do this, we are going to utilize four pieces: * s3, replaces Minio Container * neptune, replaces Graph Container * single virutal machine setup as a docker storm. * Portainer setup on in Our Openstack.

Major differences in the docker: * uses config to store traefik config * use a volume to store the trafik * using secrets

Notes on Setting up s3 and Neptune

Docker stack

Install docker stack setup as the base machine install where docker stack init --address--

From Console

setup netowrk
setup volumes
setup config
setup secrets

volume create traefik_data volume create logs

docker network create -d overlay --attachable traefik_proxy

docker config create traefik_yml ./traefik-aws/traefik.yml

docker secret create

S3SSL=true S3PORT=443

MINIO_ROOT_ACCESS_KEY=worldsbestaccesskey MINIO_ROOT_SECRET_KEY=worldsbestsecretkey

MINIO_SERVICE_ACCESS_KEY=worldsbestaccesskey

MINIO_SERVICE_SECRET_KEY=worldsbestsecretkey

GC_GITHUB_CLIENTID_OR_USER_GITHUB_TOKEN=OAUTH SECRET GC_GITHUB_SECRET_OR_USER=OAUTH APP ID

setup stack in portainer

edit the portainer_aws.env
copy over the base-aws-compose.yaml

or use the git version

Name: base
Build method: git repository
Repository URL: https://github.com/earthcube/geocodes
Reference: refs/heads/main
Compose path: dbase-aws-compose.yaml

Notes:

https://enginaltay.medium.com/how-to-use-traefik-as-ingress-router-on-aws-fc559f87f4d8