From 60e018fc97a030d4cc334dbfd323477d72675167 Mon Sep 17 00:00:00 2001 From: Samhita Alla Date: Fri, 29 Mar 2024 14:34:59 +0530 Subject: [PATCH] update sagemaker agent setup doc as secrets aren't required anymore Signed-off-by: Samhita Alla --- .../deployment/agents/sagemaker_inference.rst | 35 +++---------------- 1 file changed, 5 insertions(+), 30 deletions(-) diff --git a/docs/deployment/agents/sagemaker_inference.rst b/docs/deployment/agents/sagemaker_inference.rst index be9188d873..5ceb248c2d 100644 --- a/docs/deployment/agents/sagemaker_inference.rst +++ b/docs/deployment/agents/sagemaker_inference.rst @@ -67,37 +67,12 @@ Specify agent configuration - boto - sagemaker-endpoint -Add the AWS credentials ------------------------ +AWS credentials +--------------- -1. Install the flyteagent pod using helm: - -.. code-block:: - - helm repo add flyteorg https://flyteorg.github.io/flyte - helm install flyteagent flyteorg/flyteagent --namespace flyte - -2. Get the base64 value of your AWS credentials: - -.. code-block:: - - echo -n "" | base64 - -3. Edit the flyteagent secret: - -.. code-block:: bash - - kubectl edit secret flyteagent -n flyte - -.. code-block:: yaml - :emphasize-lines: 3-5 - - apiVersion: v1 - data: - aws-access-key: - aws-secret-access-key: - aws-session-token: - kind: Secret +When running the code locally, you can set AWS credentials as +`environment variables `__. +When running on a production AWS cluster, the IAM role is used by default. Ensure that it has the `AmazonSageMakerFullAccess` policy attached. Upgrade the Flyte Helm release ------------------------------