JavaScript File Not Loading in AEM Instance (Hosted on AWS)

[datnguyenfiserv]

We are experiencing an issue where a specific JavaScript file is not loading properly in our AEM environment. The issue persists even after restarting the AEM instances hosted on AWS.

The JS file is either not loading at all or returning a 404 error. We have verified that the file exists in the repository. Restarting the AEM instances did not resolve the issue. No recent changes were made to the file or its path. The file has been published and activated in AEM publisher and author.

Path of the JS file in AEM: etc/designs/chase-demo/clientlibs.min.js.

[HrishikeshKagne]

Hi @datnguyenfiserv ,

In AEM as a Cloud Service (and newer AEM versions), anything under /etc/designs is deprecated and no longer accessible. That’s why your JS file returns 404.

The fix is to move your client library to /apps/<project>/clientlibs or /apps/<project>/frontend, and include it using the recommended cq:clientLibraryFolder structure. Then deploy and reference it via the granite:ClientLibInclude tag or clientlib categories.

don’t use /etc/designs migrate the JS to /apps/clientlibs and re-include it. That will resolve the loading issue.

[kautuk_sahni]

@datnguyenfiserv just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!