Archil enforces POSIX permissions for files and folders. However, we do not recommend that you rely on POSIX permissions as a security boundary between untrusted users. Archil does not limit the access of “Disk Users” beyond what POSIX enforces.
Authentication methods
We recommend using IAM Authorization whenever you are mounting an Archil disk located in AWS from a server that is located in the same AWS Region.AWS role authorization
Archil natively supports using AWS IAM users or roles to authorize access to the disk. This is the recommended authorization method when mounting from AWS EC2 instances in the same region as your disk. Archil disks perform IAM authorization by matching the ARN of the mounting role to the list of that disks’ authorized users. As a result, your IAM user or role does not need any specific Archil permissions in its policy.Setup steps
- Get your EC2 server’s IAM role ARN using the following command:
- Copy the resulting IAM role ARN.
- Return to the disk’s Details page in the Archil console, and paste the role ARN as an Authorized User.
Mounting with IAM authentication
When using IAM authentication, mount your disk without specifying an auth token:Token authorization
Outside of AWS, or when mounting from a different region, Archil can create static token credentials that can be used to gain access to the disk.Setup steps
- Navigate to the disk’s Details page in the Archil console
- Click Generate Token to create a new authorization token
- Copy the generated token - you’ll need it when mounting the disk
- Keep this token secure as it grants full access to your disk
Archil does not store tokens in plaintext. Store your token somewhere securely when it’s created because it will not be visible again from the Archil console.