NextGenSoftware.OASIS.API.Providers.AWSOASIS
2.0.6
dotnet add package NextGenSoftware.OASIS.API.Providers.AWSOASIS --version 2.0.6
NuGet\Install-Package NextGenSoftware.OASIS.API.Providers.AWSOASIS -Version 2.0.6
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.AWSOASIS" Version="2.0.6" />
<PackageVersion Include="NextGenSoftware.OASIS.API.Providers.AWSOASIS" Version="2.0.6" />
<PackageReference Include="NextGenSoftware.OASIS.API.Providers.AWSOASIS" />
paket add NextGenSoftware.OASIS.API.Providers.AWSOASIS --version 2.0.6
#r "nuget: NextGenSoftware.OASIS.API.Providers.AWSOASIS, 2.0.6"
#:package NextGenSoftware.OASIS.API.Providers.AWSOASIS@2.0.6
#addin nuget:?package=NextGenSoftware.OASIS.API.Providers.AWSOASIS&version=2.0.6
#tool nuget:?package=NextGenSoftware.OASIS.API.Providers.AWSOASIS&version=2.0.6
NextGenSoftware.OASIS.API.Providers.AWSOASIS
Connects OASIS to DynamoDB through the official AWSSDK.DynamoDBv2 client. AWSOASIS reuses DynamoDBOASIS storage operations with AWS-specific provider identity and configuration; this adapter does not implement S3 object storage. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one
Current verification scope
The retained provider/history runner is Scripts/TestHosts/Run-ReusableDynamoHistoryTests.ps1 (-FullAwsSuite for the AWS suite); it reuses the installed runtime, shared dependency cache and fixed output directories. Scripts/run_aws_provider_evidence.ps1 is the earlier standalone evidence entry point, not a substitute for the current history/reconciliation gates. Local native tests do not certify hosted AWS credentials, costs, scale or all provider interfaces/options. Do not overwrite retained reports or bypass unresolved fixture journals. The older in-memory runner is not a durable production recovery journal.
Save operations require an authoritative SDK HTTP 200 acknowledgement before publishing caller IDs/provider keys. Missing/invalid responses retain mutation-reconciliation evidence; do not blindly retry them. Avatar-detail records persist the provider-specific storage key and deletion projection, like profile/holon records. Historical record APIs use the existing shared embedded-history codec: version zero selects latest, positive versions select the requested retained version, and negative versions are rejected. Enable IsVersionControlEnabled to create histories; disabling new history creation does not erase already retained archives. An absent version is not replaced with latest. Historical credential authentication remains explicitly disallowed; record history is not credential authority. Additional interface, concurrency, recovery and hosted-release gates remain open. Current evidence and limitations are recorded in Docs/WIP/HyperDrive-Providers/HYPERDRIVE_V2_CURRENT_RELEASE_GATES.md.
Exports additionally support version=-1 for all validated stored versions, with
owner/deletion filtering per version and stored archived child payloads. This is
not a cross-version graph snapshot. Values below -1 remain invalid; ordinary
point/collection reads do not accept negative versions. Username/email export
selectors use the current avatar identity independently of the holon version.
Installation
dotnet add package NextGenSoftware.OASIS.API.Providers.AWSOASIS
NuGet versions · Source project
Choose a published version compatible with the other OASIS packages in your application. This guide describes current source; older packages may not contain the same functionality.
Frameworks and dependencies
Declared target frameworks: net10.0.
Direct external package references:
NextGenSoftware.OASIS.API.Core
Project references and conditional dependency versions are recorded in the source project. NuGet restore resolves packaged dependencies; do not mix arbitrary DLLs from different release graphs.
Integration and configuration
Use this package for the responsibility described above, alongside its owning OASIS runtime/provider integration. Inspect the source project's public APIs and owning component documentation for construction and configuration; this package installation command does not start an API server, authenticate an avatar or provision an external service.
Provider adapters require their respective service configuration and credentials. Runtime libraries require the host application's lifecycle and persistent paths where applicable. Supply only the settings actually required by the owning component; do not copy production DNA into a client or public release.
Errors and security
For APIs returning OASISResult<T>, check IsError, ErrorCode and Message; do not treat a failed result as success. Preserve useful diagnostics without logging access tokens, passwords or private keys. Keep secrets in the host's appropriate protected configuration or platform storage.
Platform requirements
Target-framework compatibility is not proof that every native dependency or external service works on every operating system. Check the selected version's platform assets and native/service requirements before deployment. Unity/mobile integrations require their supported platform layer and packaging workflow; a managed NuGet archive alone does not establish Android/iOS, IL2CPP or two-device convergence acceptance.
Troubleshooting
- Restore/assembly mismatch: pin a coherent set of package versions and inspect the dependency graph.
- Configuration or authentication error: inspect the owning component's result diagnostics and service requirements without exposing secrets.
- Native loading failure: verify OS/architecture and required native artifacts rather than suppressing the error.
- Missing functionality in an older version: compare the immutable released source and release notes, not only the moving Development branch.
Releases and further documentation
[Verified release matrix](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/OASIS_RELEASE_STATUS.md) · [Documentation audit](https://github.com/NextGenSoftwareUK/OASIS/blob/Development/Docs/WIP/Release and Status/RELEASE_DOCUMENTATION_AUDIT.md)
Published NuGet versions are immutable. Updated documentation ships with a new unpublished package version after checked promotion and publication. This metadata-backed guide does not replace product-specific API examples or claim unverified platform tests.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- NextGenSoftware.OASIS.API.Core (>= 2.0.7)
- NextGenSoftware.OASIS.API.Providers.DynamoDBOASIS (>= 2.0.4)
- NextGenSoftware.OASIS.Common (>= 2.0.1)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on NextGenSoftware.OASIS.API.Providers.AWSOASIS:
| Package | Downloads |
|---|---|
|
NextGenSoftware.OASIS.OASISBootLoader
The OASIS BootLoader provides a single entry point to initialise the entire OASIS ecosystem in any .NET application. Reads OASISDNA configuration, registers and activates all configured providers, sets up Auto-FailOver/LoadBalancing, and returns a ready-to-use OASIS instance. Integrate 55+ decentralised networks into your app with just a few lines of code. Part of the OASIS Omniverse at https://oasisomniverse.one |
GitHub repositories
This package is not used by any popular GitHub repositories.
NextGenSoftware.OASIS.API.Providers.AWSOASIS v2.0.6
Connects the OASIS to Amazon DynamoDB through AWSSDK.DynamoDBv2 for holon and avatar persistence. The same SDK path supports AWS-hosted DynamoDB and DynamoDB Local for repeatable integration evidence. Part of the OASIS HOT-Swappable Provider Architecture. Ecosystem: https://oasisomniverse.one/
What's new since v2.0.5
- Initial validated package contents and metadata for this release line.
Full changelog
https://github.com/NextGenSoftwareUK/OASIS/commits/master/Providers/Cloud/NextGenSoftware.OASIS.API.Providers.AWSOASIS