You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ecommerce-applications/magento-2/how-to-configure-remote-storage-for-magento-2-x.md
+95-33Lines changed: 95 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -70,47 +70,109 @@ Magento's S3 implementation creates a test file called `storage.flag`, which is
70
70
71
71
## Serving assets from your S3 bucket
72
72
73
-
To start serving media assets from your S3 bucket, you need to make some adjustments to your nginx configuration.
74
-
75
-
We recommend that you create a configuration file `/data/web/nginx/http.asset_proxy_cache.conf` defining the cache storage location, structure, size constraints, and cache expiration policies.
73
+
To start serving media assets from your S3 bucket, you need to make some adjustments to your nginx configuration. Create the following file at `/data/web/nginx/example.com/server.assets.conf` for each relevant vhost:
Keep in mind your bucket URL might be different depending on your AWS region. For example, you might need to change it to `https://s3.amazonaws.com/$bucket$uri` instead.
113
-
Also make sure your S3 bucket policies are configured correctly, so that only `/media` is publicly readable. For example:
174
+
Make sure to change the string `my_bucket_name` to the name of your bucket and keep in mind that your bucket URL might be different depending on your AWS region. For example, you might need to change it from `https://$bucket.s3.amazonaws.com$uri` to `https://s3.amazonaws.com/$bucket$uri` instead.
175
+
Furthermore, ensure that your S3 bucket policies are configured correctly, so that only `/media` is publicly readable. For example:
0 commit comments