Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork87
AWS S3 file storage adapter for Parse Server
License
parse-community/parse-server-s3-adapter
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
The official AWS S3 file storage adapter for Parse Server. SeeParse Server S3 File Adapter Configuration for more details.
- Getting Started
- Usage with Parse Server
- Compatibility with other Storage Providers
- Migration Guide from 3.x to 4.x
npm install --save @parse/s3-files-adapter
Parse Server S3 Adapter is compatible with the following versions of Parse Server.
Parse Server Version | End-of-Life | Compatible |
---|---|---|
<=5 | December 2023 | ❌ No |
6 | December 2024 | ❌ No |
<7.3.0 | December 2025 | ❌ No |
>=7.3.0 | December 2025 | ✅ Yes |
Parse Server S3 Adapter is continuously tested with the most recent releases of Node.js to ensure compatibility. We follow theNode.js Long Term Support plan and only test against versions that are officially supported and have not reached their end-of-life date.
Node.js Version | End-of-Life | Compatible |
---|---|---|
18 | April 2025 | ✅ Yes |
20 | April 2026 | ✅ Yes |
22 | April 2027 | ✅ Yes |
You may already be compatible with this change. If you have not explicitly set anaccessKey
andsecretKey
and you have configured the environment variablesAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
, then you're all set and this will continue to work as is.
If you explicitly configured the environment variablesS3_ACCESS_KEY
S3_SECRET_KEY
OR
If you explicitly configured theaccessKey
andsecretKey
in your adapter configuration, then you'll need to...
For non AWS hosts:
- Run
aws configure
in a terminal which will step you through configuring credentials for the AWS SDK and CLI
For an AWS host:
- Ensure that the role that your host is running as has permissions for your s3 bucket
Then
- remove the
accessKey
andsecretKey
from your configuration
If for some reason you really need to be able to set the key and secret explicitly, you can still do it usings3overrides
as described below and settingaccessKeyId
andsecretAccessKey
in thes3Overrides
object.
Although it is not recommended, AWS credentials can be explicitly configured through an optionsobject, constructor string arguments or environment variables (see below).This option is provided for backward compatibility and will be removed in the forthcoming version 2.0 of this adapter.
The preferred method is to use the default AWS credentials pattern. If no AWS credentials are explicitly configured, the AWS SDK will look for credentials in the standard locations used by all AWS SDKs and the AWS CLI. More info can be found inthe docs. For more information on AWS best practices, seeIAM Best Practices User Guide.
(This list is still incomplete and in the works, in the meantime find more descriptions in the chapters below.)
Parameter | Optional | Default value | Environment variable | Description |
---|---|---|---|---|
fileAcl | yes | undefined | S3_FILE_ACL | Sets theCanned ACL of the file when storing it in the S3 bucket. Setting this parameter overrides the file ACL that would otherwise depend on thedirectAccess parameter. Setting the value'none' causes any ACL parameter to be removed that would otherwise be set. |
presignedUrl | yes | false | S3_PRESIGNED_URL | Iftrue apresigned URL is returned when requesting the URL of file. The URL is only valid for a specified duration, see parameterpresignedUrlExpires . |
presignedUrlExpires | yes | undefined | S3_PRESIGNED_URL_EXPIRES | Sets the duration in seconds after which thepresigned URL of the file expires. If no value is set, the AWS S3 SDK defaultExpires value applies. This parameter requirespresignedUrl to betrue . |
{ "appId": 'my_app_id', "masterKey": 'my_master_key', // other options "filesAdapter": { "module": "@parse/s3-files-adapter", "options": { "bucket": "my_bucket", // optional: "region": 'us-east-1', // default value "bucketPrefix": '', // default value "directAccess": false, // default value "fileAcl": null, // default value "baseUrl": null, // string, function or async function "baseUrlDirect": false, // default value "signatureVersion": 'v4', // default value "globalCacheControl": null, // default value. Or 'public, max-age=86400' for 24 hrs Cache-Control "presignedUrl": false, // Optional. If true a presigned URL is returned when requesting the URL of file. The URL is only valid for a specified duration, see parameter `presignedUrlExpires`. Default is false. "presignedUrlExpires": null, // Optional. Sets the duration in seconds after which the presigned URL of the file expires. Defaults to the AWS S3 SDK default Expires value. "ServerSideEncryption": 'AES256|aws:kms', //AES256 or aws:kms, or if you do not pass this, encryption won't be done "validateFilename": null, // Default to parse-server FilesAdapter::validateFilename. "generateKey": null // Will default to Parse.FilesController.preserveFileName } }}
Note By default Parse.FilesController.preserveFileName will prefix all filenames with a random hex code. You will want to disable that if you enable it here or wish to use S3 "directories".
Set your environment variables:
S3_BUCKET=bucketName
the following optional configuration can be set by environment variable too:
S3_SIGNATURE_VERSION=v4
And update your config / options
{ "appId": 'my_app_id', "masterKey": 'my_master_key', // other options "filesAdapter": "@parse/s3-files-adapter"}
var S3Adapter = require('@parse/s3-files-adapter');var s3Adapter = new S3Adapter( 'accessKey', 'secretKey', 'bucket', { region: 'us-east-1' bucketPrefix: '', directAccess: false, baseUrl: 'http://images.example.com', signatureVersion: 'v4', globalCacheControl: 'public, max-age=86400', // 24 hrs Cache-Control. presignedUrl: false, presignedUrlExpires: 900, validateFilename: (filename) => { if (filename.length > 1024) { return 'Filename too long.'; } return null; // Return null on success }, generateKey: (filename) => { return `${Date.now()}_${filename}`; // unique prefix for every filename } });var api = new ParseServer({ appId: 'my_app', masterKey: 'master_key', filesAdapter: s3adapter})
Note: there are a few ways you can pass arguments:
S3Adapter("bucket")S3Adapter("bucket", options)S3Adapter("key", "secret", "bucket") -- Deprecated, see notice aboveS3Adapter("key", "secret", "bucket", options) -- Deprecated, see notice aboveS3Adapter(options) // where options must contain bucket.S3Adapter(options, s3overrides)
If you use the last form,s3overrides
are the parameters passed toAWS.S3.
In this form if you sets3overrides.params
, you must set at leasts3overrides.params.Bucket
or with an options hash
var S3Adapter = require('@parse/s3-files-adapter');var s3Options = { "bucket": "my_bucket", // optional: "region": 'us-east-1', // default value "bucketPrefix": '', // default value "directAccess": false, // default value "baseUrl": null // string, function or async function "signatureVersion": 'v4', // default value "globalCacheControl": null, // default value. Or 'public, max-age=86400' for 24 hrs Cache-Control "presignedUrl": false, // default value "presignedUrlExpires": 900, // default value (900 seconds) "validateFilename": () => null, // Anything goes! "generateKey": (filename) => filename, // Ensure Parse.FilesController.preserveFileName is true!}var s3Adapter = new S3Adapter(s3Options);var api = new ParseServer({ appId: 'my_app', masterKey: 'master_key', filesAdapter: s3Adapter})
Use the optional options argument to addMetadata and/orTags to S3 objects
const S3Adapter = require('@parse/s3-files-adapter');const s3Options = {}; // Add correct optionsconst s3Adapter = new S3Adapter(s3Options);const filename = 'Fictional_Characters.txt';const data = 'That\'s All Folks!';const contentType = 'text/plain';const tags = { createdBy: 'Elmer Fudd', owner: 'Popeye'};const metadata = { source: 'Mickey Mouse'};const options = { tags, metadata };s3Adapter.createFile(filename, data, contentType, options);
Note: This adapter willautomatically add the "x-amz-meta-" prefix to the beginning of metadata tags as stated inS3 Documentation.
varS3Adapter=require("@parse/s3-files-adapter");varAWS=require("aws-sdk");//Configure Digital Ocean Spaces EndPointvars3Options={bucket:process.env.SPACES_BUCKET_NAME,baseUrl:process.env.SPACES_BASE_URL,region:process.env.SPACES_REGION,directAccess:true,globalCacheControl:"public, max-age=31536000",presignedUrl:false,presignedUrlExpires:900,bucketPrefix:process.env.SPACES_BUCKET_PREFIX,s3overrides:{accessKeyId:process.env.SPACES_ACCESS_KEY,secretAccessKey:process.env.SPACES_SECRET_KEY,endpoint:process.env.SPACES_ENDPOINT}};vars3Adapter=newS3Adapter(s3Options);varapi=newParseServer({databaseURI:process.env.DATABASE_URI||"mongodb://localhost:27017/dev",cloud:process.env.CLOUD_CODE_MAIN||__dirname+"/cloud/main.js",appId:process.env.APP_ID||"myAppId",masterKey:process.env.MASTER_KEY||"",serverURL:process.env.SERVER_URL||"http://localhost:1337/parse",logLevel:process.env.LOG_LEVEL||"info",allowClientClassCreation:false,filesAdapter:s3Adapter});
Due to the deprecation of the AWS SDK v2, Parse Server S3 Adapter 4.x adopts the AWS SDK v3. When upgrading from Parse Server S3 Adapter 3.x to 4.x, consider the following changes:
In version 4.x, when uploading a file, the adapter will automatically create the specified S3 bucket, if it doesn't exist yet. To find out whether the bucket already exists, it will send aHEAD
request to AWS S3 to list the existing bucket. This request requires the AWS IAM permissions3:ListBucket
on the bucket resource, for example:
{"Effect":"Allow","Action": ["s3:ListBucket" ],"Resource":"arn:aws:s3:::<BUCKET_NAME>"}
Note
The specified resource needs to be the bucket ARN itself, no/*
at the end, because it's a bucket-level permission, not object-level.
In version 4.x the S3 credentials are passed differently:
Parse Server S3 Adapter 3.x:
constoptions={bucket:'<AWS_S3_BUCKET>',s3overrides:{accessKeyId:'<AWS_ACCESS_KEY>',secretAccessKey:'<AWS_SECRET_KEY>'}};
Parse Server S3 Adapter 4.x:
constoptions={bucket:'<AWS_S3_BUCKET>',s3overrides:{credentials:{accessKeyId:'<AWS_ACCESS_KEY>',secretAccessKey:'<AWS_SECRET_KEY>'}}};
Alternatively, the credentials can be set on the root object:
constoptions={bucket:'<AWS_S3_BUCKET>',credentials:{accessKeyId:'<AWS_ACCESS_KEY>',secretAccessKey:'<AWS_SECRET_KEY>'}};
Note
It is best practice to not store credentials as environment variables, as they can be easily retrieved on a compromised machine. For Parse Server running in an AWS environment, use more secure alternatives like AWS Secrets Manager, or AWS Credential Identity Provider to access shared credentials:
import{fromIni}from'aws-sdk/credential-providers';constoptions={bucket:'<AWS_S3_BUCKET>',s3overrides:{credentials:fromIni({profile:'<AWS_CLIENT_PROFILE>'})}};
About
AWS S3 file storage adapter for Parse Server
Topics
Resources
License
Code of conduct
Security policy
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Sponsor this project
Uh oh!
There was an error while loading.Please reload this page.
Packages0
Uh oh!
There was an error while loading.Please reload this page.