aembit-edge-sdk 1.35.0__tar.gz

aembit_edge_sdk-1.35.0/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+.pkg-venv/
+__pycache__/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+.coverage
+coverage.xml
+mutants/
+.mutmut-cache/
+.mutmut-cache

aembit_edge_sdk-1.35.0/AGENTS.md

@@ -0,0 +1,147 @@
+# Python SDK Agent Guide
+
+Language-specific guidance for contributors and coding agents working in `py/`.
+
+This file augments the root `AGENTS.md`. Follow both files. If guidance conflicts, the root `AGENTS.md` takes precedence unless this file is stricter for Python-specific behavior.
+
+## Purpose
+
+The Python SDK should follow the conceptual design established by the TypeScript SDK while feeling idiomatic for modern Python.
+
+Changes in `py/` should prioritize:
+
+- clear and ergonomic developer APIs
+- predictable authentication and token lifecycle behavior
+- portability of concepts from the TypeScript reference implementation
+- compatibility with Python `>=3.10`
+
+## Scope
+
+This guide applies to files under `py/`, including:
+
+- SDK source code
+- Python tests
+- Python examples
+- Python documentation
+- Python packaging and tooling configuration
+
+## Directory Conventions
+
+Keep Python assets inside `py/` and avoid cross-language coupling.
+
+Recommended structure for Python work:
+
+- `py/src/aembit_edge/` for SDK implementation
+- `py/tests/` for tests
+- `py/examples/` for runnable examples
+- `py/README.md` for Python SDK usage docs
+- `py/architecture.md` for Python SDK architecture notes
+
+If the structure changes, keep naming and placement consistent within `py/`.
+
+## API Design Rules
+
+Python should expose a high-level client-first interface.
+
+- Primary entry points should hide raw protocol details.
+- Public methods should map to developer tasks such as `authenticate()` and `get_credential()`.
+- Public APIs should use Python naming conventions such as `snake_case`.
+- Public configuration should use `Trust Provider` terminology.
+- Use official Aembit Edge API terminology from `https://docs.aembit.io/api-guide/edge/`; avoid alternate API names in docs/comments.
+- Keep advanced options optional and well-scoped.
+- Preserve credential response data without forcing a rigid credential schema.
+
+Planned public entry points:
+
+- `EdgeClient`
+- `AsyncEdgeClient`
+
+## Python Standards
+
+- Support Python `>=3.10`.
+- Use full type hints in public and internal code.
+- Prefer `Protocol`, `TypedDict`, `dataclass`, and small focused classes where they improve clarity.
+- Keep public types intentionally minimal and stable.
+- Avoid unnecessary metaprogramming.
+- Prefer standard-library features unless a dependency materially improves reliability or maintainability.
+- Keep docstrings concise and focused on behavior-affecting details.
+
+## Sync And Async Design
+
+The SDK is expected to support both synchronous and asynchronous usage.
+
+- Keep shared logic in reusable core modules where possible.
+- Keep sync and async transport/client behavior aligned.
+- Do not force async-only or sync-only design assumptions into shared types or architecture.
+- When one path lands before the other, keep the code structure ready for parity.
+
+## Error Handling
+
+Errors should be actionable and consistent.
+
+- Normalize transport and API errors into SDK-defined exception types.
+- Include structured metadata when available, such as HTTP status and API error code.
+- Preserve root causes with exception chaining.
+- Avoid leaking raw low-level error shapes through public interfaces.
+
+## Auth And Token Lifecycle
+
+Authentication behavior should be predictable and safe under concurrency.
+
+- Cache bearer tokens with clear expiration handling.
+- Refresh tokens before hard expiry using a small safety window.
+- Prevent duplicate concurrent refreshes for the same client instance.
+- Handle auth failures explicitly and clear invalid cached state.
+
+## Testing Requirements
+
+Python SDK changes should include tests when behavior changes.
+
+Testing and quality tools:
+
+- use `pytest`
+- use `ruff` for linting and formatting
+- use `pyright` as the primary static type checker
+- use `uv` for local environment and dependency management
+
+Focus tests on:
+
+- request construction and serialization
+- authentication flow behavior
+- token caching and refresh logic
+- error mapping and propagation
+- credential retrieval behavior with varied payload shapes
+
+Prefer deterministic tests with mocked network behavior and controlled time for token-expiry logic.
+
+## Documentation And Examples
+
+When public Python SDK behavior changes:
+
+- update `py/README.md`
+- update or add `py/examples/` usage snippets
+- keep examples runnable and minimal
+- use placeholder values only
+
+Examples are part of product quality, not optional extras.
+
+## Dependency Policy
+
+- Avoid adding dependencies unless they materially improve reliability, maintainability, or developer experience.
+- Prefer small, well-maintained libraries over broad frameworks.
+- Do not add dependencies for trivial utilities that can be implemented clearly in SDK code.
+- When adding dependencies, consider Python `>=3.10` compatibility and static typing support.
+
+## Review Checklist For Agents
+
+Before handing work back to the user:
+
+- run `uv run ruff check .` for Python file changes and confirm it passes
+- run `uv run ruff format --check .`
+- run `uv run pyright`
+- run `uv run pytest`
+- run `uv build --wheel --sdist` when Python packaging or build configuration changes
+- ensure API and README changes are aligned
+- verify examples still reflect recommended usage
+- verify no secrets or production identifiers are present
+- present diffs and do not commit unless explicitly requested

