After some reading and testing, I was able to figure out what to do.  It looks like a brand new installation of AEM 6.5 doesn't automatically create an "install" directory under the crx-quickstart directory.  Before starting AEM for the first time, I created a crx-quickstart/install directory and pl...

This new installation doesn't have a folder at "crx-quickstart/install", so I don't think I have an external data store. To reproduce my issue, I created a new directory, copied in the aem jar and my license.properties file, started up the instance, and then uploaded my 22GB package. The new instanc...

I looked under crx-quickstart, but there isn't an "install" directory there. Is that normally created by AEM after it starts up for the first time? I'm not sure why it wasn't in this case.

In case this is useful information: Under crx-quickstart/repository I have three directories: blobids, index, and segmentstore. Their combined size is around 6GB.

Or maybe a better question is: where can I view the configuration that tells me where the datastore directory is located?

Thanks for the quick reply!
I just checked the /system/console/status-Configurations page.  Am I correct that segment store is the default for a new AEM 6.5 instance?  This is what I'm seeing for Segment Store: 
PID = org.apache.jackrabbit.oak.segment.SegmentNodeStoreService  BundleLocation = Unboun...

[Removed duplicate comment]

I started up a brand new AEM 6.5 instance with no data in it and then successfully installed a 22GB content package.  The installed nodes are all showing up in CRXDE Lite, and I can download the 22GB package and its checksum matches the originally uploaded package.  However, when I run a du operatio...

Hi @smacdonald2008.  Just wanted to follow up to see if you were able to find anything by asking internally.  Thanks!

Although we are currently connecting internally in a DEV environment, we also wish to connect to non-local instances over HTTPS.  This example was just a first attempt with a local DEV instance.  Thank you for checking on this.