Using the MinIO API via curl

Using the MinIO API via curl is straightforward, as MinIO is compatible with Amazon S3 API, so most commands follow a similar syntax. Here’s a guide on how to use curl with the MinIO API for some common operations like uploading, downloading, and managing objects.

Prerequisites

  1. Access Key and Secret Key: Obtain your MinIO Access Key and Secret Key.
  2. MinIO Endpoint: Know your MinIO server endpoint, e.g., http://localhost:9000.
  3. Bucket: You may need an existing bucket name, or create a new one using the commands below.

Authentication Header

For requests to work with MinIO, you need to include authentication in the headers. MinIO uses AWS Signature Version 4 for signing requests.

Common Examples

1. List Buckets

To list all buckets in your MinIO account, use:

curl -X GET \
  --url "http://localhost:9000/" \
  -H "Authorization: AWS <AccessKey>:<Signature>"

2. Create a Bucket

To create a new bucket, use:

curl -X PUT \
  --url "http://localhost:9000/<bucket-name>" \
  -H "Authorization: AWS <AccessKey>:<Signature>"

Replace <bucket-name> with your desired bucket name.

3. Upload an Object

To upload a file to a bucket, you can use the PUT method.

curl -X PUT \
  --url "http://localhost:9000/<bucket-name>/<object-name>" \
  -H "Authorization: AWS <AccessKey>:<Signature>" \
  --upload-file "<file-path>"

Replace <bucket-name> with the name of your bucket, <object-name> with the name you want for the uploaded object, and <file-path> with the path to the file on your system.

4. Download an Object

To download an object, use the GET method.

curl -X GET \
  --url "http://localhost:9000/<bucket-name>/<object-name>" \
  -H "Authorization: AWS <AccessKey>:<Signature>" \
  -o "<local-file-path>"

Replace <bucket-name>, <object-name>, and <local-file-path> accordingly.

5. List Objects in a Bucket

To list all objects in a bucket, use:

curl -X GET \
  --url "http://localhost:9000/<bucket-name>" \
  -H "Authorization: AWS <AccessKey>:<Signature>"

Generating the Signature

The Authorization header should contain a signature created using AWS Signature Version 4, which can be complex to generate manually. It may be easier to use tools, libraries, or pre-built clients like the MinIO Client (mc) or AWS SDKs to handle this signature.

Automating the Signing Process

Alternatively, tools like AWS CLI, MinIO Client (mc), or libraries for Python, Java, etc., can make requests easier and handle the signing process internally.

Let me know if you need additional examples or help with signing.

댓글

댓글 쓰기

이 블로그의 인기 게시물

MAX_POLL_RECORDS_CONFIG in Kafka

The default value of MAX_POLL_RECORDS_CONFIG in Apache Kafka is: 500 What is MAX_POLL_RECORDS_CONFIG ? The MAX_POLL_RECORDS_CONFIG configuration specifies the maximum number of records a Kafka consumer can retrieve in a single call to the poll() method. Key Details: Default Behavior : If not configured, the consumer will fetch up to 500 records per poll. This is a batch size limit and helps in controlling the volume of data processed at a time. Adjusting the Value : Smaller values (e.g., 10 ): Useful for low-latency processing or when you want to process fewer records at a time. Larger values (e.g., 1000 ): Useful for batch processing or applications designed to handle high throughput. Use Case Scenarios : High throughput: Increase the value to minimize the number of poll() calls. Low latency or real-time processing: Decrease the value to process smaller chunks faster. Example Configuration Java Configuration: Properties props = new Properties(); p...
자세한 내용 보기

How to change java version on gradle of flutter

To change the Java version used by Gradle in a Flutter project, you need to modify the build.gradle files of your Flutter project. Here's how you can do that: Steps: Locate the build.gradle files: You will find two build.gradle files in your Flutter project: One at the root level: <project_root>/android/build.gradle Another inside the app module: <project_root>/android/app/build.gradle Update the Java version in android/build.gradle : In the root build.gradle file, ensure that the sourceCompatibility and targetCompatibility settings are set to the desired Java version. Open <project_root>/android/build.gradle Look for the compileOptions block (or create it if it's not present). Update the Java version like this: allprojects { repositories { google() mavenCentral() } } subprojects { afterEvaluate { project -> if ( project .hasProperty( "android" )) { android { ...
자세한 내용 보기