topic Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh in Data Engineering

Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Shared"

jaredrohe — Fri, 27 Oct 2023 02:38:54 GMT

Hello,

I am attempting to configure Autoloader in File Notification mode with Delta Live Tables. I configured an instance profile, but it is not working because I immediately get AWS access denied errors. This is the same issue that is referenced here

After a bunch of debugging, I've determined that the issue is caused by the "Access Mode" being set to "Shared".

To test this, I created a new compute cluster with the correct instance profile and Access Mode set to "No Isolation Shared". I then connected to that computer cluster in a Python Notebook and I had no problem making AWS API calls through boto3.

I then ran this same experiment with another compute cluster, but this time with the Access Mode set to "Shared". I double checked that the instance profile was configured properly. This time when I connected to the compute cluster via a Python Notebook, all of my AWS commands failed with "invalid credentials" errors.

The only difference between the two consecutive tests was the Access Mode.

Therefore, it appears that Delta Live Tables need to be configured with a Cluster Policy containing an Access Mode of "No isolation Shared". However, that does not seem possible.

I've tried to update the `data_security_mode` JSON property when creating a new cluster policy. However, I then am faced with a validation error when refreshing my Delta Live Table which says that the `data_security_mode` key is not supported.

Is there a way to give the Delta Live Tables access to instance profiles?

Thanks so much for your time!
-Jared

Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh

jaredrohe — Tue, 31 Oct 2023 17:14:48 GMT

Hey @Retired_mod , thanks for the response.

My original question was not concerning how to configure instance profiles. I was able to do that successfully.

The problem is that when a cluster runs with an instance profile, the access mode is essential for the instance profile to take effect.

If the cluster runs with Access Mode "No isolation shared", then everything works.

However, if the cluster runs with "Shared" (which is the default for Delta Live Tables) then it does not work. The instance profile does not take effect.

Does the problem make sense @Retired_mod ?

Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh

djhs — Tue, 30 Apr 2024 14:41:28 GMT

Hi, I'm running into the same issue. Was this solved?

Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh

Babu_Krishnan — Wed, 01 May 2024 21:16:58 GMT

We are running into same issue, was this resolved ?

Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh

jaredrohe — Fri, 03 May 2024 14:32:29 GMT

Unfortunately, I never got this to work.

Re: Instance Profiles Do Not Work with Delta Live Tables Default Cluster Policy Access Mode "Sh

AcrobaticMonkey — Sat, 28 Sep 2024 08:54:50 GMT

Same issue here, the instance profile works fine for both No isolation and single access mode but not for shared 😕