Hi @Technolero ,   I found this https://docs.aws.amazon.com/eks/latest/userguide/manage-secrets.html  Have not tried it yet but it looks good to me 🙂 ... View more

Hi @UttamKumar    Very useful! For this to work do we need to set the "hop limit" on the EKS managed nodes metadata to 2?   Thanks, Eyal ... View more

Thanks @gwootton    For the sake of anyone interested in this topic here is what I did. To stop, after the running the "sas-stop-all" job, I modified the Desired Count of the remaining dynamic (autoscaled) node pools that were not shutdown yet to zero and thus forced a shutdown on the remaining running AWS pods.   When I wanted to start back again I changed again from zero to one and then these AWS pods started to execute back again and then I could SAS back again using the "sas-start-all" job and all seems to work fine. ... View more

There is a SAS Note https://support.sas.com/kb/63/475.html about this but it seems to be for Viya 3.4 so not sure if this is applicable...   ... View more

Hi @BrunoMueller ,   Returning to this question after some time.. Using the SAS supplied sas-stop-all job stops all SAS pods but does not seem to stop the AWS pre-requisite pods and they remain running. For example, see output below of list of pods in the AWS cluster after I ran the sas-stop-all job:   [sas@65ffd157191b /]$ kubectl -n kube-system get pods -o wide NAME                                                         READY   STATUS    RESTARTS   AGE    IP               NODE                                             NOMINATED NODE   READINESS GATES aws-node-2nmtm                                               1/1     Running   0          106m   192.168.26.23    ip-192-168-26-23.il-central-1.compute.internal   <none>           <none> aws-node-nm4kx                                               1/1     Running   0          107m   192.168.51.33    ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> cluster-autoscaler-aws-cluster-autoscaler-5d99f7f75c-k8dmh   1/1     Running   0          101m   192.168.47.236   ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> coredns-7fd98fbdf9-4pprb                                     1/1     Running   0          112m   192.168.12.32    ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> coredns-7fd98fbdf9-kk5wk                                     1/1     Running   0          112m   192.168.50.221   ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> ebs-csi-controller-67868fdb79-bnvm7                          5/5     Running   0          101m   192.168.20.78    ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> ebs-csi-controller-67868fdb79-dw2mh                          5/5     Running   0          101m   192.168.2.59     ip-192-168-26-23.il-central-1.compute.internal   <none>           <none> ebs-csi-node-6gvvl                                           3/3     Running   0          101m   192.168.14.30    ip-192-168-26-23.il-central-1.compute.internal   <none>           <none> ebs-csi-node-7zr8w                                           3/3     Running   0          101m   192.168.58.137   ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> kube-proxy-t9tgk                                             1/1     Running   0          106m   192.168.26.23    ip-192-168-26-23.il-central-1.compute.internal   <none>           <none> kube-proxy-w25wm                                             1/1     Running   0          107m   192.168.51.33    ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> metrics-server-b975dc65f-s7kxt                               1/1     Running   0          100m   192.168.5.14     ip-192-168-51-33.il-central-1.compute.internal   <none>           <none> I want to shut down all pods including the ones above to save AWS costs. The thing is that if I set the node pools to Desired Count = 0 this will close the node pools and shut down the pods but then I do not know how to start them back again.   There must be some documented way to shut down the AWS EKS cluster completely, at least I hope there is..   Any idea?     ... View more

שלום @Tzipora    כדאי לך לשאול בפורומים ממוקדי תוכן כאן באתר  לדוגמה מצאתי בפורום Data Science את ההתכתבות הבאה שמדברת על אותו מאקרו והחיתוך ל 32 תווים של שם השדה: https://communities.sas.com/t5/SAS-Data-Science/dmnormip-Format-sas/td-p/405889 אם יש לך שאלות נוספות ממליץ לך לשאול בפורום ההוא (יש לשאול באנגלית)   אייל ... View more

Hi @StuartRogers    Thank you for this info! I have a question for you: if customer wants to implement MFA then it is my understanding they can configure SAS Logon Manager to use SAML or OIDC and it is up to the Identity Provider to implement MFA, right? If so, I am not sure how to match the userids in the Identity Provider with the users extracted from AD by the Identities service. Is there a mechanism to sync AD user to the Identity Provider's list of users?   Thanks, Eyal ... View more

Hi @JosvanderVelden ,   Thank you and Renato Luppi for calling me and providing a wonderful idea how to implement this! The idea used VA's Web Content object to embed a SAS Job Execution job into the VA report and this SAS job allows the user to upload an Excel/CSV file and the SAS code loads this uploaded data to some CAS table (in CASUSER as an example) and then the VA report joins the original data with the new uploaded CAS table effectively creating a report on the VA report.     ... View more

Thanks @Patrick  Do you know if I disallow Authenticated Users from creating Session CASLIBs (which they are allowed by default) will that have a negative impact on SAS Visual Analytics app? I do not want them to create any caslib when they use SAS Studio or Python (SWAT) client but do not want that to cause issues in SAS VA.   This is what I currently have set:     ... View more