From 55b7cef7eda439a0eb7a5b98f8ab0fa0c582ce46 Mon Sep 17 00:00:00 2001 From: Frederic M <43849398+fad3t@users.noreply.github.com> Date: Mon, 9 Mar 2026 11:28:22 +0100 Subject: [PATCH] docs: update commands to generate creds for non-EKS clusters --- website/docs/getting-started-helm.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/website/docs/getting-started-helm.md b/website/docs/getting-started-helm.md index f76a65cf..15934d04 100644 --- a/website/docs/getting-started-helm.md +++ b/website/docs/getting-started-helm.md @@ -187,11 +187,17 @@ See the [Configure IAM Permissions guide](/guides/configure-iam) for more detail Use AWS credentials from your local environment (not recommended for production): ```bash +# Create the credentials file +cat < credentials +[default] +aws_access_key_id = $(aws configure get aws_access_key_id) +aws_secret_access_key = $(aws configure get aws_secret_access_key) +EOF + # Create secret with AWS credentials kubectl create secret generic -n $ACK_SYSTEM_NAMESPACE \ ack-${SERVICE}-user-secrets \ - --from-literal=AWS_ACCESS_KEY_ID=$(aws configure get aws_access_key_id) \ - --from-literal=AWS_SECRET_ACCESS_KEY=$(aws configure get aws_secret_access_key) + --from-file=credentials # Configure controller to use the secret export ACK_ENABLE_DEVELOPMENT_LOGGING=true