1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Rather than use a proxy server that is allowed access via IP which requires you running an extra instance, you can enable IAM access and use the aws-es-kibana proxy which runs locally on the client and uses the clients IAM credentials to do the SigV4 signing. Here's another local proxy that supports IAM roles which the first one I mentioned doesn't.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 10 mois
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 8 mois