Page History
...
Create two IAM accounts: an admin to set up and modify the network using the shrineNetworkLifecycle command line tool, and one for the hub tomcat process to use to send and receive messages. That admin account will need : TODO - and how to do it
Configure the Hub's shrine.conf
In tomcat's shrine.conf in the hub, turn off the in-tomcat messaging by setting shrine.hub.messagequeue.blockingWebApi.enabled to it's default false value by removing it from the hub block:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
shrine {
...
hub {
create = true
}//hub
...
}//shrine
|
Tomcat will need the hub's AWS SQS credentials to send and receive messages. Add your access ID and secret to tomcat's password.conf:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
shrine.aws.accessKeyId = "HUBAWSKEYID" //the hub's AWS access key id - usually all capitals and numbers shrine.aws.secretAccessKey = "hubAwsSecretKey" //the hub's AWS secret key - very long, mixed case letters and numbers |
Configure shrineNetworkLifecycle
The shrineNetworkLifecycle needs some additional configuration to use the AWS admin account. In In its
network.conf
Overview
Content Tools