Extensions for the LocalStack.NET Client to integrate with .NET Core configuration and dependency injection frameworks. The extensions also provides wrapper around AWSSDK.Extensions.NETCore.Setup to use both LocalStack and AWS side-by-side
This is an easy-to-use .NET client for LocalStack.
The client library provides a thin wrapper around aws-sdk-net which
automatically configures the target endpoints to use LocalStack for your local cloud
application development.
LocalStack.Client.Extensions is extensions for the LocalStack.NET Client to integrate with .NET Core configuration and dependency injection frameworks. The extensions also provides wrapper around AWSSDK.Extensions.NETCore.Setup to use both LocalStack and AWS side-by-side.
This approach is recommended since AWSSDK.Extensions.NETCore.Setup is very popular and also it is best practice for using AWSSDK.NET with .NET Core, .NET 5 or .NET 6
Installation
The easiest way to install LocalStack .NET Client Extensions is via nuget:
Install-Package LocalStack.Client.Extensions
Or use dotnet cli
dotnet add package LocalStack.Client.Extensions
Usage
The usage is very similar to AWSSDK.Extensions.NETCore.Setup with some differences.
The most important difference is that AddAwsService extensions method is used instead of AddAWSService used in AWSSDK.Extensions.NETCore.Setup. The reason for this will be explained later in this section.
In addition, the AddLocalStack extension method is also used.
(Alternatively, AddAWSServiceLocalStack method can be used to prevent mix-up with AddAWSService.)
AddLocalStack extension method is responsible for both configurations and adding of LocalStack.Client dependencies to service collection.
You can configure LocalStack.Client by using entries in the appsettings.json files, as shown in the following example.
All the entries above are has shown with default values (except UseLocalStack, it's false by default).
So the above entries do not need to be specified.
What is entered for the aws credential values in the Session section does not matter for LocalStack.
RegionName is important since LocalStack creates resources by spesified region.
Config section contains important entries for local development. Starting with LocalStack releases after v0.11.5, all services are now exposed via the edge service (port 4566) only! If you are using a version of LocalStack lower than v0.11.5, you should set UseLegacyPorts to true. Edge port can be set to any available port (see LocalStack configuration section). If you have made such a change in LocalStack's configuration, be sure to set the same port value to EdgePort in the Config section. For LocalStackHost and UseSsl entries, corresponding to the LocalStack configuration should be used.
The following sample setting files can be used to use both LocalStack.Client andAWSSDK.Extensions.NETCore.Setup in different environments.
AddAwsService is equivalent of AddAWSService used in AWSSDK.Extensions.NETCore.Setup. It decides which factory to use when resolving any AWS Service. To decide this, it checks the UseLocalStack entry.
If the UseLocalStack entry is true, it uses the Session class of LocalStack.Client to create AWS Service. If the UseLocalStack entry is false, it uses the ClientFactory class of AWSSDK.Extensions.NETCore.Setup which is also used by original AddAWSService.
It is named as AddAwsService to avoid name conflict with AddAWSService.
(Alternatively, AddAWSServiceLocalStack method can be used to prevent mix-up with AddAWSService.)
useServiceUrl Parameter
LocalStack.NET uses ClientConfig to configure AWS clients to connect LocalStack. ClientConfig has two properties called ServiceUrl and RegionEndpoint, these are mutually exclusive properties. Whichever property is set last will cause the other to automatically be reset to null. LocalStack.NET has given priority to the RegionEndpoint property and the us-east-1 region is used as the default value (Different regions can be set by using appsettings.json, see RegionName entry. Because of it sets the RegionEndpoint property after the ServiceUrl property, ServiceUrl will be set to null.
To override this behavior, the useServiceUrl optional parameter can be set to true as below.
The RegionEndpoint is not applicable for services such as AWS MediaStore, Iot. The optional parameter useServiceUrl can be useful for use in such scenarios.
Standalone Initialization
If you do not want to use any DI library, you have to instantiate SessionStandalone as follows.
/*
* ==== Default Values ====
* AwsAccessKeyId: accessKey (It doesn't matter to LocalStack)
* AwsAccessKey: secretKey (It doesn't matter to LocalStack)
* AwsSessionToken: token (It doesn't matter to LocalStack)
* RegionName: us-east-1
* ==== Custom Values ====
* var sessionOptions = new SessionOptions("someAwsAccessKeyId", "someAwsAccessKey", "someAwsSessionToken", "eu-central-");
*/
var sessionOptions = new SessionOptions();
/*
* ==== Default Values ====
* LocalStackHost: localhost
* UseSsl: false
* UseLegacyPorts: false (Set true if your LocalStack version is 0.11.5 or above)
* EdgePort: 4566 (It doesn't matter if use legacy ports)
* ==== Custom Values ====
* var configOptions = new ConfigOptions("mylocalhost", false, false, 4566);
*/
var configOptions = new ConfigOptions();
ISession session = SessionStandalone.Init()
.WithSessionOptions(sessionOptions)
.WithConfigurationOptions(configOptions).Create();
var amazonS3Client = session.CreateClientByImplementation<AmazonS3Client>();
CreateClientByInterface<TSerice> method can also be used to create AWS service, as follows
var amazonS3Client = session.CreateClientByInterface<IAmazonS3>();
useServiceUrl Parameter
LocalStack.NET uses ClientConfig to configure AWS clients to connect LocalStack. ClientConfig has two properties called ServiceUrl and RegionEndpoint, these are mutually exclusive properties. Whichever property is set last will cause the other to automatically be reset to null. LocalStack.NET has given priority to the RegionEndpoint property and the us-east-1 region is used as the default value (Different regions can be set by using appsettings.json, see RegionName entry. Because of it sets the RegionEndpoint property after the ServiceUrl property, ServiceUrl will be set to null.
To override this behavior, the useServiceUrl optional parameter can be set to true as below.
var sessionOptions = new SessionOptions();
var configOptions = new ConfigOptions();
ISession session = SessionStandalone.Init()
.WithSessionOptions(sessionOptions)
.WithConfigurationOptions(configOptions).Create();
var amazonS3Client = session.CreateClientByImplementation<AmazonMediaStoreDataClient>(true);
var amazonS3Client = session.CreateClientByImplementation<AmazonS3Client>();
The RegionEndpoint is not applicable for services such as AWS MediaStore, Iot. The optional parameter useServiceUrl can be useful for use in such scenarios.
CreateClientByInterface<TSerice> method can also be used to create AWS service, as follows
var amazonS3Client = session.CreateClientByInterface<IAmazonMediaStoreData>(true);
We welcome feedback, bug reports, and pull requests!
Use commands below to get you started and test your code:
Windows
build.ps1
Linux
./build.sh
About Sandbox Applications
In addition to Unit Tests and Functional Test, LocalStack .Net Repository has various sandbox console applications for both testing and example purposes under tests/sandboxes
Sandbox applications include various examples of initialization methods of LocalStack.Client (see Usage section) and common AWS applications. They provide a convenient and safe environment for those who want to make developments in the library.
To run sandbox applications with LocalStack container, console application called LocalStack.Container has been developed. It uses Dotnet Testcontainer to bootstrap LocalStack. Experiments can be made by running LocalStack.Container application first and then any sandbox application.
