-
Notifications
You must be signed in to change notification settings - Fork 170
feat: Add AWS (SIG4) Connection #304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* Allows adding config access utilising https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html * Utilises https://github.com/mhart/aws4fetch/
Hey @ChrisMcKee , thanks for taking the time to implement this. I currently do not use aws - can you add detailed instructions for how to setup elasticsearch in aws, including the credentials, iam, etc, so i can setup and validate this? |
Added the translations to the locale. |
@ChrisMcKee huge thanks for the localstack setup, this really helps (will try tomorrow). There is still some work to do, e.g. support for elasticvue desktop. I will work on this and cherrypick from your PR. Thanks! |
I've been running it locally using tauri:dev is desktop something else? |
Elasticvue desktop does not use javascript fetch, it uses |
@cars10 tls parfait I didn't realise the |
Thanks again @ChrisMcKee for your work on this! I added it to 1.8.0, cherrypicked the relevant changes. |
Great tool; I long missed the old elastic plugins (head plugin) and kibana is pretty useless for administration use.
I've added in AWS connections as an option and tested it; the playwright tests were hit and miss on run and the last one said the filter wasn't working so I've included a screenshot showing it works fine so it doesnt look like I'm losing my mind.