Les traductions sont fournies par des outils de traduction automatique. En cas de conflit entre le contenu d'une traduction et celui de la version originale en anglais, la version anglaise prévaudra.
# Hue
Hue (Hadoop User Experience) est une interface utilisateur graphique open source, basée sur le web, à utiliser avec Amazon EMR et Apache Hadoop. Hue regroupe plusieurs projets d'écosystème Hadoop différents au sein d'une interface configurable. Amazon EMR a également ajouté des personnalisations spécifiques à Hue sur Amazon EMR. Hue joue le rôle de serveur frontal pour les applications exécutées sur votre cluster, ce qui vous permet d'interagir avec les applications via une interface plus conviviale ou qui vous est plus familière. Grâce aux applications figurant dans Hue, telles que les éditeurs Hive et Pig, il n'est plus nécessaire de se connecter au cluster pour exécuter des scripts de façon interactive avec le shell de chaque application. Une fois que le cluster est lancé, vous pouvez interagir entièrement avec vos applications en utilisant Hue ou une interface similaire. Pour plus d'informations sur Hue, consultez [http://gethue.com](http://gethue.com).
Hue est installé par défaut lorsque vous lancez votre cluster à l'aide de la console Amazon EMR. Vous pouvez choisir de ne pas installer Hue à l'aide des **Options avancées** dans la console Amazon EMR lorsque vous lancez un cluster, ou en spécifiant explicitement l'option `--applications` et en omettant Hue lorsque vous utilisez `create-cluster` à partir de l' AWS CLI.
**Topics**
+ [Informations sur la version de Hue](#emr-Hue-versions)
+ [Fonctionnalités prises en charge et non prises en charge de Hue sur Amazon EMR](emr-hue-supported-features.md)
+ [Considérations](emr-hue-considerations.md)
+ [Connexion à l'interface utilisateur Web de Hue](accessing-hue.md)
+ [Utilisation de Hue avec une base de données distante dans Amazon RDS](hue-rds.md)
+ [Configurations avancées pour Hue](advanced-configurations.md)
+ [Historique des versions de Hue](Hue-release-history.md)
## Informations sur la version de Hue
**Version Hue pour 7.12.0**
Le tableau suivant répertorie la version de Hue incluse dans la dernière version d’Amazon EMR série 7.x, ainsi que les composants qu’Amazon EMR installe avec Hue.
Pour connaître la version des composants installés avec Hue dans cette version, consultez la [version 7.12.0 Versions des composants](emr-7120-release.md).
**Informations de version Hue pour emr-7.12.0**
| Étiquette de version Amazon EMR | Version Hue | Composants installés avec Hue |
| --- | --- | --- |
| emr-7,12.0 | Hue 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-hdfs-zkfc, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
**Version de Hue pour 6.15.0**
Le tableau suivant répertorie la version de Hue incluse dans la dernière version d'Amazon EMR série 6.x, ainsi que les composants qu'Amazon EMR installe avec Hue.
Pour connaître la version des composants installés avec Hue dans cette version, consultez les [versions des composants de la version 6.15.0](emr-6150-release.md).
**Informations sur la version de Hue pour emr-6.15.0**
| Étiquette de version Amazon EMR | Version Hue | Composants installés avec Hue |
| --- | --- | --- |
| emr-6.15.0 | Hue 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
**Version Hue pour 5.36.2**
Le tableau suivant répertorie la version de Hue incluse dans la dernière version d'Amazon EMR série 5.x, ainsi que les composants qu'Amazon EMR installe avec Hue.
Pour connaître la version des composants installés avec Hue dans cette version, consultez la [version 5.36.2 Versions des composants](emr-5362-release.md).
**Informations de version Hue pour emr-5.36.2**
| Étiquette de version Amazon EMR | Version Hue | Composants installés avec Hue |
| --- | --- | --- |
| emr-5.36.2 | Hue 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
# Fonctionnalités prises en charge et non prises en charge de Hue sur Amazon EMR
Avec Amazon EMR 7.0.0 et versions ultérieures, Hue requiert Python 3.9 ou version ultérieure. Lorsque vous utilisez le chiffrement en transit, vous devez utiliser une clé de chiffrement de 2 048 bits.
+ Amazon S3 et Hadoop File System (HDFS) Browser
+ Avec les autorisations appropriées, vous pouvez parcourir et transférer les données entre le stockage HDFS éphémère et les compartiments S3 appartenant à votre compte.
+ Par défaut, les superutilisateurs de Hue peuvent accéder à tous les fichiers auxquels les rôles IAM Amazon EMR sont autorisés à accéder. Les utilisateurs nouvellement créés n'ont pas automatiquement les autorisations d'accéder à l'explorateur de fichiers Amazon S3 et doivent avoir les autorisations `filebrowser.s3_access` activées pour leur groupe.
+ Hive – Exécutez des requêtes interactives sur vos données. Vous pouvez également créer un prototype d'interrogation par programmation ou par lot.
+ Pig – Exécutez des scripts sur vos données ou exécutez des commandes interactives.
+ Oozie – Créer et surveiller des flux de travail Oozie.
+ Gestionnaire Metastore – Affichez et manipulez le contenu de la metastore Hive (importation/création, suppression, etc.).
+ Explorateur de tâches – Affichez l’état des tâches Hadoop que vous avez soumises.
+ Gestion des utilisateurs – Gérez les comptes Hue et intégrez les utilisateurs LDAP à Hue.
+ AWS Exemples — Il existe plusieurs « ready-to-run » exemples de traitement d'échantillons de données provenant de divers AWS services à l'aide d'applications dans Hue. Lorsque vous vous connectez à Hue, vous êtes dirigé vers l'application Hue Home où les exemples de données sont préinstallés.
+ Livy Server est pris en charge uniquement dans la version Amazon EMR 5.9.0 et ultérieure.
+ Pour utiliser Hue Notebook pour Spark, vous devez installer Hue avec Livy et Spark.
+ Trino/Presto – Hue prend en charge la connexion aux serveurs de données Trino et Presto. Avec Amazon EMR 7.0.0 et versions ultérieures, cette connectivité est facilitée par des connecteurs `trino-python-client` et `presto-python-client`. Les versions antérieures à 7.0.0 utilisent un connecteur JDBC via une passerelle JDBC.
+ Le tableau de bord Hue n'est pas pris en charge.
+ PostgreSQL n'est pas pris en charge.
# Considérations
Tenez compte des limites suivantes lorsque vous utilisez [Hue](https://gethue.com) sur Amazon EMR.
## Performances avec de grandes tables de métadonnées Hue
Si la base de données de métadonnées Hue devient trop volumineuse, les performances risquent de se dégrader. Pour vérifier la taille des tables, connectez-vous d'abord au nœud principal du cluster Amazon EMR sur Amazon EC2 avec SSH et exécutez la commande `sudo mysql -u root` pour démarrer la CLI MySQL. Pour obtenir la taille de votre table, exécutez la requête`SELECT COUNT(*) FROM hue.`. Consultez ce qui suit pour savoir ce qui ** peut être :
+ document\$1bureau
+ document\$1bureau 2
+ oozie\$1job
+ requête beeswax\$1saved
+ session à la cire d'abeille
+ histoire de beeswax\$1query
Si l'exécution de cette requête renvoie un nombre supérieur à 100 000, vous devez exécuter la commande de nettoyage suivante pour supprimer les anciens enregistrements.
```
cd /opt/cloudera/parcels/CDH/lib/hue # Hue home directory ./build/env/bin/hue desktop_document_cleanup
```
Pour plus d'informations sur le nettoyage de votre base de données, consultez la [page de référence de la documentation Hue](https://docs.gethue.com/administrator/administration/reference/#general).
Hue ne nettoie pas automatiquement les tables, mais les versions 5.12.0 et supérieures d'Amazon EMR fournissent une méthode pour supprimer les anciens documents des tables. Créez le script shell suivant et exécutez-le en tant qu'étape dans un cluster Amazon EMR avec un paramètre entier qui représente le nombre maximal de jours pendant lesquels les documents doivent être conservés dans la base de données de métadonnées.
```
#!/bin/bash
if grep isMaster /mnt/var/lib/info/instance.json | grep false;
then
echo "This is not the primary node; do nothing, exiting"
exit 0
fi
while [ ! -f /usr/lib/hue/desktop/core/src/desktop/management/commands/desktop_document_cleanup.py ]
do
sleep 1
done
sudo systemctl stop hue.service
sudo sed -i 's+ LOG.warn+ # LOG.warn+g' /usr/lib/hue/desktop/core/src/desktop/management/commands/desktop_document_cleanup.py
sudo /usr/lib/hue/build/env/bin/hue desktop_document_cleanup --keep-days $1
sudo systemctl start hue.service
```
## Incompatibilité entre les versions de Hue
Si vous utilisez la même base de données de métadonnées Hue sur plusieurs clusters compatibles Hue, nous recommandons que ces clusters exécutent la même version de Hue. Les différentes versions de Hue peuvent avoir des schémas différents pour la base de données de métadonnées Hue. L'utilisation de la même base de données pour différentes versions peut entraîner l'échec d'une installation de Hue. Par exemple, essayer d'utiliser la même base de données pour deux clusters sur lesquels les versions 4.10.0 et 4.11.0 sont installées peut provoquer des erreurs de connexion pour les utilisateurs qui tentent de se connecter au cluster 4.10.0.
Pour obtenir la liste des labels de version d'Amazon EMR et des versions installées correspondantes de Hue, consultez l'historique des versions de [Hue](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/Hue-release-history.html).
# Connexion à l'interface utilisateur Web de Hue
La connexion à l'interface utilisateur web Hue est identique à la connexion à n'importe quelle interface HTTP hébergée sur le nœud principal d'un cluster. La procédure suivante décrit comment accéder à l'interface utilisateur de Hue. Pour plus d'informations, consultez [Affichage des interfaces web hébergées sur les clusters EMR](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-web-interfaces.html) dans le *Guide de gestion Amazon EMR*.
**Pour afficher l'interface utilisateur Web de Hue**
1. Suivez ces instructions pour [Configurer un tunnel SSH vers le nœud principal à l'aide du redirecteur de port dynamique](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-ssh-tunnel.html) dans le *Guide de gestion Amazon EMR*.
1. Tapez l'adresse suivante dans votre navigateur pour ouvrir l'interface Web **Hue** : `http://master public DNS:8888` où se *master public dns* trouve le nom DNS public de votre nœud maître de cluster, par exemple`ec2-11-22-333-44.compute-1.amazonaws.com`.
1. Sur l'écran de connexion à Hue, si vous êtes administrateur et que vous vous connectez pour la première fois, saisissez un nom d'utilisateur et un mot de passe pour créer votre supercompte Hue, puis sélectionnez **Créer un compte**. Sinon, tapez votre nom d'utilisateur et votre mot de passe, puis sélectionnez **Create account (Créer un compte)**, ou saisissez les informations d'identification fournies par votre administrateur.
# Utilisation de Hue avec une base de données distante dans Amazon RDS
Par défaut, les informations utilisateur et les historiques de requêtes Hue sont stockés dans une base de données MySQL locale sur le nœud maître. Vous pouvez également créer un ou plusieurs clusters compatibles avec Hue à l'aide d'une configuration stockée dans Amazon S3 et d'une base de données MySQL dans Amazon Relational Database Service (Amazon RDS). Cela vous permet de conserver les informations utilisateur et l'historique des requêtes créés par Hue sans maintenir votre cluster Amazon EMR en cours d'exécution. Nous vous recommandons d'utiliser le chiffrement côté serveur Amazon S3 pour stocker le fichier de configuration.
Commencez par créer la base de données distante pour Hue.
**Pour créer la base de données MySQL externe**
1. Ouvrez la console Amazon RDS à l'adresse [https://console.aws.amazon.com/rds/](https://console.aws.amazon.com/rds/).
1. Cliquez sur **Launch a DB Instance (Lancement d'une instance DB)**.
1. Choisissez MySQL et cliquez sur **Select (Sélectionner)**.
1. Laissez la sélection par défaut de **Multi-AZ Deployment and Provisioned IOPS Storage (Déploiement multi-AZ et Stockage sur volumes IOPS dimensionnés)** et cliquez sur **Next (Suivant)**.
1. Conservez les valeurs par défaut des spécifications de l'instance, spécifiez les paramètres, puis cliquez sur **Next (Suivant)**.
1. Dans la page Configuration de paramètres avancés, choisissez un groupe de sécurité et un nom de base de données adéquats. Le groupe de sécurité que vous utilisez doit permettre au moins l'accès TCP entrant pour le port 3306 à partir du nœud maître de votre cluster. Si vous n'avez pas créé votre cluster à ce stade, vous pouvez autoriser tous les hôtes à se connecter au port 3306 et ajuster le groupe de sécurité, une fois que vous avez lancé le cluster. Cliquez sur **Launch DB Instance (Lancement d'une instance DB)**.
1. Dans le tableau de bord RDS, sélectionnez **Instances** et choisissez l'instance que vous venez de créer. Lorsque votre base de données est disponible, notez la dbname (nom de la base de données), le nom d'utilisateur, le mot de passe et le nom d'hôte d'instance RDS. Vous allez utiliser ces informations pour créer et configurer votre cluster.
**Pour spécifier une base de données MySQL externe pour Hue lors du lancement d'un cluster à l'aide du AWS CLI**
Pour spécifier une base de données MySQL externe pour Hue lors du lancement d'un cluster à l'aide de AWS CLI, utilisez les informations que vous avez indiquées lors de la création de votre instance RDS pour la configurer à l'`hue.ini`aide d'un objet de configuration
**Note**
Vous pouvez créer plusieurs clusters qui utilisent la même base de données externe, mais chaque cluster partage l'historique des requêtes et les informations utilisateur.
+ À l'aide de AWS CLI, créez un cluster sur lequel Hue est installé, en utilisant la base de données externe que vous avez créée et en référençant un fichier de configuration avec une classification de configuration pour Hue qui spécifie les propriétés de la base de données. L'exemple suivant crée un cluster avec Hue installé en référençant un fichier de configuration dans Amazon S3, `myConfig.json`, qui spécifie la configuration de la base de données.
**Note**
Les caractères de continuation de ligne Linux (\$1) sont inclus pour des raisons de lisibilité. Ils peuvent être supprimés ou utilisés dans les commandes Linux. Pour Windows, supprimez-les ou remplacez-les par un caret (^).
```
aws emr create-cluster --release-label emr-7.12.0 --applications Name=Hue Name=Spark Name=Hive \
--instance-type m5.xlarge --instance-count 3 \
--configurations https://s3.amazonaws.com/amzn-s3-demo-bucket/myfolder/myConfig.json --use-default-roles
```
Vous trouverez ci-dessous des exemples de contenus du fichier `myConfig.json`. Remplacez*dbname*, *username**password*, et par *RDS instance hostname* les valeurs que vous avez notées précédemment dans le tableau de bord RDS.
```
[{
"Classification": "hue-ini",
"Properties": {},
"Configurations": [
{
"Classification": "desktop",
"Properties": {},
"Configurations": [
{
"Classification": "database",
"Properties": {
"name": "dbname",
"user": "username",
"password": "password",
"host": "RDS instance hostname",
"port": "3306",
"engine": "mysql"
},
"Configurations": []
}
]
}
]
}]
```
## Résolution des problèmes
**En cas de basculement d'Amazon RDS**
Il est possible que les utilisateurs rencontrent des retards en exécutant une requête parce que l'instance de base de données Hue ne répond pas ou est en cours de basculement. Voici quelques faits et directives pour ce problème :
+ Si vous vous connectez à la console Amazon RDS, vous pouvez rechercher des événements de basculement. Par exemple, pour voir si un basculement est en cours ou a eu lieu, recherchez des événements tels que « Le basculement de l'instance Multi-AZ a commencé » et « Basculement de l'instance Multi-AZ terminé. »
+ Il faut environ 30 secondes à une instance RDS pour terminer un basculement.
+ Si vous recevez des longer-than-normal réponses à des requêtes dans Hue, essayez de réexécuter la requête.
# Configurations avancées pour Hue
Cette section comprend les rubriques suivantes.
**Topics**
+ [Configuration de Hue pour les utilisateurs LDAP](hue-ldap.md)
# Configuration de Hue pour les utilisateurs LDAP
L'intégration sur LDAP permet aux utilisateurs de se connecter à Hue à l'aide d'informations d'identification existantes stockées dans un annuaire LDAP. Lorsque vous intégrez Hue sur LDAP, vous n'avez pas besoin de gérer indépendamment des informations utilisateur dans Hue. Les informations ci-dessous illustrent l'intégration de Hue avec Microsoft Active Directory, mais les options de configuration sont analogues à n'importe quel répertoire LDAP.
Tout d'abord, l'authentification LDAP se lie au serveur et établit la connexion. Ensuite, la connexion établie est utilisée pour toutes les requêtes suivantes pour rechercher des informations utilisateur LDAP. A moins que votre serveur Active Directory autorise les connexions anonymes, une connexion doit être établie à l'aide d'un nom unique et d'un mot de passe de liaison. Le nom unique (ou DN) de liaison est défini par le paramètre de configuration `bind_dn`. Le mot de passe de liaison est défini par le paramètre de configuration `bind_password`. Hue a deux manières de lier des demandes LDAP : liaison de recherche et liaison directe. La méthode préférée pour l'utilisation de Hue avec Amazon EMR est la liaison de recherche.
Lorsque la liaison de recherche est utilisée avec Active Directory, Hue utilise l'attribut de nom d'utilisateur (défini par `user_name_attr config`) pour rechercher l'attribut qui doit être extrait du nom unique (ou DN) de la base. La liaison de recherche est utile lorsque le nom unique complet n'est pas connu pour l'utilisateur de Hue.
Par exemple, vous avez peut-être `user_name_attr config` définir pour utiliser le nom commun (ou CN). Dans ce cas, le serveur Active Directory utilise le nom d'utilisateur Hue fourni au cours de l'ouverture de session pour rechercher dans l'arborescence de répertoires un nom commun qui corresponde, en commençant par le nom unique de la base. Si le nom commun pour l'utilisateur Hue est trouvé, le nom unique de l'utilisateur est renvoyé par le serveur. Hue construit ensuite un nom unique utilisé pour authentifier l'utilisateur en effectuant une opération de liaison.
**Note**
La liaison de recherche parcourt toutes les sous-arborescences du répertoire pour trouver des noms d'utilisateur, en commençant par le nom unique de la base. Le nom unique de la base spécifié dans la configuration LDAP Hue doit être le plus proche parent du nom d'utilisateur, à défaut de quoi les performances de votre authentification LDAP pourront en être affectées.
Lorsque la liaison directe est utilisée avec Active Directory, le `nt_domain` ou `ldap_username_pattern` exact doit être utilisé pour s'authentifier. Lorsque la liaison directe est utilisée, si l'attribut de domaine nt (défini par le paramètre de configuration `nt_domain`) est défini, un modèle de nom unique d'utilisateur est créé à l'aide du formulaire : `@nt_domain`. Ce modèle est utilisé pour rechercher dans toutes les sous-arborescences du répertoire, en commençant par le nom unique de la base. Si le domaine nt n'est pas configuré, Hue recherche un modèle exact de nom unique pour l'utilisateur (défini par le paramètre de configuration `ldap_username_pattern`). Dans ce cas, le serveur recherche une valeur `ldap_username_pattern` correspondante dans toutes les sous-arborescences du répertoire, en commençant par le nom unique de la base.
**Pour lancer un cluster doté de propriétés LDAP pour Hue à l'aide du AWS CLI**
+ Pour spécifier les propriétés LDAP pour `hue-ini`, créez un cluster avec Hue installé et référencez un fichier JSON avec les propriétés de configuration pour LDAP. Un exemple de commande est présenté ci-dessous. Elle fait référence à un fichier de configuration `myConfig.json` stocké dans Amazon S3.
```
aws emr create-cluster --release-label emr-7.12.0 --applications Name=Hue Name=Spark Name=Hive \
--instance-type m5.xlarge --instance-count 3 --configurations https://s3.amazonaws.com/amzn-s3-demo-bucket/myfolder/myConfig.json.
```
Vous trouverez ci-dessous des exemples de contenus `myConfig.json`.
```
[
{
"Classification": "hue-ini",
"Properties": {},
"Configurations": [
{
"Classification": "desktop",
"Properties": {},
"Configurations": [
{
"Classification": "ldap",
"Properties": {},
"Configurations": [
{
"Classification": "ldap_servers",
"Properties": {},
"Configurations": [
{
"Classification": "yourcompany",
"Properties": {
"base_dn": "DC=yourcompany,DC=hue,DC=com",
"ldap_url": "ldap://ldapurl",
"search_bind_authentication": "true",
"bind_dn": "CN=hue,CN=users,DC=yourcompany,DC=hue,DC=com",
"bind_password": "password"
},
"Configurations": []
}
]
}
]
},
{
"Classification": "auth",
"Properties": {
"backend": "desktop.auth.backend.LdapBackend"
}
}
]
}
]
}
]
```
**Note**
Avec la version 5.21.0 et ultérieures d'Amazon EMR, vous permet de remplacer les configurations de cluster et de spécifier des classifications de configuration supplémentaires pour chaque groupe d'instances dans un cluster en cours d'exécution. Pour ce faire, utilisez la console Amazon EMR, le AWS Command Line Interface (AWS CLI) ou le AWS SDK. Pour plus d'informations, consultez [Fourniture d'une configuration pour un groupe d'instances dans un cluster en cours d'exécution](https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps-running-cluster.html).
**Pour afficher des paramètres LDAP dans Hue**
1. Vérifiez que vous disposez d'une connexion VPN active ou d'un tunnel SSH pour le nœud principal du cluster Amazon EMR. Ensuite, dans votre navigateur, tapez : 8888 *master-public-dns* pour ouvrir l'interface Web de Hue.
1. Connectez-vous à l'aide de vos informations d'identification d'administrateur Hue. Si la fenêtre **Did you know? (Le saviez vous ?)** s'ouvre, cliquez sur **Got it, prof\$1 (Compris, professeur \$1)** pour la fermer.
1. Cliquez sur l'icône **Hue** dans la barre d'outils.
1. Sur la page **About Hue (À propos de Hue)**, sélectionnez **Configuration**.
1. Dans la section **Configuration Sections and Variables (Sections et variables de configuration)**, cliquez sur **Desktop (Bureau)**.
1. Défilez à la section **ldap** pour afficher vos paramètres.
# Historique des versions de Hue
Le tableau suivant répertorie la version de Hue incluse dans chaque version d'Amazon EMR, ainsi que les composants installés avec l'application. Pour connaître les versions des composants de chaque version, consultez la section Version des composants de votre version dans [Versions Amazon EMR 7.x](emr-release-7x.md), [Versions Amazon EMR 6.x](emr-release-6x.md) ou [Versions Amazon EMR 5.x](emr-release-5x.md).
**Informations sur la version de Hue**
| Étiquette de version Amazon EMR | Version Hue | Composants installés avec Hue |
| --- | --- | --- |
| emr-7,12.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-hdfs-zkfc, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.11.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-hdfs-zkfc, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.10.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.9.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7,8.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7,7.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.6.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.5.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.4.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.3.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.2.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.36.2 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.1.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-7.0.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.15.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.14.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.13.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.12.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.11.1 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.11.0 | 4.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.10.1 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.10.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.9.1 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.9.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.8.1 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.8.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.7.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.36.1 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.36.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.6.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.35.0 | 4.10.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.5.0 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.4.0 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.3.1 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.3.0 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.2.1 | 4.8.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.2.0 | 4.8.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.1.1 | 4.7.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.1.0 | 4.7.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.0.1 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-6.0.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.34.0 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.33.1 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.33.0 | 4.9.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.32.1 | 4.8.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.32.0 | 4.8.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.31.1 | 4.7.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.31.0 | 4.7.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.30.2 | 4.6.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.30.1 | 4.6.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| emr-5.30.0 | 4.6.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mariadb-server, oozie-client, oozie-server |
| mr-5.29.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.28.1 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.28.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.27.1 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.27.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.26.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.25.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.24.1 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.24.0 | 4.4.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.23.1 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.23.0 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.22.0 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.21.2 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.21.1 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.21.0 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.20.1 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.20.0 | 4.3.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.19.1 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.19.0 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.18.1 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.18.0 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.17.2 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.17.1 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.17.0 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.16.1 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.16.0 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.15.1 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.15.0 | 4.2.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.14.2 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.14.1 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.14.0 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.13.1 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.13.0 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.12.3 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.12.2 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.12.1 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.12.0 | 4.1.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.11.4 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.11.3 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.11.2 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.11.1 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.11.0 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.10.1 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.10.0 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.9.1 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.9.0 | 4.0.1 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.8.3 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.8.2 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.8.1 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.8.0 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.7.1 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.7.0 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.6.1 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.6.0 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hadoop-yarn-timeline-server, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.5.4 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.5.3 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.5.2 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.5.1 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.5.0 | 3.12.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.4.1 | 3.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.4.0 | 3.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.3.2 | 3.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.3.1 | 3.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.3.0 | 3.11.0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.2.3 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.2.2 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.2.1 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.2.0 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.1.1 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.1.0 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-5.0.3 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-5.0.2 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-5.0.1 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-5.0.0 | 3.10.0-amzn-0 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.9.6 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.9.5 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.9.4 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.9.3 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.9.2 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.9.1 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.5 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.4 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.3 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.2 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.1 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.8.0 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.7.4 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.7.3 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.7.2 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-client, oozie-server |
| emr-4.7.1 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.7.0 | 3.7.1-amzn-7 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-kms-server, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.6.1 | 3.7.1-amzn-6 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.6.0 | 3.7.1-amzn-6 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.5.0 | 3.7.1-amzn-5 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.4.0 | 3.7.1-amzn-5 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.3.0 | 3.7.1-amzn-5 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.2.0 | 3.7.1-amzn-5 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |
| emr-4.1.0 | 3.7.1-amzn-4 | emrfs, emr-ddb, emr-goodies, emr-kinesis, hadoop-client, hadoop-hdfs-datanode, hadoop-hdfs-library, hadoop-hdfs-namenode, hadoop-yarn-nodemanager, hadoop-yarn-resourcemanager, hue-server, mysql-server, oozie-server |