Copy link to clipboard
Copied
Looking through the docs and some example code in github for the InDesing APIs through Firefly services I can see that the input/output assets list AWS S3, Dropbox, and Azure as the supported assets. However it looks like these are just utilizing signed/ pre-signed URLs, and they are not the only cloud services which support this style of access to assets.
Is it possible to use a different cloud storage system for assets with Firefly InDesign APIs assuming it can generate a signed url for use by the Adobe backends? Specifically I want to know if it is possible to utilize these APIs with signed URLs for Google Cloud Storage assets.
From the reading the docs, I strongly doubt this would work as is, since there's likely a domain based whitelist for these assets. But I'm especially curious if it's feasible to get a domain whitelisted.
Context
I'm working on a design for automating some manual steps in a workflow where we convert INDD to IDML. I'm considering either Firefly Services InDesign API or InDesign Server. But neither fits the requirements exactly. Specifically: I may have a hard requirement for assets to be stored in Google Cloud Storage, and there's a very strong preference for not self-hosting a Windows machine to handle this conversion.
This may not be the correct channel to pose this question, if there's a better avenue let me know.
Copy link to clipboard
Copied
Last I checked Firefly was in beta, so did you try contacting folks who got you access to the service? Looking at the Github page I see a slack channel for support, check that out https://github.com/AdobeDocs/ff-services-docs/tree/main
-Manan
Copy link to clipboard
Copied
... Looking at the Github page I see a slack channel for support, check that out https://github.com/AdobeDocs/ff-services-docs/tree/main
Unfortunately that Slack channel is internal to Adobe...
Copy link to clipboard
Copied
HI @erinferinferinf so this is sitll in Beta? What would be the best way to get help in such a case?
-Manan
Copy link to clipboard
Copied
Thanks for the replies.
@Manan Joshi I didn't realize it may be in Beta. I don't remember reading that in the docs. This is something I'd need to know as well.
I don't currently have access to the service so I have been struggling to find a resource internal to my organization that can help me find a good point of contact at Adobe. It's possible some other teams have used some of the Adobe APIs but I'm not sure.
The biggest question I have is around whether it's possible to get support for whitelisting a new domain for input/output assets for the InDesign API in Firefly services. Though if they are in Beta as Manan said, I'm also curious what the launch timeline looks like. Anyway, this may still not be the best place to ask this, but I'm not sure where is.
Copy link to clipboard
Copied
@artistic_Brilliance2906 I had applied for access for this service sometime back and I had got it. Since then I did not follow up, I was curious about pricing and exactly how this would be different from InDesign Server in terms of pricing and all. I thought after this is out of beta this information would be made public. However, I did not find any information of this going live or being used by someone in production
-Manan
Copy link to clipboard
Copied
Currently Firefly InDesign APIs only support the documented storage providers (AWS S3, Dropbox, Azure) and they do enforce domain whitelisting on signed URLs. You can’t just swap in Google Cloud Storage links unless Adobe adds support. If GCS is a hard requirement, your options are either proxying assets through a supported storage backend or going with InDesign Server. For an official answer or to request GCS whitelisting, the right channel is Adobe’s developer support / Adobe I/O forums.
Copy link to clipboard
Copied
... For an official answer or to request GCS whitelisting, the right channel is Adobe’s developer support / Adobe I/O forums.
If you mean this forum: https://experienceleaguecommunities.adobe.com/t5/adobe-developer/ct-p/adobe-io
I don't think you'll find the answer you're looking for there...
Copy link to clipboard
Copied
Thanks for the response. I understand that just substituting the URL would not work. Even if it did, it's outside of the documented spec so I wouldn't rely on it anyway. I understand the rest of what you said as well. The issue with other storage is policy, not technical, so proxying through another storage does not solve that problem sadly. InDesign server may be the only viable solution, but I want to cover my bases.
the right channel is Adobe’s developer support / Adobe I/O forums.
Are you referring to the paid dev support here https://helpx.adobe.com/support/programs/cc-exchange-developer-support.html ?
Since that appears to be sepcifically for Creative Cloud dev support, I wasn't sure that was the correct channel since I'm specifically talking about the APIs under Firefly Services.
Copy link to clipboard
Copied
Additionally, per the documentation changes in the last month or so, it looks like they have added support for GCP output from Firefly InDesign API:
I'd guess that means that input assets are also on the roadmap, but who knows. I'd love to get some concrete info on that.
I also just noticed an email at the top of these docs: https://developer.adobe.com/firefly-services/docs/indesign-apis/api/scripts/ So I'll try reaching out there.
Copy link to clipboard
Copied
Hi Please check out the updated documentation for InDesign API. Adobe do support Google Cloud storage as input for InDesign API. Only If there is an custom domain present that require to be added in allowedlist.
Copy link to clipboard
Copied
Thanks! I saw that recent change in the documentation yesterday. It's great to hear that input assets are now supported. I'm still curious if Google Cloud Storage output assets are on the roadmap as well. Do you happen to have any info on that, or know of a good channel for me to ask about that?
I tried emailing idservices@adobe.com, which is listed at the top of the InDesign APIs docs, but I received a message couldn't be delivered error, due to not being on the allowed senders list.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now