PostQuantum.FileEncryption.Aws 1.6.0

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher.

Requires NuGet 6.0.0 or higher.

dotnet add package PostQuantum.FileEncryption.Aws --version 1.6.0
                    


                    

                
NuGet\Install-Package PostQuantum.FileEncryption.Aws -Version 1.6.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="PostQuantum.FileEncryption.Aws" Version="1.6.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="PostQuantum.FileEncryption.Aws" Version="1.6.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="PostQuantum.FileEncryption.Aws" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add PostQuantum.FileEncryption.Aws --version 1.6.0
                    


                    

                
#r "nuget: PostQuantum.FileEncryption.Aws, 1.6.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package PostQuantum.FileEncryption.Aws@1.6.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=PostQuantum.FileEncryption.Aws&version=1.6.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=PostQuantum.FileEncryption.Aws&version=1.6.0
                    


                            Install as a Cake Tool

PostQuantum.FileEncryption.Aws

Envelope encryption with AWS KMS — your master key never leaves AWS. AwsKmsContentKeyProvider plugs AWS KMS into PostQuantum.FileEncryption's IContentKeyProvider seam: every file is encrypted under a fresh per-file content key that KMS GenerateDataKey wraps under your customer master key; decryption sends only the small wrapped blob back to KMS Decrypt.

dotnet add package PostQuantum.FileEncryption.Aws

Usage

using Amazon.KeyManagementService;
using PostQuantum.FileEncryption;
using PostQuantum.FileEncryption.Aws;

var kms = new AmazonKeyManagementServiceClient();          // credentials from the usual AWS chain
var provider = new AwsKmsContentKeyProvider(kms, "alias/my-app-key");

await new PqFileEncryptor().EncryptFileAsync("report.pdf", "report.pdf.pqfe", provider);
await new PqFileDecryptor().DecryptFileAsync("report.pdf.pqfe", "report.pdf", provider);

Optionally bind extra encryption context (audited by CloudTrail, required to unwrap):

var provider = new AwsKmsContentKeyProvider(kms, "alias/my-app-key",
    new Dictionary<string, string> { ["tenant"] = "contoso" });

Security behavior

  • The master key stays in KMS. Only the per-file content key crosses the boundary, and only wrapped. Rotation re-wraps the small content key — multi-gigabyte payloads are never re-encrypted.
  • Bound wraps. Every wrap carries a library-specific encryption context (plus your entries), and unwrap pins the configured key id — a blob wrapped under a different key or context fails closed with PqDecryptionException, indistinguishable from tampering.
  • Operational errors stay operational. Missing keys, access denial, throttling, and network failures surface as the AWS SDK's own exceptions, not as decryption failures.
  • IAM permissions needed: kms:GenerateDataKey to encrypt, kms:Decrypt to decrypt.

Versioning

Kept in lockstep with PostQuantum.FileEncryption. No change to the .pqfe v2 container format, which remains FROZEN for the 1.x line.

To God be the glory — 1 Corinthians 10:31.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.6.0 295 7/11/2026
1.5.0 307 7/2/2026
1.4.1 299 6/13/2026
1.4.0 328 6/13/2026

1.5.0 — hardening in lockstep with the family: unwrap rejects oversized wrapped blobs client-side (the KMS Decrypt limit is 6,144 bytes), so a hostile container yields the documented fail-closed PqDecryptionException instead of a raw SDK exception after a doomed network round-trip, and the engine now rejects any provider-returned content key that is not exactly 32 bytes. No change to the provider's API or the .pqfe v2 container format, which remains FROZEN for the 1.x line. See CHANGELOG.md.