当AWS登录后的Kibana抛出“Missing Role”错误时,可能是由于缺少正确的IAM角色或权限配置所致。以下是一些可能的解决方法。
aws iam create-role --role-name KibanaRole --assume-role-policy-document '{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Principal": {
"Service": "kibana.amazonaws.com"
},
"Action": "sts:AssumeRole"
}]
}'
aws iam put-role-policy --role-name KibanaRole --policy-name KibanaPolicy --policy-document '{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": [
"es:Describe*",
"es:List*",
"es:Get*",
"es:ESHttp*"
],
"Resource": "*"
}]
}'
elasticsearch.username: "kibana"
elasticsearch.password: "password"
elasticsearch.hosts: ["https://your-es-endpoint"]
elasticsearch.requestHeadersWhitelist: ["Authorization"]
elasticsearch.ssl.certificateAuthorities: ["/path/to/your/cert.pem"]
elasticsearch.ssl.verificationMode: full
elasticsearch.ssl.keystore.path: /path/to/your/keystore.p12
elasticsearch.ssl.keystore.password: your_keystore_password
elasticsearch.ssl.truststore.path: /path/to/your/truststore.p12
elasticsearch.ssl.truststore.password: your_truststore_password
elasticsearch.ssl.key: /path/to/your/key.pem
elasticsearch.ssl.certificate: /path/to/your/cert.pem
elasticsearch.ssl.keyPassphrase: your_key_passphrase
elasticsearch.ssl.privateKey: /path/to/your/private/key.pem
确保上述配置中的角色名称、密码和Elasticsearch主机等与实际情况匹配。
这些解决方法应该能够解决AWS登录后Kibana抛出“Missing Role”错误的问题。如果问题仍然存在,建议检查AWS CloudWatch日志以获取更详细的错误信息,并进一步调查和解决问题。