There is no clear solution but 2 workarounds: Workaround 1:Only for dev and stage domains, we can use custom path for robots.txt, e.g. https://publish-pxxxx-exxxx.adobeaemcloud.com/my-path/robots.txt  - which shows custom robots file.Workaround 2:Configure custom domain names for dev and stage envs ...

Still doesn't work - Another observation: /robots.txt - shows Adobe's default file. but //robots.txt - shows the custom one that we want.

its AEM as a cloud service, so not possible to hit the publisher directly.

thanks @konstantyn_diachenko , but it didn't work...

thanks, yes this seems like cached at CDN level, this is AEM as a Cloud service and we are using Adobe bundled fastly CDN. so when i try publish+dispatcher url, its always with CDN. how to bypass CDN? 

Hello, We are implementing custom robots.txt which will be maintainable by content authors. the file is located in: "/content/dam/mycompany/config/robots.txt" We implemented following Dispatcher changes and deployed to AEMaaCS env: 1. filters.any# Allow robots.txt /0104 { /type "allow" /url "/conten...

@narendiran_ravi thanks a lot, marking this as accepted solution.

Hello, For our project we require a connection to be made to a SFTP server. We managed to get this to work locally, OSGI picks the newly included Jsch JAR and we where able to establish a SFTP connection and perform the required operations. However, The AEMaaCS(2025.3.19823.20250304T101418Z) build p...