ERROR [proxy:start] sqsQueueNameTemplate is invalid!

This article applies to:

  • Onboarding/Proxy Data Buffering
  • Product edition:Proxy 9.0 and later.
  • Feature Category: Proxy. 


Problem Description:

Starting with Proxy version 9 and later, it was added the option for users to add an SQS -  AWS Simple Queue Service - for the proxy to send data to the SQS instead of buffering the data to the local on-disk when there is a data outage or when proxies are backing up.


Upon times, this set up may fail mainly due to configuration issues on the either of the following Proxy settings:   sqsBuffersqsQueueNameTemplatesqsQueueIdentifier, and sqsQueueRegion


One of the errors you may find on the Log File  is the following:


2022-04-25 19:45:32,758 ERROR [proxy:start] sqsQueueNameTemplate is invalid! Must contain {{id}} {{entity}} and {{port}} replacements.

java.lang.IllegalArgumentException: sqsQueueNameTemplate is invalid! Must contain {{id}} {{entity}} and {{port}} replacements.


Note: The preceding log excerpts/Messages are only examples. Date, time, and environmental variables may vary depending on your environment.



The information placed next to sqsQueueNameTemplate property is not matching the expected syntax as per



When viewing the suggested pattern:  wf-proxy-{{id}}-{{entity}}-{{port}} that, for example, it results in a queue named wf-proxy-id-points-2878 we need to leave Only 1 set of curly brackets for each section and fill out with what would be the baseline of the template.

So, if we use the above example, it should actually look like  wf-proxy-{id}-{points}-{2878} when entering it on the Conf file.


See also:

Data Buffering 

[INTERNAL] How to Remove Queued Data at the Proxy 

[INTERNAL] How to export data queued at the Aria Operations for Applications Proxy 



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk