We are attempting to switch over the way we store and serve our add-ons to AWS. We've using Jive Hosted add ons up until this point.

My theory on how this would work would be to:

1. Create an app with 'jive-sdk create app' that gives all the necessary meta data and files for jive add ons.

2. Somewhere in this created file structure add a reference to the URL that AWS gives for an s3 bucket.

3. Create extension with "jive-sdk build add-on"

4. Upload extension to Add-Ons in instance

This method seems logical on keeping things updated seemlessly without having to upload the add on every single time there is a change. In this way, I'd just have to update the files through AWS and anywhere my add on/tool is reference will get updated automatically.

Has anyone attempted to have their front end hosted on AWS (S3 etc) and have it successfully be served in an uploaded add on? Can you help point me in the areas in the jiveconfiguration or defintion or xml files I might need to update with the bucket URL?

Data Provider

If you want to create a Jive-hosted custom view tile, you must specify a local URL for the "view" property (and for the "config" property if you have a configuration UI), and specify that your tile is "internal" using the following JSON property within your tile definition:

"dataProviderKey": "internal"

This allows you to create a tile without the need for an integration service.

On the other hand, if you want to host a service, simply omit this dataProviderKey property and specify an http URL for the "view" value in definition.json.