Error when configuring SSO in AWS Edition

We are using Dremio via AWS Marketplace and we tried to change the way we authenticate by using this guide:

Configuring SSO in AWS Edition - Dremio

But we receive this error right after changing the config (Dremio dont start after that):

2022-07-12 19:02:51,857 [main] INFO  c.d.datastore.LocalKVStoreProvider - Starting LocalKVStoreProvider
2022-07-12 19:02:52,745 [main] INFO  c.d.d.a.LegacyKVStoreProviderAdapter - Starting LegacyKVStoreProviderAdapter.
2022-07-12 19:02:52,758 [main] INFO  c.d.datastore.LocalKVStoreProvider - LocalKVStoreProvider is up
2022-07-12 19:02:52,867 [main] INFO  c.d.datastore.LocalKVStoreProvider - Stopping LocalKVStoreProvider
2022-07-12 19:02:52,952 [main] INFO  c.d.datastore.LocalKVStoreProvider - Stopped LocalKVStoreProvider
2022-07-12 19:02:53,129 [main] INFO  com.dremio.dac.daemon.DACDaemon - Dremio daemon write path: /var/lib/dremio
2022-07-12 19:02:53,130 [main] INFO  com.dremio.dac.daemon.DACDaemon - This node is the master node, ip-xx-xx-x-xx.ec2.internal. This node acts as a coordinator.
2022-07-12 19:02:53,256 [main] WARN  com.dremio.telemetry.api.Telemetry - Failure reading telemetry configuration. Leaving telemetry as is.
java.lang.IllegalArgumentException: resource dremio-telemetry.yaml not found.
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:220)
        at com.google.common.io.Resources.getResource(Resources.java:198)
        at com.dremio.telemetry.api.Telemetry$1.get(Telemetry.java:104)
        at com.dremio.telemetry.api.Telemetry$1.get(Telemetry.java:86)
        at com.dremio.telemetry.api.config.AutoRefreshConfigurator.refreshOnce(AutoRefreshConfigurator.java:74)
        at com.dremio.telemetry.api.config.AutoRefreshConfigurator.<init>(AutoRefreshConfigurator.java:54)
        at com.dremio.telemetry.api.config.AutoRefreshConfigurator.<init>(AutoRefreshConfigurator.java:44)
        at com.dremio.telemetry.api.Telemetry.startTelemetry(Telemetry.java:121)
        at com.dremio.exec.server.BootStrapContext.<init>(BootStrapContext.java:62)
        at com.dremio.dac.daemon.DACDaemonModule.bootstrap(DACDaemonModule.java:325)
        at com.dremio.dac.daemon.DACDaemon.<init>(DACDaemon.java:185)
        at com.dremio.dac.daemon.DACDaemon.newDremioDaemon(DACDaemon.java:313)
        at com.dremio.dac.daemon.DACDaemon.newDremioDaemon(DACDaemon.java:321)
        at com.dremio.dac.daemon.DremioDaemon.main(DremioDaemon.java:103)
2022-07-12 19:02:54,616 [main] ERROR ROOT - Dremio is exiting. Failure while starting services.
java.lang.IllegalArgumentException: resource config.json not found.
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:220)
        at com.google.common.io.Resources.getResource(Resources.java:198)
        at com.dremio.extusr.ExternalUserConfig.configFromUri(ExternalUserConfig.java:31)
        at com.dremio.extusr.azuread.AzureADConfig.configFromUri(AzureADConfig.java:33)
        at com.dremio.dac.daemon.EnterpriseDACDaemonModule.setupAzureAD(EnterpriseDACDaemonModule.java:1338)
        at com.dremio.dac.daemon.EnterpriseDACDaemonModule.setupExternalUserGroupService(EnterpriseDACDaemonModule.java:1146)
        at com.dremio.dac.daemon.EnterpriseDACDaemonModule.setupUserGroupService(EnterpriseDACDaemonModule.java:1099)
        at com.dremio.dac.daemon.EnterpriseDACDaemonModule.setupUserService(EnterpriseDACDaemonModule.java:1059)
        at com.dremio.dac.daemon.DACDaemonModule.build(DACDaemonModule.java:652)
        at com.dremio.dac.daemon.EnterpriseDACDaemonModule.build(EnterpriseDACDaemonModule.java:312)
        at com.dremio.dac.daemon.AwsDACDaemonModule.build(AwsDACDaemonModule.java:59)
        at com.dremio.dac.daemon.DACDaemon.<init>(DACDaemon.java:186)
        at com.dremio.dac.daemon.DACDaemon.newDremioDaemon(DACDaemon.java:313)
        at com.dremio.dac.daemon.DACDaemon.newDremioDaemon(DACDaemon.java:321)
        at com.dremio.dac.daemon.DremioDaemon.main(DremioDaemon.java:103)
[ec2-user@ip-10-56-6-81 dremio]$

Does anyone know what could be done in that case?

Hi

how did you resolved this issue, I am seeing similar exception in the log after setting up sso with oauth.json.

Thanks