Please make sure that you have followed all of the steps laid out in the AWS Setup document before proceeding.
- Go to Beanstalk Service
- Create application
- Give it a name and description (e.g. Management Console)
- Click create web server
- Select "tomcat" platform and "load balancing" environment
- Click through defaults until you reach the configuration details and select m3.large instance, your keypair, basic health reporting, and root volume device of 30 GiB with General Purpose SSD.
- Select the IAM instance role you set up previously (ie
management-console
). - Launch the environment.
- Navigate to environment -> configuration -> software configuration
- jvm command line params:
-Dduracloud.home=/tmp/duracloud-home -Dmc.config.file=s3://<your-s3-config-bucket>/path-to-duracloud-properties-file
- environment params:
- key: S3_CONFIG_BUCKET
- value:
<your-s3-config-bucket>
- Set min/max instance counts to 2 and 3 respectively.
- Under scaling trigger section:
- Trigger measurement: CPU Utilization
- Trigger statistic: average
- Unit of measurement: percent
- Measurement period: 1
- Breach duration: 1
- Upper threshold: 80
- Upper breach scale: 1
- Lower threshold: 20
- Lower breach scale: -1
- Secure listener port: 443
- Navigate to "Load Balancing"
- Select SSL Certificate
- Select session stickiness
- Click
Apply
- Navigate to EC2 -> load balancers
- Under port configuration enable "load balancer generated cookie stickiness" for ports 80 and 443.
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.
- 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
- Upload the account-management-app/target/ama-.war to Beanstalk (Application Versions).
- Create a user by clicking on the new user link on the management console login page.
- 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;
- Login into the management console.
- Click on
Root Console
in the upper right hand corner of window. - Click on
DuraCloud Mill
tab. - Enter the requested mill database fields.
- Enter "auditlogs" for the Audit Log Space Id
- 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.
- Click
Ok
- Click on the
Global Properties
tab. - 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 theInstance Notification Topic ARN
field. - 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.
- 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)