From f9d9c12f532c882a666ac49513c7403c30c5df5e Mon Sep 17 00:00:00 2001
From: trentmc <5305452+trentmc@users.noreply.github.com>
Date: Sun, 25 Oct 2020 15:57:46 +0100
Subject: [PATCH] say 'not ready yet for s3'

---
 content/tutorials/amazon-s3-for-brizo.md  | 2 ++
 content/tutorials/on-premise-for-brizo.md | 4 +++-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/tutorials/amazon-s3-for-brizo.md b/content/tutorials/amazon-s3-for-brizo.md
index 62b4574a..13f2d9e7 100644
--- a/content/tutorials/amazon-s3-for-brizo.md
+++ b/content/tutorials/amazon-s3-for-brizo.md
@@ -3,6 +3,8 @@ title: Set Up Amazon S3 Storage
 description: Tutorial about how to set up Amazon S3 storage for use with Ocean Protocol.
 ---
 
+*Note: This needs updating for Ocean V3. As a workaround: Brizo has been renamed to provider-py; it should work similarly.*
+
 To enable Brizo to use files stored in Amazon S3 (i.e. files with an URL containing `s3://`), you must:
 
 1. have an Amazon AWS user account (IAM account) with permission to read those files from S3, and
diff --git a/content/tutorials/on-premise-for-brizo.md b/content/tutorials/on-premise-for-brizo.md
index f2d141a9..511e7543 100644
--- a/content/tutorials/on-premise-for-brizo.md
+++ b/content/tutorials/on-premise-for-brizo.md
@@ -1,8 +1,10 @@
 ---
 title: Set Up On-Premise Storage
-description: Tutorial about how to set up on-premise storage for use with Ocean Protocol.
+description: Tutorial about how to set up on-premise storage for use with Ocean.
 ---
 
+*Note: This needs updating for Ocean V3. As a workaround: Brizo has been renamed to provider-py; it should work similarly.*
+
 To enable Brizo to use files stored in on-premise storage (i.e. files with an URL not containing `core.windows.net` or `s3://`), there is _nothing to do, other than make sure Brizo can resolve the URLs_. In particular, you don't have to set any Brizo-specific configuration settings, e.g. in the `[osmosis]` section of the Brizo config file or in some special Brizo environment variables.
 
 Local and private network URLs are fine so long as they can be resolved by Brizo. Potential examples include `http://localhost/helicopter_data.xls`, `http://192.168.12.34/almond_sales_2012.csv` and `http://10.12.34.56/duck_photos.zip`.