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
The official AWS S3 file storage adapter for Parse Server. See [Parse Server S3 File Adapter Configuration](https://docs.parseplatform.org/parse-server/guide/#configuring-s3adapter) for more details.
-[passing as an instance](#passing-as-an-instance)
24
+
-[Usage with Digital Ocean Spaces](#usage-with-digital-ocean-spaces)
25
+
-[Adding Metadata and Tags](#adding-metadata-and-tags)
26
+
27
+
# Installation
12
28
13
29
`npm install --save @parse/s3-files-adapter`
14
30
15
31
# AWS Credentials
16
32
17
-
## Deprecation Notice -- AWS Credentials
18
-
*the ability to explicitly pass credentials to this adapter is deprecated and will be removed in a future release.*
33
+
⚠️ The ability to explicitly pass credentials to this adapter is deprecated and will be removed in a future release.
19
34
20
35
You may already be compatible with this change. If you have not explicitly set an `accessKey` and `secretKey` and you have configured the environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`, then you're all set and this will continue to work as is.
21
36
@@ -41,6 +56,7 @@ For an AWS host:
41
56
If for some reason you really need to be able to set the key and secret explicitly, you can still do it using `s3overrides` as described below and setting `accessKeyId` and `secretAccessKey` in the `s3Overrides` object.
42
57
43
58
# Deprecated Configuration
59
+
44
60
Although it is not recommended, AWS credentials can be explicitly configured through an options
45
61
object, constructor string arguments or environment variables ([see below](#using-a-config-file)).
46
62
This option is provided for backward compatibility and will be removed in the forthcoming version 2.0 of this adapter.
0 commit comments