Deployment files can be stored in inbox, outbox, and sandbox buckets. The inbox is where files arrive after they’ve been synced. The outbox is where you place files that you want to be synced. The sandbox is a play area for creating and manipulating files.
Buckets can be enabled for each deployment on their deployment page under the File Management tab. Files can be stored in Google Buckets, AWS S3 Buckets or locally. The platform storage cannot be local if a user uses a cluster.
Google Buckets
If you are using Google Buckets, you must type in the bucket name and input your Google credentials. There is the option to You can import your credential file directly. Input the location of your local root directory location when using Edge file storage.
...
Note that in the following modal, Bucket Name is the name of the ACTUAL Google Bucket whereas Name (near the top of the modal) is any name you choose to identify the Bucket Set.
...
You can view your Google credentials in JSON formatting if you click View.
...
There is an option to store files in Google
...
AWS S3 Buckets
When using AWS S3 Buckets you must type in the bucket name and your S3 Credentials:
AWS ACCESS KEY ID
AWS ACCESS KEY SECRET
...
Note that in this modal, Bucket Name is the name of the ACTUAL AWS S3 bucket while Name (near the top of the modal) is any name you choose to identify the Bucket Set.
Also note that the Bucket Region of the AWS S3 bucket is required. The example modal shows the region set to us-east-2. Enter your region accordingly.
You can store files in Buckets on the Admin Management page if you are an admin user.
...
The Files page allows you to view the file tree and the file’s data.
...
If you are on the platform, it will show you a deployment list. When you click a deployment, you can see its file viewer. If you are on an edge, it will take you directly to the file viewer that contains all the files for all of that edge’s deployments.Admin Developer:
...