Registry / aws / aws-cryptography-internal-standard-library

aws-cryptography-internal-standard-library

JSON →
library1.11.2pypypiunverified

The `aws-cryptography-internal-standard-library` is an internal Python library, a foundational component primarily utilized by the AWS Cryptographic Material Providers Library (MPL) and subsequently by the AWS Encryption SDK. It provides cryptographic primitives and standard library interfaces for other AWS cryptography projects. Users are strongly advised against taking a standalone dependency on this library, as its internal nature means there are no guarantees about API stability or functionality between minor versions. The current version is 1.11.2, and its release cadence aligns with its dependent AWS cryptography libraries.

pip install aws-cryptography-internal-standard-library
INSTALL
IMPORT
SIG · AWS-CRYPTOGRAPHY-I
A
aws-cryptography-internal-standard-library
awspythonv1.11.2
Install
3.7s avg
Import
Disk
84MB
Pass rate
6/ 10
Env Coverage6 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v1.11.2 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
glibc
py 3.10
4/8 runs
4/8 runs
py 3.11
✓ —
✓ 4s
py 3.12
✓ —
✓ 3.59s
py 3.13
✓ —
✓ 3.46s
py 3.9
4/8 runs
4/8 runs
84MB installed
● package 84MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

aws_cryptography_internal_standard_library
# No public API for direct import. This library is an internal dependency.
This library is not intended for direct use or public import. Its modules are typically consumed by other AWS cryptography libraries like the AWS Cryptographic Material Providers Library.

This library is designed for internal use by other AWS cryptography projects, not for direct public consumption. Attempting to use it directly may lead to unpredictable behavior and breaking changes. The recommended way to leverage AWS cryptographic best practices is through higher-level libraries such as the AWS Encryption SDK, which internally manages and utilizes this standard library. The commented-out example demonstrates how you would typically encrypt and decrypt data using the AWS Encryption SDK, which is the intended interface for end-users.

print('The aws-cryptography-internal-standard-library is an internal dependency.') print('Direct interaction is not recommended as its API is unstable and not for public use.') print('Instead, use public-facing libraries like the AWS Encryption SDK (aws-encryption-sdk).') # Example of how you would typically interact with encryption functionality # through the AWS Encryption SDK, which internally uses libraries like this one. # This code snippet is for illustration and requires additional setup (AWS credentials, KMS key). # import aws_encryption_sdk # from aws_encryption_sdk.keyrings.aws_kms import AwsKmsKeyring # key_arn = os.environ.get('KMS_KEY_ARN', 'arn:aws:kms:us-west-2:111122223333:key/example-key-id') # plaintext = b'my secret data' # try: # # Instantiate the AWS Encryption SDK client # client = aws_encryption_sdk.EncryptionSDKClient() # # Create a KMS Keyring (this uses the AWS Cryptographic Material Providers Library internally) # keyring = AwsKmsKeyring(key_ids=[key_arn]) # # Encrypt the data # ciphertext, header = client.encrypt(source=plaintext, keyring=keyring) # print(f'Ciphertext: {ciphertext.hex()}') # # Decrypt the data # decrypted_plaintext, _ = client.decrypt(source=ciphertext, keyring=keyring) # print(f'Decrypted plaintext: {decrypted_plaintext.decode()}') # except Exception as e: # print(f'Error demonstrating AWS Encryption SDK: {e}') # print('Please ensure AWS credentials and a valid KMS_KEY_ARN are configured.')
Debug
Known issues
breakingDo NOT take a standalone dependency on this library. It is an internal component, and AWS makes no guarantees that its functionality or API will remain stable or consistent between minor versions. Direct usage can lead to unexpected breakages in your application.
fix
Migrate to public-facing AWS cryptography libraries like the `aws-encryption-sdk` or `aws-cryptographic-material-providers`. These libraries offer stable APIs and are designed for customer use.
affects: All versions
gotchaLack of direct documentation and examples. Since this library is internal, there is no dedicated public documentation or usage examples for direct interaction. Relying on reverse-engineering or undocumented internal APIs is highly discouraged.
fix
Refer to the documentation and examples for the AWS Encryption SDK or the AWS Cryptographic Material Providers Library. These libraries provide the officially supported and documented interfaces for AWS cryptography.
affects: All versions
gotchaPython compatibility is dictated by its consumers. While PyPI lists `<4.0.0,>=3.11.0`, the effective minimum Python version might be higher or lower depending on the specific versions of the consuming AWS cryptography libraries (e.g., `aws-encryption-sdk`).
fix
Always check the Python compatibility requirements of the top-level AWS cryptography library you are using (e.g., `aws-encryption-sdk`) as that will be the authoritative source for your environment.
affects: All versions
Upgrade
Version history
1.11.2latest on PyPI · released Feb 23, 2026
Audit
Dependencies
cryptographyrequiredRequired by higher-level AWS cryptography libraries that utilize this internal library for cryptographic operations.
boto3optionalRequired by higher-level AWS cryptography libraries for interaction with AWS services like KMS.
Agent activity
46 hits · last 30 days
node
38
OpenAI (training)
2
Resources
aws-cryptography-internal-standard-library — pip install aws-cryptography-internal-standard-library · libregistry