AWS Console vs BucketDesk. Same bucket, different job.

Count the steps

Same job, counted in steps.

Four things your team does with files every week, walked through in the AWS Console and in BucketDesk.

1. Send a client one file

   A presigned link from the console lasts 12 hours at most.

   9

   AWS Console: 9 steps

   1. Sign in to AWS
   2. Open S3
   3. Open the bucket
   4. Find the folder
   5. Select the file
   6. Actions
   7. Share with a presigned URL
   8. Set the expiry
   9. Copy and send

   3

   BucketDesk: 3 steps

   1. Open the file
   2. Share
   3. Copy the link

2. Let a teammate into one folder

   In AWS that means a new IAM user and a policy written by hand.

   5

   AWS Console: 5 steps

   1. Open IAM
   2. Create a user
   3. Write a prefix policy
   4. Attach it
   5. Send the sign-in details

   2

   BucketDesk: 2 steps

   1. Invite by email
   2. They sign in

3. Look at a PowerPoint

   The console hands you the raw file.

   3

   AWS Console: 3 steps

   1. Select the file
   2. Download
   3. Open it in PowerPoint

   1

   BucketDesk: 1 steps

   1. Click the file

4. Rename a folder

   S3 has no rename, so the console copies and then deletes.

   6

   AWS Console: 6 steps

   1. Select every object
   2. Actions
   3. Copy
   4. Pick the new folder
   5. Copy
   6. Delete the originals

   2

   BucketDesk: 2 steps

   1. Folder menu
   2. Rename

Price

AWS S3 ConsoleFree**Your time learning AWS jargon, clicking through folders, and hunting down the right file is billed separately. In frustration.

BucketDeskFree to startYour files. Your AWS account. No engineering degree required.

Bucket settings, lifecycle rules and IAM stay in the console, where they belong.