[Sorry for the delayed response.]
The S3 work moved to the Unidata/netCDF-java repo in PR #173
<https://github.com/Unidata/netcdf-java/pull/173> ("S3 Support"). This PR
got merged into master a week or so ago and is available in the netCDF-Java
5.3.0-SNAPSHOT release (and will be in the upcoming 5.3.0 release). The
latest TDS code built with netCDF-Java 5.3.0-SNAPSHOT can be configured to
serve an individual netCDF file stored as an S3 object using a datasetRoot
<?xml version="1.0" encoding="UTF-8"?>
<catalog name="Test TDS S3"
<datasetRoot path="s3-test" location="s3://noaa-goes16" />
<dataset name="Test GOES-16 S3" ID="testS3Grid"
In this case, the datasetRoot location is the bucket name, and the urlPath
is the datasetRoot path combined with the key. We rely on the AWS Java SDK
(v2) to handle credentials, setting of region, etc. For now, you can set
the region by creating a credentials file ~/.aws/credentials that looked
Which is how netCDF-java knows which region to use for bucket access. We
may look at other mechanisms to make that a bit more integrated into TDS
configuration but for now that should work.
Once the netCDF 5.3.0 release comes out, TDS snapshot builds will be built
with this capability. For now, you would need to build the TDS and
explicitly tell it to build with netCDF-Java 5.3.0-SNAPSHOT.
On Tue, Feb 4, 2020 at 2:30 PM H. Joe Lee <hyoklee@xxxxxxxxxxxx> wrote:
> Is it possible to serve netCDF data on AWS S3 using THREDDS?
> I think it seems possible based on the S3 feature branch .
> If so, can someone share an example THREDDS catalog configuration?
>  https://github.com/Unidata/thredds/tree/feature/s3+hdfs
> 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: