Merge pull request #2561 from magento-devdocs/hg-cloud-issues

Fix remote storage related to Cloud
Fix /pull/9144

Author: hguthrie

src/cloud/docker/docker-mode-developer.md

@@ -29,7 +29,7 @@ Large files (>1 GB) can cause a period of inactivity. DB dumps and archive files
 {:.procedure}
 To launch the Docker environment in developer mode:
 
-1. In your local environment, generate the Docker Compose configuration file. You can use the service configuration options, such as `--php`, to [specify a version][services].
+1. In your local project root, generate the Docker Compose configuration file. You can use the service configuration options, such as `--php`, to [specify a version][services].
 
    ```bash
    ./vendor/bin/ece-docker build:compose --mode="developer"
@@ -41,7 +41,7 @@ To launch the Docker environment in developer mode:
    ./vendor/bin/ece-docker build:compose --mode="developer" --sync-engine="mutagen"
    ```
 
-   {:.bs-callout-info}
+   {:.bs-callout-tip}
    You can further customize the Docker Compose configuration file by adding additional options to the `build:compose` command. For example, you can set the software version for a service, or add Xdebug configuration. See [service configuration options].
 
 1. _Optional_: If you have a custom PHP configuration file, copy the default configuration DIST file to your custom configuration file and make any necessary changes.
@@ -56,9 +56,9 @@ To launch the Docker environment in developer mode:
    docker-compose up -d
    ```
 
-1. If you selected the `manual-native` option, start the file synchronization using the following commands.
+1. If you selected the `manual-native` option, start the file synchronization.
 
-   **This command copies all data from the local machine to the Docker volume:**
+   **To copy all data from the local machine to the Docker volume:**
 
    ```bash
    ./bin/magento-docker copy-to --all
@@ -71,7 +71,7 @@ To launch the Docker environment in developer mode:
    ./bin/magento-docker copy-to vendor
    ```
 
-   **To copy all data from the Docker volume to the local machine, use:**
+   **To copy all data from the Docker volume to the local machine:**
 
    ```bash
    ./bin/magento-docker copy-from --all
@@ -136,7 +136,7 @@ To launch the Docker environment in developer mode:
    docker-compose run --rm deploy magento-command cache:clean
    ```
 
-1. Access the local Magento Cloud template by opening one of the following URLs in a browser:
+1. Access the local storefront by opening one of the following URLs in a browser:
 
    -  `http://magento2.docker`
 

src/cloud/docker/docker-mode-production.md

@@ -78,7 +78,7 @@ To launch the Docker environment in production mode:
    docker-compose restart
    ```
 
-1. Access the local Magento Cloud template by opening one of the following URLs in a browser:
+1. Access the local storefront by opening one of the following URLs in a browser:
 
    -  `http://magento2.docker`
 

src/cloud/env/variables-deploy.md

@@ -392,26 +392,6 @@ You must have a Redis service configured in the `.magento.app.yaml` file and in
 
 The read-only connection is not available for use in the Integration environment or if you use the [`CACHE_CONFIGURATION` variable](#cache_configuration).
 
-### `REMOTE_STORAGE`
-
--  **Default**—_Not set_
--  **Version**—{{site.data.var.ee}} 2.4.2 and later
-
-Configure a _storage adapter_ to store media files in a persistent, remote storage container using a storage service, such as AWS S3. Use the remote storage option to improve performance on Cloud projects with complex, multi-server configurations that must share resources.
-
-```yaml
-stage:
-  deploy:
-    REMOTE_STORAGE:
-      driver: aws-s3 # Required
-      prefix: cloud # Optional
-      config:
-        bucket: my-bucket # Required
-        region: my-region # Required
-        key: my-key # Optional
-        secret: my-secret-key # Optional
-```
-
 ### `RESOURCE_CONFIGURATION`
 
 -  **Default**—Not set

src/cloud/release-notes/ece-release-notes.md

@@ -42,7 +42,7 @@ See [Upgrades and patches]({{ site.baseurl }}/cloud/project/project-upgrade-pare
 ## v2002.1.5
 *Release date: Feb 1, 2021*<br/>
 
--  {:.new}**Remote storage**—Added the [`REMOTE_STORAGE`]({{site.baseurl}}/cloud/env/variables-deploy.html#remote_storage) environment variable to enable Cloud Projects for remote storage of media files using a storage service, such as AWS S3.<!--MCLOUD-7153-->
+-  {:.new}**Remote storage**—Added the `REMOTE_STORAGE` environment variable to enable Cloud Projects for remote storage of media files using a storage service, such as AWS S3. This configuration option is part of the {{site.data.var.ct}} package, but is not supported on {{site.data.var.ece}}.<!--MCLOUD-7153-->
 
 -  {:.new}**New cloud:config:validate command**—Added command `php vendor/bin/ece-tools cloud:config:validate` to validate the `.magento.env.yaml` configuration before pushing changes to the remote Cloud environment.<!--MCLOUD-7120-->
 

src/guides/v2.4/config-guide/remote-storage/config-remote-storage.md

@@ -12,6 +12,9 @@ The Remote Storage module provides the option to store media files and schedule
 {:.bs-callout-info}
 Remote storage is available in version 2.4.2 and later only. See the [2.4.2 release notes]({{page.baseurl}}/release-notes/open-source-2-4-2.html).
 
+{:.bs-callout-info}
+The Remote storage module is _not_ supported on {{site.data.var.ece}}.
+
 ![schema image]
 
 ## Remote storage options
@@ -78,7 +81,7 @@ After you enable remote storage for a specific adapter, you can use the CLI to m
 ```
 
 {:.bs-callout-info}
-The sync command only migrates files in the `pub/media` directory, _not_ the import/export files in the `var` directory. See [Scheduled Import/Export][import-export] in the _Magento 2.4 User Guide_.
+The sync command only migrates files in the `pub/media` directory, _not_ the import/export files in the `var` directory. See [Scheduled Import/Export][import-export] in the _Commerce 2.4 User Guide_.
 
 <!-- link definitions -->
 [AWS S3]: {{site.baseurl}}/guides/v2.4/config-guide/remote-storage/config-remote-storage-aws-s3.html