ACL (Access Control List) is a mechanism that determines who has access to your buckets and objects (files/folders). To set up a Public ACL, right-click on the Bucket and select "Public" or select "Share Link" to set it up.
Step 1: Right-click on the Bucket and choose “Public“
Step 2: Once you have set up Public for a Bucket, the screen will display as “Public” when accessing the link of that Bucket.
As well as using pre-configured storage classes, you can set up your own S3 Buckets from scratch, configuring access policies, versioning, and lifecycle rules to suit your specific storage needs.
Step 1: Click on “Create Bucket”
Step 2: Fill in name of “Bucket”. Refer the rule for define the Name for Bucket in this
S3 Versioning allows you to keep multiple versions of an object in the same bucket, protecting against accidental deletions and enabling easy recovery of previous file versions when needed.
Step 1: Right-click to Bucket, choose “Versions” to enable file versioning for a Bucket, and view all versions of files in that Bucket.
Step 2: previous versions of files, ensuring data recovery and protection from accidental deletions or overwrites.
The Bucket Management page displays information about your Buckets, including name, size, public and private modes, and operations of that Bucket.
Rules Bucket names must follow domain name constraints.
Bucket names must be unique.
Bucket names cannot be formatted as IP addresses
Lifecycle rules for files/folders (Objects) must be clearly defined according to usage needs.
For example:
You need to upload a large amount of data and want these files to only exist for 90 days.
Enable versioning for the Bucket, but because the number of file versions is large, it takes up much storage space.
An HI GIO S3 Bucket Policy is a JSON-based resource policy that manages access permissions to S3 buckets. It specifies who can access the bucket, the actions allowed, and the conditions for access.
You can prefer the example S3 bucket policy in “.”
Step 1: Right-click on the Bucket and select 'Bucket Policy.' Customize the Bucket Policy by Amazon S3 standards. For additional examples and further guidance, refer to the official documentation.
Bucket names can be 3 to 63 characters long.
Bucket names cannot contain uppercase characters or underscores.
Bucket names must start with a lowercase letter or number.
Bucket names must be a series of one or more labels.
The following example bucket names are valid and follow the recommended naming guidelines for general-purpose buckets:
docexamplebucket1
log-delivery-march-2020
my-hosted-content
The following example bucket names are valid but are not recommended for uses other than static website hosting:
my.example.s3.bucket
The following example bucket names are invalid:
doc_example_bucket (contains an underscore)
DocExampleBucket (contains uppercase letters)
doc-example-bucket- (ends with a hyphen)
Step3: Enable Object Lock (If needed)
Object Lock is a feature that allows you to store objects using the write-once, read-many (WORM) model. ObjectLock can help prevent objects from being deleted or overwritten for a fixed period or indefinitely.
The Object Lock feature is only used when creating a new Bucket. After selecting “Enable object lock” for a Bucket, all files/folders created/uploaded in that Bucket will be automatically set to the mode you selected in the next step.
Step 4: Choose "Governance mode" or "Compliance mode" or “NONE“
Governance mode: Use Governance mode if you want to protect objects from deletion by most users for a pre-set retention period but also want some users with special permissions to have the flexibility to change retention settings or delete objects. Users with the s3:BypassGovernance Retention permission can override or delete retention settings in governance mode.
Compliance mode: Use Compliance mode if you have compliance data retention requirements. You should only use Compliance mode if you do not want any users to be able to delete objects within the preset retention period.
NONE mode: Use Veeam Backup mode to protect the backup file “immutable mode of Veeam”.
Managing Lifecycle rules will help you solve the above problems. In a Bucket, you can create multiple Lifecycle rules to apply only to folders or all files and folders, depending on your needs.
Step 1: Right-click into Bucket and choose Lifecycle rules
Step 2: Click on “New Rule” to create the Rules
Step 3: Set up the rules you want to apply to your bucket and set the days you need to apply. After choosing the Rules, click “Add New Rule”.
Permanently delete file: It will remove all versions of the object from the bucket, including any archived versions, making it unrecoverable once deleted.
Permanently deleting previous versions: It will remove older file versions from the bucket, ensuring they cannot be recovered while the current version remains intact.
Step 4: Click “Save” to apply the Rule to Bucket.
Step 2: You can modify the Bucket Policy as needed in this popup. Once you have made the necessary changes, click "Update Policy" to apply the updates.
After choosing 1 of 2 modes to lock the object, you have to choose the desired number of days in the "Retention period" section. Retention period: 90 days means that the Bucket and the objects in that Bucket are locked in the mode you choose for 90 days from the date the Bucket was created.
Retention period: Specify a fixed period of time during which the object is locked. During this period, your object is protected by WORM and cannot be overwritten or deleted. You can apply a retention period in days with a minimum of 1 day and no maximum.
After xx days you set, S3 will delete all files created 60 days ago. It does not take into account the frequency of usage for these files.
