rootdir_security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
rootdir_security [2022/08/06 19:32] yves [Accessing secured content] |
rootdir_security [2022/08/06 19:34] yves [Accessing secured content] |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| * [[rootdir_s3|S3 storage]] | * [[rootdir_s3|S3 storage]] | ||
| * [[rootdir_azure|Azure storage]] | * [[rootdir_azure|Azure storage]] | ||
| - | |||
| - | === S3 storage === | ||
| - | |||
| - | PMA.core is one of the few vendors that [[https://www.prweb.com/releases/pathomation_announces_support_for_cloud_storage_and_file_transfer_protocol_ftp_servers/prweb18296771.htm|supports cloud storage natively]]. | ||
| - | |||
| - | Let's say that you have an S3 bucket and put slides in it: | ||
| - | |||
| - | {{ ::rootdir_s3_10.png?direct&400 |}} | ||
| - | |||
| - | To protect access, you should create a dedicated entity that can only access that content. | ||
| - | |||
| - | {{ ::rootdir_s3_20.png?direct&400 |}} | ||
| - | |||
| - | You can then create a pair of dedicated access / secret keys for the new entity: | ||
| - | |||
| - | {{ :rootdir_s3_30.png?direct&400 |}} | ||
| - | |||
| - | These keys are then used to configure the S3 mounting point at the PMA.core side: | ||
| - | |||
| - | {{ :rootdir_s3_40.png?direct&400 |}} | ||
| - | |||
| - | The mounting point only functions when the provided credentials are still active on the S3 storage side. If not, an error message ensues: | ||
| - | |||
| - | {{ :rootdir_s3_50.png?direct&400 |}} | ||
| - | |||
| - | If all is well, you can now browse your slides directly from your S3 content. | ||
| - | |||
| - | {{ :rootdir_s3_60.png?direct&400 |}} | ||
| - | |||
| - | As of version 3.1, PMA.core also supports IAM AWS Role policies. | ||
| === Azure storage === | === Azure storage === | ||
rootdir_security.txt ยท Last modified: 2022/08/06 19:41 by yves
