Trino Considerations - Amazon EMR
Non-configurable Trino deployment propertiesAdditional considerations
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Trino Considerations

Consider the following when you run Trino on Amazon EMR.

Non-configurable Trino deployment properties

The following table shows the different configuration options for Trino properties files.

File Configurable

log.properties

Trino: Configurable in Amazon EMR versions 6.1.0 and later. Use the prestosql-log or trino-log configuration classification.

config.properties

Trino: Configurable in Amazon EMR versions 6.1.0 and later. Use the prestosql-config or trino-config configuration classification.

hive.properties

Trino: Configurable in Amazon EMR versions 6.1.0 and later. Use the prestosql-connector-hive or trino-connector-hive configuration classification.

node.properties

Trino: Configurable in Amazon EMR versions 6.1.0 and later. Use the prestosql-node or trino-node configuration classification.

jvm.config

Not configurable.

Additional considerations

  • For Trino on EMR version 6.1.0 and later, Amazon EMR automatically configures a shared secret key for secure internal communication between cluster nodes. You don't need to do any additional configuration to enable this security feature, and you can override the configuration with your own secret key. For information about Trino internal authentication, see Trino 353 documentation: Secure internal communication.