Skip to main content

Change the AWS credential a NodeLink uses

Jaah reads and changes a NodeLink's AWS EFS file system through one AWS credential: it creates access points there and writes the file system's policy. Switch it to another credential when the old one is going away, such as a key you are about to rotate or delete, or when it lacks a permission Jaah needs.

Nodes don't use this credential to mount the folder, so they keep their mount while you change it.

Before you start:

  • NodeLink is shown only while your plan includes it.
  • Changing a NodeLink requires permission to edit credentials, as org admins have.
  • This applies to storage on AWS EFS only. Jaah-managed storage has no credential of yours, and GCP Filestore and Azure Files storage don't offer Change.
  • Add the new credential first, as in Add a credential. It must see the same file system, in the same AWS account and region, with these permissions: CreateAccessPoint, DeleteAccessPoint, DescribeAccessPoints, PutFileSystemPolicy and TagResource, plus DescribeFileSystemPolicy so the Storage tab can show the policy.
  1. In the sidebar, select Directory, then the Networks tab, then NodeLink.
  2. Select the NodeLink's name, then its Storage tab. The facts list shows the credential in use beside AWS credential.
  3. Select Change beside AWS credential. A credential picker opens under the facts.
  4. In AWS credential, pick the new credential. Hover the label to read Jaah reads and changes this file system through it. If the list is empty, it reads No AWS credential. with an Add secret link that opens a new credential's page.
  5. Select Save. Jaah checks that the new credential can see the file system before it saves. If it can't, the tab says why and keeps the old credential; pick another or give that one access in AWS.
  6. Select Refresh from AWS, so the tab reads the file system through the new credential.
  7. Check Policy. Current means Jaah read the policy through the new credential and it matches the one Jaah writes. Unknown means the credential can't read the policy; follow Repair a NodeLink's file-system policy.
  8. Select the Nodes tab and check that each node still reads Mounted.

To back out before saving, select Cancel beside Save. The credential belongs to the storage, so every NodeLink on the same storage now uses the new one. Once no storage uses the old credential, you can delete it as in Replace or delete a credential.