How do I create a client with the V4 Signing process about elasticsearch-net-aws HOT 7 CLOSED

If you must supply an access key explicitly you can use this constructor. However I recommend supplying credentials to your application via EC2 instance profile or other means. See this guide for more information.

This library uses the AWSSDK's normal means of loading credentials and should work just like other service clients in that library. If you don't supply credentials then it will try to look them up automatically via environment variables, aws profile, and ec2 instance metadata.

from elasticsearch-net-aws.

Thanks for replying so quickly.

I should have said I'm using the AWS Elastic Search service - does this matter?

I have an access policy allowing a particular account (my account) and I'm unsure whether I have to provide my username and password, or whether I need to create an access key/secret?

Thanks again

from elasticsearch-net-aws.

It depends on where you're running your code. If you are going to run on an EC2 instance you can simply assign a role that has access to your Elasticsearch Service domain to the EC2 instance. The same goes for running on AWS Lambda. If you're running from your local computer then you will need to use an access key. You can supply the access key to your application in few different ways described in this guide

from elasticsearch-net-aws.

I am going to be calling the Elasticsearch service from Azure functions so I think I'll need to use the constructor.

I just had a look at the documentation but it's not clear how I should create the credentials for my use case.

Edit: I just found this document which shows AWSCredentials subclasses

from elasticsearch-net-aws.

If you're using Azure this library won't work for. This will only work for Amazon AWS.

from elasticsearch-net-aws.

Thanks for letting me know -I didn't know that and should have mentioned Azure sooner...

from elasticsearch-net-aws.

You're welcome.

from elasticsearch-net-aws.