version: "3"

services:

  s3:

    image: minio/minio

    command: server /export

    ports:

    - "9000:9000"

    volumes:

      - ./data:/export

      - ./config:/root/.minio

    environment:

    - "MINIO_ACCESS_KEY=dalongdemo"

    - "MINIO_SECRET_KEY=dalongdemo"

provider "s3" {

    s3_server = "localhost:9000"

    s3_access_key = "dalongdemo"

    s3_secret_key = "dalongdemo"

    s3_api_signature = "v4"

    s3_ssl = false

    s3_debug = true

}

resource "s3_bucket" "bucket_create" {

  bucket = "s3page"

}

resource "s3_file" "upload_index_page" {

    bucket = "s3page"

    name = "index.html"

    file_path = "./files/index.html"

    content_type = "text.html"

    debug = true

    depends_on = ["s3_bucket.bucket_create"]

}

resource "s3_file" "upload_user_js" {

    bucket = "s3page"

    name = "user.js"

    file_path = "./files/user.js"

    content_type = "application/javascript"

    debug = true

    depends_on = ["s3_bucket.bucket_create"]

}

我测试环境是mac，使用go get 安装provider，然后copy plugin 到tf 定义文件目录，注意需要创建目录

mkdir -p ./.terraform/plugins/darwin_amd64/

./.terraform/plugins/darwin_amd64/

terraform init

terraform plan

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create

Terraform will perform the following actions:

  + s3_bucket.bucket_create

      id: <computed>

      bucket: "s3page"

      debug: "false"

  + s3_file.upload_index_page

      id: <computed>

      bucket: "s3page"

      content_type: "text.html"

      debug: "true"

      file_path: "./files/index.html"

      name: "index.html"

  + s3_file.upload_user_js

      id: <computed>

      bucket: "s3page"

      content_type: "application/javascript"

      debug: "true"

      file_path: "./files/user.js"

      name: "user.js"

Plan: 3 to add, 0 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform

can't guarantee that exactly these actions will be performed if

"terraform apply" is subsequently run.

terraform apply

An execution plan has been generated and is shown below.

Resource actions are indicated with the following symbols:

  + create

Terraform will perform the following actions:

  + s3_bucket.bucket_create

      id: <computed>

      bucket: "s3page"

      debug: "false"

  + s3_file.upload_index_page

      id: <computed>

      bucket: "s3page"

      content_type: "text.html"

      debug: "true"

      file_path: "./files/index.html"

      name: "index.html"

  + s3_file.upload_user_js

      id: <computed>

      bucket: "s3page"

      content_type: "application/javascript"

      debug: "true"

      file_path: "./files/user.js"

      name: "user.js"

Plan: 3 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?

  Terraform will perform the actions described above.

  Only 'yes' will be accepted to approve.

  Enter a value: yes

s3_bucket.bucket_create: Creating...

  bucket: "" => "s3page"

  debug: "" => "false"

s3_bucket.bucket_create: Creation complete after 0s

s3_file.upload_index_page: Creating...

  bucket: "" => "s3page"

  content_type: "" => "text.html"

  debug: "" => "true"

  file_path: "" => "./files/index.html"

  name: "" => "index.html"

s3_file.upload_user_js: Creating...

  bucket: "" => "s3page"

  content_type: "" => "application/javascript"

  debug: "" => "true"

  file_path: "" => "./files/user.js"

  name: "" => "user.js"

s3_file.upload_index_page: Creation complete after 0s

s3_file.upload_user_js: Creation complete after 0s

Apply complete! Resources: 3 added, 0 changed, 0 destroyed.