Configure and use AWS CLI with WEKA S3 storage
Learn how to configure and use the AWS CLI with WEKA S3 storage.
Last updated
Learn how to configure and use the AWS CLI with WEKA S3 storage.
Last updated
To use the AWS CLI to access S3-compatible storage on WEKA, configure the CLI with the appropriate endpoint and credentials.
Verify AWS CLI is installed:
Verify that the AWS CLI is installed on your system. If required, see .
Configure AWS CLI with WEKA credentials:
Use the following command to start configuration:
Enter the following information when prompted:
AWS Access Key ID: Your WEKA S3 user access key.
AWS Secret Access Key: Your WEKA S3 user secret key.
Default region name: You can leave this blank.
Default output format: You can leave this blank.
Enable AWS Signature Version 4 for WEKA server:
WEKA requires AWS Signature Version 4 for authentication. Set it using:
When using AWS CLI commands with WEKA, specify the custom endpoint URL. The following are some common operations:
Replace https://your-weka-server:9000
with your WEKA server's actual address.
This command creates a new bucket named mybucket
.
This command uploads local-file.txt
to the mybucket
bucket.
This command lists the contents of the mybucket
bucket.
This command downloads remote-file.txt
from the mybucket
bucket to the current directory.
This command deletes file-to-delete.txt
from the mybucket
bucket.
If you attempt to remove a bucket that is not empty, you receive an error. You must either empty all object versions from the bucket or add --force
to the remove bucket command. --force
deletes the bucket and all object versions within it.
This command removes the mybucket
bucket.