are you using a compatible version of Eclipse with AEM Developer Tools. Compatibility can change with different versions of AEM and Eclipse, so make sure you're using the recommended versions. else try to use other IDE such as IntelliJ IDEA with the Adobe IntelliJ Plugin.

i would suggest you to ask you Product Admin / see you user access to Adobe IO profile [https://adminconsole.adobe.com/], In case Adobe IO profile is not assigned to your username, ask Admin to assign product Adobe IO profile to your user name and provide role as "developer"

Thank you for details, it seems to be supported but i would think better approach would be using Cloud service Assets as it bring in performance capability - all the assets from the on prem can be ported to cloud instance - thoughts ?

Hi if you are using cloud service then might be your preview service is disabled/ blocked- check with adobe support or- refer page below to address IP allow list for Preview Service for each enviormenthttps://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using...

i am getting error while accessing API for cloud Manager -  Adobe IO cloud Manager project has been setup in Adobe IO console works fine using Postman and getting expected response on the API call.When i tried to replicate same in JS Code/Fetch call, getting below error has been blocked by CORS poli...

i am getting error while accessing API for cloud Manager -  Adobe IO cloud Manager project has been setup in Adobe IO console works fine using Postman and getting expected response on the API call.When i tried to replicate same in JS Code/Fetch call, getting below error has been blocked by CORS poli...

This is old thread but point to issue which still valid, i am also getting similar error. when i tried using Cloud Manager API via JS / Fetch cod  has been blocked by CORS policy: Request header field access-control-allow-methods is not allowed by Access-Control-Allow-Headers in preflight response. ...

adding working link as prior link leading to 404 https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/assets-cloud-changes.html

i am not sure there would any case like that, as Site and assets license mostly shipped together by Adobe if any I don't think there will be any risk here, asset would be delivered from cloud and would have some limitations like workflow introduced by Asset Compute Service/ part of asset cloud offer...

if it is related to AEM actual jar file , you might need to open a ticket with Adobe