Skip to content

Latest commit

 

History

History
87 lines (80 loc) · 4.78 KB

management-console-setup.md

File metadata and controls

87 lines (80 loc) · 4.78 KB
Raw

Management Console Setup

Prerequisites

Please make sure that you have followed all of the steps laid out in the AWS Setup document before proceeding.

Deploy to Beanstalk

Create Beanstalk Environment

  1. Go to the Beanstalk Service in the AWS console
  2. Select Create New Application
  3. Give it a name and description (e.g. DuraCloud Management Console)
  4. Click Create web server
  5. Select Tomcat platform, Tomcat 8.5 with Corretto 11 running on 64bit Amazon Linux 2 platform branch and 4.1.7 version
  6. Select the Sample application (it will be replaced by DuraCloud apps in a later step), and keep the default deployment preferences
  7. Take defaults for environment name and URL (or update them if you'd prefer.) The environment URL must be unique.
  8. Leave additional resources unchecked
  9. Click on Configure more options
  10. Under Presets click high availability
  11. Edit VPC section and select your VPC and subnets and click save
  12. Edit Load Balancer select application load balancer. Add a listener with https, port 443 and your *. certificate. Edit the default process and change the health check path to /login
  13. Edit Manage Updates disable managed updates.
  14. Click "Edit" in the Software section and select Apache under Container Options and enter the following Environmental Variables:
  15. Edit Capacity 0. select Load balanced Environment type 0. min instances to 2 0. max instances to5 0. m5.large instance type 0. scaling cooldown to 360. 0. Scaling Triggers: * Metric: CPUUtilization * Statistic: Average * Unit: Percent * Period: 1 * Breach Duration: 5 * Upper threshold: 70 * Scale up Increment: 1 * Lower threshold: 20 * Scale-down increment: -1
  16. EditNotifications, enter an email address
  17. Edit Security, set your keypair and IAM instance profile
  18. Edit Monitoring
    • Enable Ignore application 4xx
    • Enable Ignore load balancer 4xx
  19. Click Create Environment
  20. Navigate to Configuration -> Software and set the followiwng:
    • jvm command line params: -Dduracloud.home=/tmp/duracloud-home -Dmc.config.file=s3://<your-s3-config-bucket>/path-to-duracloud-properties-file

You are now ready to deploy the DuraCloud beanstalk zip. You can do so by following the instruction in "Deploy to Production" detailed in this document.

  1. Build the latest tagged release of the management-console 
    git clone https://github.com/duracloud/management-console.git
cd management-console
mvn clean install -DskipTests -DskipIntTests -DskipDeploy
  2. Upload the account-management-app/target/ama-.war to Beanstalk (Application Versions).

Configure Management Console

Create a root user

  1. Create a user by clicking on the new user link on the management console login page.
  2. Make the newly created user a root user by logging directly into the duracloud_accounts database and runing the following command: update duracloud_user set root = true;

Configure Mill properties

  1. Login into the management console.
  2. Click on Root Console in the upper right hand corner of window.
  3. Click on DuraCloud Mill tab.
  4. Enter the requested mill database fields.
  5. Enter "auditlogs" for the Audit Log Space Id
  6. In a separate window, log into the aws console and navigate to SQS. Note the name of the queue ending in "_audit" and enter that into the DuraCloud Mill form you were just working on.
  7. Click Ok

Configure Global Properties

  1. Click on the Global Properties tab.
  2. In a separate tab go into the AWS SNS console, copy the topic ARN for the duracloud-account-topic for the topic your created in the SNS step in the AWS Setup document, and paste into the Instance Notification Topic ARN field.
  3. Retrieve your CloudFront account id, the access key id and s3 path to your CloudFront key. These values you set aside in the CloudFront Key generation step in the AWS setup document and plug them into their respecitive fields in the form.
  4. Now you are ready to start creating accounts. The first account you create should be the account that will be used to store and access your auditlogs and duplication-policy-repo, as noted in the instructions for the (duplication-policy-editor](mill-setup.md#deploy-the-duplication-policy-editor)