Page History

...

A: Yes, this is supported. When a derivative private AMI is created in a customer account, the original Marketplace product codes are retained by the derived AMI. Intel cannot assist with the customization process, but will support customizations that do not interfere with the operation of Cloud Edition functionality. An example of a supported customization might be something like site-specific IDS requirements mandating certain auditing packages to be installed and configured on every instance. Rather than having to re-install/re-configure these packages every time a Lustre server instance is deployed, the customer could start an instance running our published AMI, perform the required customizations, then create a derived AMI which is private to their account. They would then substitute their private AMI’s ID in the CloudFormation templates and create a new Cloud Edition filesystem as usual. The instances created using this method would now include the customizations but would otherwise function the same.

Q: Can Cloud Edition be run in a completely private VPC (i.e. no access to the public Internet)?

A: No. Cloud Edition is a complete solution for creating and running a Highly-Available Lustre filesystem in AWS. As such, it requires access to AWS APIs in order to perform initial filesystem configuration as well as to automatically respond to failover events which would otherwise bring the filesystem to a halt. For more information about Cloud Edition network requirements and details, please see Cloud Edition Networking.