This sample demonstrates how to create a full environment for the open source forum tool Discourse. This example will create all assets required to utilize AWS services. The Discourse site will be automatically setup with an initial admin user and an OpenID plugin is set up to allow users to register and login via Amazon Cognito.

1. Amazon CloudFront is used for CDN via S3 and the application load balancer
2. Amazon Route 53 holds the hosted zone for DNS management to create verified outbound email domains along with domain certificates
3. Amazon S3 holds user upload files and static assets in one bucket along with Discourse backups in another bucket
4. AWS Certificate Manager is used to create a DNS validated certificate
5. AWS Secrets Manager holds the initial setup credentials and created database credentials.
6. Amazon Cogntio user pools are used via OpenID
7. Amazon SES handles outbound email notifications
8. AWS Systems Manager Session Manager is used to connect to internal instances for debugging purposes
9. AWS Auto Scaling will create the desired number of instances in the desired availability zones
10. Amazon EC2 instances are bootstrapped via a user data script which pulls down the latest stable version of Discourse and sets up the app.yml then launches the Discourse docker image.
11. Amazon RDS Aurora serverless V2 Postgres database stores user details and posts
12. Amazon ElastiCache for Redis is used as a caching layer

1. Apache Maven 3.8.5 or greater installed
2. Java 11 or greater installed
3. AWS Cloud Development Kit (CDK) 1.120.0 or higher
4. Valid docker login credentials
5. A domain name hosted by Route53 which is used to
   1. Create a subdomain for discourse
   2. Validate SES domain
   3. Validate DNS Certificates
6. Public Acl creation must be enabled on the account for discourse to work. The following aws cli command will enable the required options

aws s3control put-public-access-block \
--account-id 123456789012 \
--public-access-block-configuration '{"BlockPublicAcls": false, "IgnorePublicAcls": true, "BlockPublicPolicy": true, "RestrictPublicBuckets": true}'

1. Git clone this repository
2. Create an AWS Secrets Manager secret with the following key value pairs
   1. DOCKER_USER - A docker login user (required for docker pull quota)
   2. DOCKER_PASSWORD - A docker login password
   3. DISCOURSE_ADMIN_EMAIL - The email address for the initial admin user
   4. DISCOURSE_ADMIN_PASSWORD - The password for the initial admin user
   5. DISCOURSE_ADMIN_USERNAME - The username for the initial discourse user
      1. Note this is a discourse login and is not linked to cognito.
3. Edit the cdk-command.sh with information required
   1. CDK_DEPLOY_DISCOURSE_ACCOUNT - The AWS account used for this deployment
   2. CDK_DEPLOY_DISCOURSE_REGION - The AWS region used for this deployment
   3. CDK_DEPLOY_DISCOURSE_STACK_ID - The stack id can be modified to allow for CI/CD and multiple different deployments. If no value is set the default value of 'Discourse' is used.
   4. CDK_DEPLOY_DISCOURSE_HOSTED_ZONE_ID - The Route 53 hosted zone id
   5. CDK_DEPLOY_DISCOURSE_HOSTED_ZONE_NAME - The Route 53 hosted zone name
   6. CDK_DEPLOY_DISCOURSE_DOMAIN_NAME - The domain name to use for this instance of discourse for example 'discourse.example.com'
   7. CDK_DEPLOY_DISCOURSE_SES_SMTP_DOMAIN_NAME - The domain name to use for SES SMTP emails
   8. CDK_DEPLOY_DISCOURSE_NOTIFICATION_EMAIL - The email address for outbound notification emails from the Discourse system
   9. CDK_DEPLOY_DISCOURSE_DEVELOPER_EMAILS - A list of admin account email addresses separated by commas
   10. CDK_DEPLOY_DISCOURSE_COGNITO_AUTH_SUB_DOMAIN_NAME - Amazon Cognito domain for the hosted UI
   11. CDK_DEPLOY_DISCOURSE_SETTINGS_SECRET_ARN - 'arn:aws:secretsmanager:{region}:{account}:secret:{secret}
   12. CDK_DEPLOY_DISCOURSE_CIDR - The CIDR block to use when creating the VPC
   13. CDK_DEPLOY_DISCOURSE_CLOUDFRONT_ALB_HEADER_CHECK_HEADER - This header name is used to restrict access to the ALB from just CloudFront. If this environment variable is not found a default value of 'X-Discourse-ALB-Check' is used.
   14. CDK_DEPLOY_DISCOURSE_CLOUDFRONT_ALB_HEADER_CHECK_VALUE - The header value use to restrict access to the ALB from just CloudFront. If this environment variable is not found a default value of 'c9fd4d17-24a6-463f-b470-1c4347253245' is used.
4. Run ./cdk-command.sh deploy to deploy into your account
5. It takes approx. 15-20 minutes AFTER the discourse EC2 instance is created for the full discourse setup to complete and be available
   1. The EC2 instance will set up the database structure and push assets to the S3 bucket prior to starting up the Discourse server

1. You can log into EC2 instances via Session Manager
2. Once logged in you will require sudo -s for most commands
3. Discourse is installed in the folder /var/discourse
4. Running . discourse-env in the /var/discourse folder will set up the current shell session environment variables
5. To check if docker is running execute the command docker ps
6. EC2 instance startup logs are located at /var/log/cloud-init-output.log and can be helpful to determine the actions taken by the user data startup script.
   1. This log may also contain any errors that occurred on startup.
7. You can run various docker commands via the Discourse helper script ./launcher {command} app for instance:
   1. ./launcher enter app will put you into the discourse docker instance shell
   2. ./launcher logs app will display the discourse docker app logs
8. Your accounts SES (simple email service) will only send email to verified addresses unless validated for production.
   1. Via the console you can add your own email to the verified list for testing

1. From the root folder for this project run ./cdk-command.sh destroy

See CONTRIBUTING for more information.

This library is licensed under the MIT-0 License. See the LICENSE file.