Preliminaries

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 itas described in SHRINE 4.1.0 Chapter 8 - SHRINE's Configuration .

Configure the Hub's shrine.conf

...

shrine {
  network {
    network {
      name = "Network Name"
      hubQueueName = "hub"
      adminEmail = "yourEmail@yourhospital.edu"
      momId = "arn:aws:iam::1234567890:user/your-hub"
      aws.sqs = {
        queueOwnerAWSAccountId = "1234567890" //Digits
        networkPrefix = "shrinebest-devnetwork"
        region = "us-east-1"
      }
    }
    nodes = [
      {
        name = "Hub's node"
        key = "hub-node"
        userDomainName = "network-hub"
        queueName = "hubNode"
        sendQueries = "false"
        adminEmail = "yourEmail@yourhospital.edu"
        momId = "arn:aws:iam::1234567890:user/your-hub"
      }
    ]
  }
}

The hub owns all of the AWS SQS queues. Find the queue owner's account ID by TODO- all digits - in the upper right corner of the AWS IAM console page.

Choose a network prefix. This will be prepended to queue names to allow managing multiple networks in the same AWS account.

Use AWS IAM identity names of the account to receive the messages for the momId. Find this by TODOon the AWS IAM > Users > user page.

Note that the network's momId is the same as hub's node momId. Each downstream node will have its own AWS AIM identity from its own AWS account.

...