...

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:

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 its the admin AWS credentials to create, modify, and delete AWS SQS Queues. Add that to the shrineNetworkLifecycle's conf/password.conf :

shrine.aws.accessKeyId = "ADMINAWSKEYID" //the admin AWS access key id - usually all capitals and numbers
shrine.aws.secretAccessKey = "AdminAwsSecretKey" //the admin AWS secret key - very long, mixed case letters and numbers

network.conf