[Nucleus Enterprise on AWS] Issues with Saving USD Files on Nucleus Server in AWS. Failed to save layer sample.usd due to permission issue

Omniverse Archive Omniverse Technical Support
, , ,
1

Hello,

I followed the instructions on the NVIDIA Omniverse Nucleus Server on AWS EC2 page to set up a Nucleus server on AWS.

I logged in as the administrator with the username “Omniverse” and created other users. The user who created and attempted to save the USD files has administrator privileges and confirmed write permissions to the folders and files. However, when I try to create and save USD files using both USD Composer and IsaacSim, I encounter the following error:
2025-mm-dd hh:mm:ss [Error] [omni.usd] ERROR! Failed to save layer omniverse://nucleus.xxxxx.com:443/Projects/xx/sample.usd due to permission issue.

Could you please help me understand why this error occurs and how to resolve it?

Additionally, I noticed something concerning in the /var/lib/nucleus-data/log/lft/access.log.current file. The Response Code is 201, indicating that the response was successful, but the “Instance” field shows abc4f67f6a9b, which does not match the actual instance ID of the AWS EC2 instance that is running. Is it normal for the “Instance” field to differ from the actual AWS EC2 instance ID? Could this discrepancy be causing the error? If so, what should I correct?

Thank you for your assistance.

Best regards,

2

Thank you for your inquiry. I am just curious, but how are you using Nucleus on your EC2? Do you need multiple users? Nucleus is not required for most single machines like this. You can just save files normally within normal windows or Linux file structure. Are you trying to connect a local machine to the same EC2 Nucleus server, or just use it on the one VM?

With regards to the specific error, make sure you are in a fresh, new, user folder that you have created. Then right click on that folder and make sure your user has full read/write permissions. Do not use any of the samples. Start a fresh file as well. That way you own the folder and the file.

Please refer to this file for specific help on permissions. ACLs and Permissions Management — Omniverse Nucleus

With regard to your second question, I am not sure. I will need to seek some help on that.

3

Please validate you are not running Nucleus or the Composer applications through any custom or 3rd party proxies, as this is not supported.

Also please validate you have all the proper ports open and accessible for Nucleus to function.
Networking and TCP/IP Ports — Omniverse Nucleus

4

Thank you for your response.

I have validated that we are not running Nucleus or the Composer applications through any custom or third-party proxies. We are using the default network configuration provided by AWS.

Regarding the network and port settings, I have ensured that all the necessary ports are open and accessible for Nucleus to function properly. I have referred to the Networking and TCP/IP Ports — Omniverse Nucleus documentation and confirmed that the required ports are configured correctly.

Despite these validations, the permission issue when saving USD files still persists. Could you provide any additional troubleshooting steps or insights to resolve this issue?

Thank you for your assistance.

Best regards,

5

For testing purposes, I temporarily opened all ports to try saving the USD file, but I still encountered the following error:
2025-mm-dd hh:mm:ss [Error] [omni.usd] ERROR! Failed to save layer omniverse://nucleus.xxxxx.com:443/Projects/xx/Sample-Sphere.usd due to permission issue.
Therefore, I can confirm that the issue is not related to port settings.

Additionally, I have verified that the user has read and write permissions in the folder created by the administrator within the user directory. Despite these permissions being correctly set, the error persists.

Could you provide any further troubleshooting steps or insights to resolve this permission issue?

Best regards,

6

Ok try a couple of things.

  1. can you save any file to the normal OS desktop, outside of Nucleus? Just normal file permission?
  2. can you read and open our demo content inside of Nucleus?
  3. can you try saving the file to your OS desktop first, and then try copying that file to your desired Nucleus location?
  4. can you save a file ANYWHERE on Nucleus? Not just in Projects?
  5. does your folder location have any red padlocks on it?
7

In addition, please validate you can upload data directly to Nucleus through Navigator without error

8

Thank you for your suggestions. Here are the results of the tests:

  1. I can save files to the normal OS desktop outside of Nucleus. Additionally, I can save files to a local Nucleus running on localhost, but I cannot save files to the Nucleus server running on AWS.
  2. Yes, I can read and open the demo content inside of Nucleus.
  3. I can save a file to the OS desktop and then copy that file to the desired Nucleus location. However, I cannot create and save a file directly from USD Composer to the Nucleus server on AWS. Additionally, while I can open existing USD files, I cannot edit and overwrite them on the AWS Nucleus server. This method is inconvenient.
  4. I can copy files from the OS to any location on Nucleus.
  5. There are no red padlocks on the folder location.

In addition, I can upload data directly to Nucleus through Navigator without any errors.

Despite these validations, the permission issue when saving USD files directly from USD Composer to the AWS Nucleus server still persists. Could you provide any further troubleshooting steps or insights to resolve this issue?

Thank you for your assistance.

Best regards,