terraform-aws-eks-s3-csi-driver's Introduction

terraform-aws-eks-s3-csi-driver

Create the IAM resources for the S3 CSI Driver and install the add-on on an existing EKS cluster.

Usage:

module "eks-s3-csi-driver" {
  source  = "Z4ck404/eks-s3-csi-driver/aws"

  aws_profile      = "zack-labs"
  aws_region       = "us-west-2"
  eks_cluster_name = "zack-demo-0"

  s3_bucket_name = "zack-s3-mount--usw2-az1--x-s3"
}

examples:

AWS Examples S3 mount on eks using the driver

The module:

Requirements

No requirements.

Providers

Name	Version
aws	n/a

Modules

No modules.

Resources

Name	Type
aws_eks_addon.s3_csi	resource
aws_iam_policy.s3_policy	resource
aws_iam_role.s3_role	resource
aws_iam_role_policy_attachment.s3_role_attachment	resource
aws_eks_addon_version.s3_csi	data source
aws_eks_cluster.eks_cluster	data source
aws_iam_openid_connect_provider.this	data source

Inputs

Name	Description	Type	Default	Required
aws_profile	AWS Profile	`string`	`""`	no
aws_region	Region Code	`string`	n/a	yes
eks_cluster_name	EKS cluster name	`string`	n/a	yes
s3_bucket_name	Name of the S3 bucket	`string`	n/a	yes

Outputs

No outputs.

terraform-aws-eks-s3-csi-driver's People

Contributors

Stargazers

Watchers

terraform-aws-eks-s3-csi-driver's Issues

Provider configuration inside modules

I attempted to utilize your module and noticed that configuring the provider is required. I'm curious whether this requirement was an intentional design choice or if there's other specific reason