Skip to content

fix: Use AWS env vars for IAM user - #306

Merged
NohaIhab merged 1 commit into
track/1.10from
kf-8982-fix-use-aws-env-vars-for-iam-user
Sep 10, 2026
Merged

NohaIhab merged 1 commit into
track/1.10from
kf-8982-fix-use-aws-env-vars-for-iam-user

Conversation

@NohaIhab

@NohaIhab NohaIhab commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Closes canonical/charmed-kubeflow-solutions#265

Fix explained thoroughly in canonical/charmed-kubeflow-solutions#265 (comment)

Explicitly set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars so MinIO in gateway mode uses those credentials and does not accidentally assume other IAM credentials found in the Pod/node.

Explicitly set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars so
MinIO in gateway mode uses those credentials and does not accidentally
assume other IAM credentials found in the Pod/node.

canonical/kfp-operators#785
@NohaIhab
NohaIhab merged commit 556b6cc into track/1.10 Sep 10, 2026
12 checks passed
@NohaIhab
NohaIhab deleted the kf-8982-fix-use-aws-env-vars-for-iam-user branch September 10, 2026 11:38
NohaIhab added a commit that referenced this pull request Sep 10, 2026
Explicitly set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars so
MinIO in gateway mode uses those credentials and does not accidentally
assume other IAM credentials found in the Pod/node.

canonical/charmed-kubeflow-solutions#265
NohaIhab added a commit that referenced this pull request Sep 10, 2026
Explicitly set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY env vars so
MinIO in gateway mode uses those credentials and does not accidentally
assume other IAM credentials found in the Pod/node.

canonical/charmed-kubeflow-solutions#265
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Minio gateway mode not working as expected after upgrade from ckf-1.10/stable to 1.10/stable

3 participants