aembit_edge_sdk-1.35.0/LICENSE

@@ -0,0 +1,190 @@
+Copyright 2024-present Aembit, Inc.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

aembit_edge_sdk-1.35.0/PKG-INFO

@@ -0,0 +1,160 @@
+Metadata-Version: 2.5
+Name: aembit-edge-sdk
+Version: 1.35.0
+Summary: Python SDK for the Aembit Edge API
+Author: Aembit
+License: Apache-2.0
+License-File: LICENSE
+Keywords: aembit,credentials,edge,sdk,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: botocore>=1.42.83
+Provides-Extra: dev
+Requires-Dist: mutmut>=3.7.0; extra == 'dev'
+Requires-Dist: pip-audit>=2.8.0; extra == 'dev'
+Requires-Dist: pyright>=1.1.408; extra == 'dev'
+Requires-Dist: pytest-cov>=6.0.0; extra == 'dev'
+Requires-Dist: pytest>=8.4.2; extra == 'dev'
+Requires-Dist: ruff>=0.14.0; extra == 'dev'
+Requires-Dist: tomli-w>=1.0.0; extra == 'dev'
+Requires-Dist: tomli>=2.0.1; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Aembit Edge Python SDK
+
+[![PyPI version](https://img.shields.io/pypi/v/aembit-edge-sdk.svg)](https://pypi.org/project/aembit-edge-sdk/)
+[![Python](https://img.shields.io/pypi/pyversions/aembit-edge-sdk.svg)](https://pypi.org/project/aembit-edge-sdk/)
+[![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Aembit/edge-sdks/blob/main/LICENSE)
+
+Official Python SDK for interacting with the [Aembit Edge API](https://docs.aembit.io/api-guide/edge/).
+
+The Aembit Edge SDK allows Python backend services, serverless functions, web applications, AI agents, and MCP servers to authenticate and retrieve credentials dynamically without managing static secrets.
+
+## Features
+
+- 🔐 **Zero Hardcoded Secrets**: Authenticate via workload identity (AWS STS Role, GitHub Actions OIDC, GitLab CI/CD OIDC, Terraform Cloud OIDC).
+- 🔄 **Automatic Token Lifecycle**: Built-in in-memory bearer token caching and proactive background refresh.
+- 🪵 **Standard Library Logging**: Configured via the standard `logging` library under the `aembit_edge` namespace.
+- 📦 **Modern Python**: Strictly typed, supporting Python `>=3.10`.
+
+## Installation
+
+```bash
+pip install aembit-edge-sdk
+```
+
+Or using `uv`:
+
+```bash
+uv add aembit-edge-sdk
+```
+
+## Quickstart
+
+### Using AWS IAM Role (STS)
+
+```python
+from aembit_edge import CredentialServerRef, EdgeClient, EdgeClientConfig, GetCredentialInput
+from aembit_edge.trust_providers import AwsRoleTrustProvider
+
+# 1. Initialize the AWS Role Trust Provider
+aws_provider = AwsRoleTrustProvider(region="us-east-1")
+
+# 2. Configure the Edge Client
+config = EdgeClientConfig(
+    base_url="https://your-tenant.aembit.io",
+    client_id="your-client-id",
+    trust_provider=aws_provider,
+)
+client = EdgeClient(config)
+
+# 3. Retrieve target server credentials
+server = CredentialServerRef(host="database.internal", port=5432)
+request = GetCredentialInput(server=server, credential_type="api_key")
+
+result = client.get_credential(request)
+print("Retrieved Credential Data:", result.data)
+```
+
+### Using OIDC Trust Providers (GitHub, GitLab, Terraform)
+
+```python
+from aembit_edge import CredentialServerRef, EdgeClient, EdgeClientConfig, GetCredentialInput
+from aembit_edge.trust_providers import GitHubTrustProvider
+
+# 1. Initialize the trust provider with the environment's identity token
+github_provider = GitHubTrustProvider(identity_token="YOUR_GITHUB_OIDC_TOKEN")
+
+# 2. Configure the Edge Client
+config = EdgeClientConfig(
+    base_url="https://your-tenant.aembit.io",
+    client_id="your-client-id",
+    trust_provider=github_provider,
+)
+client = EdgeClient(config)
+
+# 3. Request credentials for a target server
+server = CredentialServerRef(host="api.internal", port=443)
+request = GetCredentialInput(server=server, credential_type="api_key")
+
+result = client.get_credential(request)
+print("Retrieved Credential Data:", result.data)
+```
+
+Other OIDC providers (`GitLabTrustProvider`, `TerraformTrustProvider`) follow the same pattern:
+
+```python
+from aembit_edge.trust_providers import GitLabTrustProvider, TerraformTrustProvider
+
+# For GitLab CI/CD:
+gitlab_provider = GitLabTrustProvider(identity_token="YOUR_GITLAB_OIDC_TOKEN")
+
+# For Terraform Cloud:
+terraform_provider = TerraformTrustProvider(identity_token="YOUR_TERRAFORM_OIDC_TOKEN")
+```
+
+## Supported Trust Providers
+
+| Trust Provider | Class Name | Import Path |
+| :--- | :--- | :--- |
+| **AWS IAM Role (STS)** | `AwsRoleTrustProvider(region=...)` | `aembit_edge.trust_providers` |
+| **GitHub Actions OIDC** | `GitHubTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+| **GitLab CI/CD OIDC** | `GitLabTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+| **Terraform Cloud OIDC** | `TerraformTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+
+## Logging & Observability
+
+By default, the SDK remains silent with a `logging.NullHandler` attached to the `aembit_edge` namespace. To enable operational debug logging:
+
+```python
+import logging
+
+logging.basicConfig(level=logging.INFO)
+logging.getLogger("aembit_edge").setLevel(logging.DEBUG)
+```
+
+## Examples
+
+Runnable integration examples are available in the GitHub repository:
+
+- [Logging Integration (Loguru & Structlog)](https://github.com/Aembit/edge-sdks/tree/main/py/examples/logging_integration)
+
+## Documentation & Resources
+
+- [Official Aembit Edge API Guide](https://docs.aembit.io/api-guide/edge/)
+- [Aembit Documentation](https://docs.aembit.io/)
+- [GitHub Issue Tracker](https://github.com/Aembit/edge-sdks/issues)
+- [Contributing Guide](https://github.com/Aembit/edge-sdks/blob/main/CONTRIBUTING.md)
+
+## License
+
+This project is licensed under the [Apache-2.0 License](https://github.com/Aembit/edge-sdks/blob/main/LICENSE).

aembit_edge_sdk-1.35.0/README.md

@@ -0,0 +1,129 @@
+# Aembit Edge Python SDK
+
+[![PyPI version](https://img.shields.io/pypi/v/aembit-edge-sdk.svg)](https://pypi.org/project/aembit-edge-sdk/)
+[![Python](https://img.shields.io/pypi/pyversions/aembit-edge-sdk.svg)](https://pypi.org/project/aembit-edge-sdk/)
+[![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/Aembit/edge-sdks/blob/main/LICENSE)
+
+Official Python SDK for interacting with the [Aembit Edge API](https://docs.aembit.io/api-guide/edge/).
+
+The Aembit Edge SDK allows Python backend services, serverless functions, web applications, AI agents, and MCP servers to authenticate and retrieve credentials dynamically without managing static secrets.
+
+## Features
+
+- 🔐 **Zero Hardcoded Secrets**: Authenticate via workload identity (AWS STS Role, GitHub Actions OIDC, GitLab CI/CD OIDC, Terraform Cloud OIDC).
+- 🔄 **Automatic Token Lifecycle**: Built-in in-memory bearer token caching and proactive background refresh.
+- 🪵 **Standard Library Logging**: Configured via the standard `logging` library under the `aembit_edge` namespace.
+- 📦 **Modern Python**: Strictly typed, supporting Python `>=3.10`.
+
+## Installation
+
+```bash
+pip install aembit-edge-sdk
+```
+
+Or using `uv`:
+
+```bash
+uv add aembit-edge-sdk
+```
+
+## Quickstart
+
+### Using AWS IAM Role (STS)
+
+```python
+from aembit_edge import CredentialServerRef, EdgeClient, EdgeClientConfig, GetCredentialInput
+from aembit_edge.trust_providers import AwsRoleTrustProvider
+
+# 1. Initialize the AWS Role Trust Provider
+aws_provider = AwsRoleTrustProvider(region="us-east-1")
+
+# 2. Configure the Edge Client
+config = EdgeClientConfig(
+    base_url="https://your-tenant.aembit.io",
+    client_id="your-client-id",
+    trust_provider=aws_provider,
+)
+client = EdgeClient(config)
+
+# 3. Retrieve target server credentials
+server = CredentialServerRef(host="database.internal", port=5432)
+request = GetCredentialInput(server=server, credential_type="api_key")
+
+result = client.get_credential(request)
+print("Retrieved Credential Data:", result.data)
+```
+
+### Using OIDC Trust Providers (GitHub, GitLab, Terraform)
+
+```python
+from aembit_edge import CredentialServerRef, EdgeClient, EdgeClientConfig, GetCredentialInput
+from aembit_edge.trust_providers import GitHubTrustProvider
+
+# 1. Initialize the trust provider with the environment's identity token
+github_provider = GitHubTrustProvider(identity_token="YOUR_GITHUB_OIDC_TOKEN")
+
+# 2. Configure the Edge Client
+config = EdgeClientConfig(
+    base_url="https://your-tenant.aembit.io",
+    client_id="your-client-id",
+    trust_provider=github_provider,
+)
+client = EdgeClient(config)
+
+# 3. Request credentials for a target server
+server = CredentialServerRef(host="api.internal", port=443)
+request = GetCredentialInput(server=server, credential_type="api_key")
+
+result = client.get_credential(request)
+print("Retrieved Credential Data:", result.data)
+```
+
+Other OIDC providers (`GitLabTrustProvider`, `TerraformTrustProvider`) follow the same pattern:
+
+```python
+from aembit_edge.trust_providers import GitLabTrustProvider, TerraformTrustProvider
+
+# For GitLab CI/CD:
+gitlab_provider = GitLabTrustProvider(identity_token="YOUR_GITLAB_OIDC_TOKEN")
+
+# For Terraform Cloud:
+terraform_provider = TerraformTrustProvider(identity_token="YOUR_TERRAFORM_OIDC_TOKEN")
+```
+
+## Supported Trust Providers
+
+| Trust Provider | Class Name | Import Path |
+| :--- | :--- | :--- |
+| **AWS IAM Role (STS)** | `AwsRoleTrustProvider(region=...)` | `aembit_edge.trust_providers` |
+| **GitHub Actions OIDC** | `GitHubTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+| **GitLab CI/CD OIDC** | `GitLabTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+| **Terraform Cloud OIDC** | `TerraformTrustProvider(identity_token=...)` | `aembit_edge.trust_providers` |
+
+## Logging & Observability
+
+By default, the SDK remains silent with a `logging.NullHandler` attached to the `aembit_edge` namespace. To enable operational debug logging:
+
+```python
+import logging
+
+logging.basicConfig(level=logging.INFO)
+logging.getLogger("aembit_edge").setLevel(logging.DEBUG)
+```
+
+## Examples
+
+Runnable integration examples are available in the GitHub repository:
+
+- [Logging Integration (Loguru & Structlog)](https://github.com/Aembit/edge-sdks/tree/main/py/examples/logging_integration)
+
+## Documentation & Resources
+
+- [Official Aembit Edge API Guide](https://docs.aembit.io/api-guide/edge/)
+- [Aembit Documentation](https://docs.aembit.io/)
+- [GitHub Issue Tracker](https://github.com/Aembit/edge-sdks/issues)
+- [Contributing Guide](https://github.com/Aembit/edge-sdks/blob/main/CONTRIBUTING.md)
+
+## License
+
+This project is licensed under the [Apache-2.0 License](https://github.com/Aembit/edge-sdks/blob/main/LICENSE).