Authentication for Linked Resources in Storyline Package

We use Storyline to create and publish content to our LMS (we are currently using Totara). Historically, we have take the approach of attaching local files to our SCORM packages before exporting them to be published on the web. Using this approach, files that we link to from our SCORM packages are protected behind the LMS' authentication. However, the downside of using this approach is that when there are updates to these ancillary materials, we have to re-publish the SCORM in any and all courses where it's referenced. 

 

To try to solve this problem, we're exploring linking to resources referenced in the SCORM package via an s3 bucket link instead -- meaning there'd be a live link between the SCORM and the linked resource and we'd only have to updated ancillary materials one time. While this will be a time saver, we've hit a roadblock in better protecting this content. 

 

Has anyone had a similar problem? If so, any ideas on how we could get the benefit of not having to re-publish our SCORM packages every time there's an ancillary material update while not losing at least some basic protection of the intellectual property we may point users to?

 

Appreciate any help or thoughts!