CODEWITHSUNDEEP
c#asp.net-core.net-core-2.0
aman
aman

Reputation: 6242

Creating AWS initialization class

I have a API which connects to my dynamo db. My API has quite a few endpoints for GET, POST, Delete etc. I am using the following code:

var awsCredentials = Helper.AwsCredentials(id, password);
var awsdbClient = Helper.DbClient(awsCredentials, "us-east-2");
var awsContext = Helper.DynamoDbContext(awsdbClient);

List<ScanCondition> conditions = new List<ScanCondition>();
var response = await context.ScanAsync<MyData>(conditions).GetRemainingAsync();

return response.ToList();

The first three lines of my code ie setting awsCredentials, awsdbClient & awsContext are repeated in each of my WEB API call.

And this is my static helper class:

public static class Helper
{
    public static BasicAWSCredentials AwsCredentials(string id, string password)
    {
        var credentials = new BasicAWSCredentials(id, password);
        return credentials;
    }
    public static AmazonDynamoDBClient DynamoDbClient(BasicAWSCredentials credentials, RegionEndpoint region)
    {
        var client = new DBClient(credentials, region);
        return client;
    }
    public static DynamoDBContext DynamoDbContext(AmazonDynamoDBClient client)
    {
        var context = new DynamoDBContext(client);
        return context;
    }
}

I use this helper class in my API to initialize AWS.

Is there a better way to initialize this?

Upvotes: 1

Views: 694

Answers (1)

gunr2171
gunr2171

Reputation: 17520

Let's take advantage of ASP.Net's built-in Dependency Injection.

We need to make a quick interface to expose the values you need.

public interface IDynamoDbClientAccessor
{
    DynamoDBContext GetContext();
}

And a settings class that we'll use in a bit.

public class DynamoDbClientAccessorSettings
{
    public string Id { get; set; }
    public string Password { get; set; }
    public string Region { get; set; }
}

Now the concrete class.

public class DynamoDbClientAccessor : IDynamoDbClientAccessor
{
    private readonly DynamoDbClientAccessorSettings settings;

    public DynamoDbClientAccessor(IOptions<DynamoDbClientAccessorSettings> options)
    {
        settings = options?.Value ?? throw new ArgumentNullException(nameof(options));
    }

    public DynamoDBContext GetContext()
    {
        // You have the option to alter this if you don't
        // want to create a new context each time. 
        // Have a private variable at the top of this class
        // of type DynamoDBContext. If that variable is not null,
        // return the value. If it is null, create a new value,
        // set the variable, and return it.

        var awsCredentials = Helper.AwsCredentials(settings.Id, settings.Password);
        var awsdbClient = Helper.DbClient(awsCredentials, settings.Region);
        var awsContext = Helper.DynamoDbContext(awsdbClient);

        return awsContext;
    }
}

Hook all of this up in your Startup class

services.AddSingleton<IDynamoDbClientAccessor, DynamoDbClientAccessor>();
services.Configure<DynamoDbClientAccessorSettings>(c =>
{
    c.Id = "YOUR ID";
    c.Password = "YOUR PASSWORD";
    c.Region = "YOUR REGION";
});

Now in your controller or other DI service you ask for a IDynamoDbClientAccessor instance in the constructor.

Once you get more familar with Dependency Injection you'll be able to break apart more things into their own dependent services. As Daniel says, the AWS SDK even provides some interfaces for you to use which can help as well.

Upvotes: 2

Related Questions