At this point, the only release of the TDS that supports S3 storage is
5.0.0-beta8 (and a few previous snapshot versions), and is currently
limited to serving individual objects. I believe simple (non-scanning) NcML
aggregations should work as well (they do in netCDF-Java, but I have not
tried using it directly in a TDS configuration catalog).
On Fri, Jun 19, 2020 at 7:50 AM Jesper Baasch-Larsen <jbl@xxxxxxxxxxxxxx>
> Hi THREDDS people
> I am trying to run THREDDS with this catalog.xml file:
> using the unidata/thredds-docker:4.6.15 docker image which I believe
> should support using S3 as a storage backend.
> But I get this error in catalogInit.log:
> You are currently running TDS version 4.6.15 - 2020-06-16T13:36:16-0600
> Latest Available TDS Version Info:
> latest development version = 5.0.0-beta8
> latest stable version = 4.6.15
> initCatalogs(): initializing 1 root catalogs.
> Catalog init catalog.xml
> initCatalog catalog.xml -> /usr/local/tomcat/content/thredds/catalog.xml
> -------readCatalog(): full
> path=/usr/local/tomcat/content/thredds/catalog.xml; path=catalog.xml
> ----Catalog Validation
> *** ERROR DataRootConfig path =s3-test directory= <cdms3:noaa-goes16/>
> does not exist
> add static catalog to hash=catalog.xml
> Did I misconfigure something?
> Best Regards
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
> thredds mailing list
> For list information or to unsubscribe, visit: