parallax-aws 0.1.0__tar.gz

parallax_aws-0.1.0/.gitignore

@@ -0,0 +1,16 @@
+# Python build / test artifacts (uv, hatchling, pytest-cov, pyright).
+.venv/
+__pycache__/
+*.pyc
+*.egg-info/
+build/
+dist/
+coverage.xml
+.coverage
+.coverage.*
+.pytest_cache/
+.ruff_cache/
+# An editable install compiles parallax-postgres's Cython sources in place.
+packages/parallax-postgres/src/**/*.c
+*.so
+*.pyd

parallax_aws-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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.

parallax_aws-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Parallax
+Copyright 2026 David Lee
+
+Licensed under the Apache License, Version 2.0.
+Third-party dependencies are distributed separately under their own licences.

parallax_aws-0.1.0/PKG-INFO

@@ -0,0 +1,141 @@
+Metadata-Version: 2.5
+Name: parallax-aws
+Version: 0.1.0
+Summary: Parallax AWS credential providers: RDS IAM database authentication as a Credential Source (the sole botocore declarer).
+Project-URL: Documentation, https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/guide/README.md
+Project-URL: Repository, https://github.com/davidsunglee/parallax
+Project-URL: Changelog, https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/releases.md
+Author: Parallax
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Python: >=3.14
+Requires-Dist: botocore>=1.43.99
+Requires-Dist: parallax-core==0.1.0
+Provides-Extra: postgres
+Requires-Dist: parallax-postgres==0.1.0; extra == 'postgres'
+Requires-Dist: psycopg<3.4,>=3.3.6; extra == 'postgres'
+Description-Content-Type: text/markdown
+
+# parallax-aws
+
+Parallax's AWS credential providers: the sole declarer of `botocore`. See
+the [Python binding](https://github.com/davidsunglee/parallax/blob/main/languages/python/spec/python.md).
+The distribution includes Apache-2.0 `LICENSE` and `NOTICE`; see the
+[release notes](https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/releases.md)
+for publication status.
+
+## Authenticating an RDS Postgres login with IAM
+
+Install the `postgres` extra — `python -m pip install "parallax-aws[postgres]==0.1.0"` — and each
+endpoint is one call:
+
+```python
+from parallax.aws.postgres import rds_endpoint
+from parallax.postgres import PoolOptions, PostgresAdapter
+from parallax.snapshot import connect
+
+writer = rds_endpoint(
+    host="orders.cluster-abc.us-east-1.rds.amazonaws.com",
+    user="orders_service",
+    database="orders",
+    region="us-east-1",
+    pool=PoolOptions(min_size=2, max_size=20),
+)
+with connect(PostgresAdapter(writer=writer), model) as root:
+    ...
+```
+
+What comes back is the ordinary `PostgresEndpoint`, configured, and the
+application composes the adapter around it — nothing sits between the
+application and the adapter at runtime, and nothing was resolved or opened to
+build it. The factory is where three things are stated once, so no deployment
+has to remember them: the connection is encrypted, the token is signed for the
+host, port and user the endpoint's connections then use, and the endpoint to
+sign for is the one the application connects through — so each endpoint signs
+for its own host.
+
+`params` keeps the rest of libpq's grammar open — `application_name`,
+`options`, `connect_timeout`, and `sslrootcert` with an `sslmode` of
+`verify-ca` or `verify-full`, which is what AWS's own certificate bundle is for.
+It may strengthen the TLS requirement and may not weaken it, it may not ask for
+the GSS encryption libpq would carry the login over in TLS's place, and it may
+not restate `host`, `port`, `user`, `dbname` or `password`: a value the token
+was not signed for authenticates nothing. `host` names one endpoint for the same
+reason — libpq reads a comma-separated list of them, and a token signed for the
+list authenticates at none of its members. Every refusal is fixed text, because
+`params` is a place other secrets live.
+
+## The source on its own
+
+`RdsIamCredentials` is a `CredentialSource`, and the part of this package that
+imports no adapter. An application assembling its own connection string uses it
+directly, and a deployment on another engine installs this package without the
+`postgres` extra and gets no database driver with it.
+
+```python
+from parallax.aws import RdsIamCredentials
+from parallax.postgres import PostgresEndpoint
+
+host = "orders.cluster-abc.us-east-1.rds.amazonaws.com"
+writer = PostgresEndpoint(
+    f"postgresql://orders_service@{host}:5432/orders?sslmode=require",
+    credentials=RdsIamCredentials(host=host, port=5432, user="orders_service", region="us-east-1"),
+)
+```
+
+IAM database authentication is identical on RDS Postgres and Aurora Postgres.
+For a cluster, the endpoint above is the one the application connects through:
+a token proves nothing at an endpoint it was not signed for. Written this way,
+the TLS requirement the factory would have stated is the caller's to spell.
+
+## What has to agree outside Parallax
+
+- the database login exists and holds the IAM role —
+  `CREATE USER orders_service; GRANT rds_iam TO orders_service;`;
+- the AWS identity the process runs as is allowed `rds-db:connect` on
+  `arn:aws:rds-db:<region>:<account>:dbuser:<resource-id>/orders_service`;
+- the connection is encrypted. An IAM token is a password, so it travels over
+  TLS: `sslmode=require` at least, and `verify-full` with AWS's certificate
+  bundle where the deployment can supply one.
+
+## What resolving a token costs
+
+Signing is local — no AWS endpoint is reached to produce a token. What can block
+is botocore finding or refreshing the AWS credentials it signs with: the
+environment, a profile, an ECS task role, IMDSv2, IRSA, or SSO. The record
+bounds the network all of that reaches over, because the seam requires a source
+to, and it creates its RDS client on first use rather than at construction, so
+composing an adapter stays free of I/O.
+
+One thing it does not bound: a helper command a profile's `credential_process`
+names. botocore waits on that command with no timeout, and so does this record —
+the program is yours, and so is bounding its wait. Be exact about what an
+unbounded one costs, because it is not one connection: the RDS client is created
+once under a lock, so a helper that hangs holds every pool worker behind it and
+the application stops connecting rather than connects slowly. A helper that
+cannot promise to answer — one waiting on a person, or on a network of its own
+it has not bounded — belongs behind a session of your own, built on a chain that
+does not run it. An injected session is used exactly as given.
+
+There is no token cache and no refresh thread. A connection the server has
+already accepted is never disturbed by its token ageing out, and when a source
+is asked for a new one is the port's rule rather than this package's — see
+`core/spec/m-db-port.md`, "Configuration carries where, and a Credential Source
+carries how".
+
+```python
+# a session of your own — a profile, static keys, a test double; used as given
+RdsIamCredentials(host=endpoint, port=5432, user="app", region="us-east-1", session=session)
+```
+
+## When a token cannot be produced
+
+Every botocore or signing failure surfaces as
+`CredentialResolutionError: RDS IAM token could not be generated`, with the
+native error chained beneath it. The message is fixed text so that nothing a
+provider says can leak through it; what the adapter then reports — a startup
+that fails naming the refusal, or an acquisition failing with
+`reason="credentials_refused"` — is in
+[PostgreSQL connection lifecycle](https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/postgresql-lifecycle.md)
+under "Where the password lives".

parallax_aws-0.1.0/README.md

@@ -0,0 +1,122 @@
+# parallax-aws
+
+Parallax's AWS credential providers: the sole declarer of `botocore`. See
+the [Python binding](https://github.com/davidsunglee/parallax/blob/main/languages/python/spec/python.md).
+The distribution includes Apache-2.0 `LICENSE` and `NOTICE`; see the
+[release notes](https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/releases.md)
+for publication status.
+
+## Authenticating an RDS Postgres login with IAM
+
+Install the `postgres` extra — `python -m pip install "parallax-aws[postgres]==0.1.0"` — and each
+endpoint is one call:
+
+```python
+from parallax.aws.postgres import rds_endpoint
+from parallax.postgres import PoolOptions, PostgresAdapter
+from parallax.snapshot import connect
+
+writer = rds_endpoint(
+    host="orders.cluster-abc.us-east-1.rds.amazonaws.com",
+    user="orders_service",
+    database="orders",
+    region="us-east-1",
+    pool=PoolOptions(min_size=2, max_size=20),
+)
+with connect(PostgresAdapter(writer=writer), model) as root:
+    ...
+```
+
+What comes back is the ordinary `PostgresEndpoint`, configured, and the
+application composes the adapter around it — nothing sits between the
+application and the adapter at runtime, and nothing was resolved or opened to
+build it. The factory is where three things are stated once, so no deployment
+has to remember them: the connection is encrypted, the token is signed for the
+host, port and user the endpoint's connections then use, and the endpoint to
+sign for is the one the application connects through — so each endpoint signs
+for its own host.
+
+`params` keeps the rest of libpq's grammar open — `application_name`,
+`options`, `connect_timeout`, and `sslrootcert` with an `sslmode` of
+`verify-ca` or `verify-full`, which is what AWS's own certificate bundle is for.
+It may strengthen the TLS requirement and may not weaken it, it may not ask for
+the GSS encryption libpq would carry the login over in TLS's place, and it may
+not restate `host`, `port`, `user`, `dbname` or `password`: a value the token
+was not signed for authenticates nothing. `host` names one endpoint for the same
+reason — libpq reads a comma-separated list of them, and a token signed for the
+list authenticates at none of its members. Every refusal is fixed text, because
+`params` is a place other secrets live.
+
+## The source on its own
+
+`RdsIamCredentials` is a `CredentialSource`, and the part of this package that
+imports no adapter. An application assembling its own connection string uses it
+directly, and a deployment on another engine installs this package without the
+`postgres` extra and gets no database driver with it.
+
+```python
+from parallax.aws import RdsIamCredentials
+from parallax.postgres import PostgresEndpoint
+
+host = "orders.cluster-abc.us-east-1.rds.amazonaws.com"
+writer = PostgresEndpoint(
+    f"postgresql://orders_service@{host}:5432/orders?sslmode=require",
+    credentials=RdsIamCredentials(host=host, port=5432, user="orders_service", region="us-east-1"),
+)
+```
+
+IAM database authentication is identical on RDS Postgres and Aurora Postgres.
+For a cluster, the endpoint above is the one the application connects through:
+a token proves nothing at an endpoint it was not signed for. Written this way,
+the TLS requirement the factory would have stated is the caller's to spell.
+
+## What has to agree outside Parallax
+
+- the database login exists and holds the IAM role —
+  `CREATE USER orders_service; GRANT rds_iam TO orders_service;`;
+- the AWS identity the process runs as is allowed `rds-db:connect` on
+  `arn:aws:rds-db:<region>:<account>:dbuser:<resource-id>/orders_service`;
+- the connection is encrypted. An IAM token is a password, so it travels over
+  TLS: `sslmode=require` at least, and `verify-full` with AWS's certificate
+  bundle where the deployment can supply one.
+
+## What resolving a token costs
+
+Signing is local — no AWS endpoint is reached to produce a token. What can block
+is botocore finding or refreshing the AWS credentials it signs with: the
+environment, a profile, an ECS task role, IMDSv2, IRSA, or SSO. The record
+bounds the network all of that reaches over, because the seam requires a source
+to, and it creates its RDS client on first use rather than at construction, so
+composing an adapter stays free of I/O.
+
+One thing it does not bound: a helper command a profile's `credential_process`
+names. botocore waits on that command with no timeout, and so does this record —
+the program is yours, and so is bounding its wait. Be exact about what an
+unbounded one costs, because it is not one connection: the RDS client is created
+once under a lock, so a helper that hangs holds every pool worker behind it and
+the application stops connecting rather than connects slowly. A helper that
+cannot promise to answer — one waiting on a person, or on a network of its own
+it has not bounded — belongs behind a session of your own, built on a chain that
+does not run it. An injected session is used exactly as given.
+
+There is no token cache and no refresh thread. A connection the server has
+already accepted is never disturbed by its token ageing out, and when a source
+is asked for a new one is the port's rule rather than this package's — see
+`core/spec/m-db-port.md`, "Configuration carries where, and a Credential Source
+carries how".
+
+```python
+# a session of your own — a profile, static keys, a test double; used as given
+RdsIamCredentials(host=endpoint, port=5432, user="app", region="us-east-1", session=session)
+```
+
+## When a token cannot be produced
+
+Every botocore or signing failure surfaces as
+`CredentialResolutionError: RDS IAM token could not be generated`, with the
+native error chained beneath it. The message is fixed text so that nothing a
+provider says can leak through it; what the adapter then reports — a startup
+that fails naming the refusal, or an acquisition failing with
+`reason="credentials_refused"` — is in
+[PostgreSQL connection lifecycle](https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/postgresql-lifecycle.md)
+under "Where the password lives".

parallax_aws-0.1.0/pyproject.toml

@@ -0,0 +1,43 @@
+[project]
+name = "parallax-aws"
+version = "0.1.0"
+description = "Parallax AWS credential providers: RDS IAM database authentication as a Credential Source (the sole botocore declarer)."
+readme = "README.md"
+requires-python = ">=3.14"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Parallax" }]
+dependencies = [
+    "parallax-core==0.1.0",
+    # Declared for the AWS credential chain rather than for the token: the
+    # presign is local, but finding the credentials to sign with — environment,
+    # profiles, IMDSv2, ECS task roles, IRSA, SSO, and the automatic refresh of
+    # every temporary credential those produce — is botocore's. boto3 adds
+    # nothing: `generate_db_auth_token` is a botocore RDS-client operation, so an
+    # application already using boto3 shares this one install.
+    "botocore>=1.43.99",
+]
+
+# The engine-specific slice `parallax.aws.postgres` composes a
+# `PostgresAdapter`, and this extra is what keeps the rest of the distribution
+# free of one: a deployment on another engine installs the credential provider
+# and no database driver arrives with it. The slice also imports psycopg
+# directly, so the extra declares the driver beside the adapter that brings its
+# binary build.
+[project.optional-dependencies]
+postgres = ["parallax-postgres==0.1.0", "psycopg>=3.3.6,<3.4"]
+
+[project.urls]
+Documentation = "https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/guide/README.md"
+Repository = "https://github.com/davidsunglee/parallax"
+Changelog = "https://github.com/davidsunglee/parallax/blob/main/languages/python/docs/releases.md"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/parallax"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/parallax", "README.md", "LICENSE", "NOTICE"]

parallax_aws-0.1.0/src/parallax/aws/__init__.py

@@ -0,0 +1,5 @@
+from __future__ import annotations
+
+from parallax.aws._rds import RdsIamCredentials
+
+__all__ = ["RdsIamCredentials"]

parallax_aws-0.1.0/src/parallax/aws/_rds.py

@@ -0,0 +1,126 @@
+from __future__ import annotations
+
+import threading
+from dataclasses import dataclass, field
+from typing import TYPE_CHECKING, Protocol, cast
+
+import botocore.session
+from botocore.config import Config
+
+from parallax.core.db_port import CredentialResolutionError, Password
+
+if TYPE_CHECKING:
+    from botocore.client import BaseClient
+    from botocore.session import Session
+
+__all__ = ["RdsIamCredentials"]
+
+_TOKEN_REFUSAL = "RDS IAM token could not be generated"
+
+# What one credential-chain call may cost before the source gives up. The chain
+# reaches the instance metadata service, an ECS task-role endpoint, STS or SSO,
+# and botocore's own default is sixty seconds a side with five attempts — a wait
+# the seam forbids, because a source runs where nothing above it can interrupt
+# it. The budget is attempts in total, the first one included.
+_CHAIN_CONNECT_TIMEOUT = 2.0
+_CHAIN_READ_TIMEOUT = 2.0
+_CHAIN_ATTEMPTS = 2
+
+
+class _RdsTokenClient(Protocol):
+    """The one RDS-client operation this module calls.
+
+    botocore attaches ``generate_db_auth_token`` to an RDS client when the
+    client is created, so it is on no class a type checker can read it off.
+    """
+
+    def generate_db_auth_token(
+        self, DBHostname: str, Port: int, DBUsername: str, Region: str
+    ) -> str: ...
+
+
+def _bounded_session() -> Session:
+    """A botocore session whose credential chain bounds its own network calls.
+
+    The default client configuration reaches every client the session creates,
+    the STS and SSO clients the chain builds internally included. The instance
+    metadata service is reached through a fetcher rather than a client and takes
+    its bounds from the session's own configuration, which is why that pair is
+    set beside the client default rather than covered by it.
+    """
+    session = botocore.session.get_session()
+    session.set_default_client_config(
+        Config(
+            connect_timeout=_CHAIN_CONNECT_TIMEOUT,
+            read_timeout=_CHAIN_READ_TIMEOUT,
+            retries={"total_max_attempts": _CHAIN_ATTEMPTS, "mode": "standard"},
+        )
+    )
+    session.set_config_variable("metadata_service_timeout", _CHAIN_CONNECT_TIMEOUT)
+    session.set_config_variable("metadata_service_num_attempts", _CHAIN_ATTEMPTS)
+    return session
+
+
+class _TokenSigner:
+    """The RDS client a source signs on, created once and then kept.
+
+    Creating a client runs the AWS credential chain, which on EC2 or ECS is a
+    metadata-service call, so it cannot happen while configuration is being
+    built. botocore clients are thread-safe and botocore sessions are not, so
+    the one creation is serialized here and every pool worker afterwards signs
+    on the same client — which is also why a chain that blocks blocks all of
+    them.
+    """
+
+    __slots__ = ("_client", "_lock", "_region", "_session")
+
+    def __init__(self, session: Session | None, region: str) -> None:
+        self._session = session
+        self._region = region
+        self._lock = threading.Lock()
+        self._client: _RdsTokenClient | None = None
+
+    def client(self) -> _RdsTokenClient:
+        with self._lock:
+            if self._client is None:
+                session = self._session if self._session is not None else _bounded_session()
+                created: BaseClient = session.create_client("rds", region_name=self._region)
+                self._client = cast("_RdsTokenClient", created)
+            return self._client
+
+
+@dataclass(frozen=True, slots=True)
+class RdsIamCredentials:
+    """Authenticates an RDS or Aurora Postgres login with an IAM token.
+
+    ``host``, ``port`` and ``user`` are what the token is signed for and must be
+    what the connection then uses: a token signed for one endpoint proves
+    nothing at another, so a cluster reached through its own endpoint is signed
+    for that endpoint. ``region`` is the token's credential scope.
+
+    ``session`` is a botocore session to resolve AWS credentials through. Left
+    absent, the record builds one whose credential chain bounds its own network
+    calls; an injected one is used exactly as given and never reconfigured, so
+    its owner keeps whatever bounds it was built with — and chooses the chain,
+    which is what a deployment whose profile runs an unbounded
+    ``credential_process`` helper does instead.
+    """
+
+    host: str
+    port: int
+    user: str
+    region: str
+    session: Session | None = field(default=None, repr=False)
+    _signer: _TokenSigner = field(init=False, repr=False, compare=False)
+
+    def __post_init__(self) -> None:
+        object.__setattr__(self, "_signer", _TokenSigner(self.session, self.region))
+
+    def resolve(self) -> Password:
+        try:
+            token = self._signer.client().generate_db_auth_token(
+                DBHostname=self.host, Port=self.port, DBUsername=self.user, Region=self.region
+            )
+        except Exception as exc:
+            raise CredentialResolutionError(_TOKEN_REFUSAL) from exc
+        return Password(token)

parallax_aws-0.1.0/src/parallax/aws/postgres.py

@@ -0,0 +1,95 @@
+from __future__ import annotations
+
+from typing import TYPE_CHECKING
+
+import psycopg.conninfo
+
+from parallax.aws._rds import RdsIamCredentials
+from parallax.postgres import PoolOptions, PostgresEndpoint
+
+if TYPE_CHECKING:
+    from collections.abc import Mapping
+
+    from botocore.session import Session
+
+    from parallax.postgres import OnDemandOptions
+
+__all__ = ["rds_endpoint"]
+
+# What the token is signed for, plus the secret it stands in for. A connection
+# that used any other value for one of these would present a token signed for
+# something else, so the factory states them and `params` may not restate them.
+_RESERVED = frozenset({"host", "port", "user", "dbname", "password"})
+_WEAKER_THAN_REQUIRE = frozenset({"disable", "allow", "prefer"})
+
+_HOST_REFUSAL = (
+    "host must name one endpoint; a token is signed for the host it names, not for a list."
+)
+_RESERVED_REFUSAL = (
+    "params must not name host, port, user, dbname or password; the factory states those."
+)
+_SSLMODE_REFUSAL = (
+    "params must not weaken sslmode below require; an IAM token travels only over TLS."
+)
+# libpq offers GSS encryption in TLS's place rather than beneath it, and takes it
+# whenever it is available unless it is switched off, whatever `sslmode` says.
+_GSSENCMODE_REFUSAL = "params must not enable gssencmode; an IAM token travels only over TLS."
+
+
+def rds_endpoint(
+    *,
+    host: str,
+    user: str,
+    database: str,
+    region: str,
+    port: int = 5432,
+    params: Mapping[str, str] | None = None,
+    session: Session | None = None,
+    pool: PoolOptions | OnDemandOptions | None = None,
+) -> PostgresEndpoint:
+    """Configure a Postgres endpoint whose login authenticates with an RDS IAM token.
+
+    ``host`` is the endpoint the application connects through — a cluster's
+    writer or reader endpoint for Aurora — and, with ``port`` and ``user``, what
+    each token is signed for, so every endpoint signs for its own host. It names
+    one endpoint: libpq reads a comma-separated ``host`` as a list to try in
+    turn, and a token signed for that whole list authenticates at none of them.
+    ``region`` is the token's credential scope and ``session`` an optional
+    botocore session to resolve AWS credentials through.
+
+    ``params`` carries the rest of libpq's grammar — ``application_name``,
+    ``options``, ``connect_timeout``, ``sslrootcert`` — so this factory never
+    becomes a second spelling of the connection string. It may raise
+    ``sslmode`` to ``verify-ca`` or ``verify-full``; it may not weaken it, it
+    may not ask for the GSS encryption libpq would carry the token over
+    instead, and it may not name what the token is bound to. Every refusal is
+    fixed text, because ``params`` is a place other secrets live. ``pool`` is
+    the endpoint's retention, :class:`~parallax.postgres.PoolOptions`' defaults
+    where omitted.
+
+    Nothing here resolves a token, reaches AWS, or opens anything: the result is
+    configuration, exactly as a directly constructed endpoint is.
+    """
+    if "," in host:
+        raise ValueError(_HOST_REFUSAL)
+    requested = dict(params or {})
+    if _RESERVED & requested.keys():
+        raise ValueError(_RESERVED_REFUSAL)
+    if requested.get("sslmode", "require") in _WEAKER_THAN_REQUIRE:
+        raise ValueError(_SSLMODE_REFUSAL)
+    if requested.get("gssencmode", "disable") != "disable":
+        raise ValueError(_GSSENCMODE_REFUSAL)
+    conninfo = psycopg.conninfo.make_conninfo(
+        host=host,
+        port=port,
+        user=user,
+        dbname=database,
+        **{"sslmode": "require", "gssencmode": "disable", **requested},
+    )
+    return PostgresEndpoint(
+        conninfo,
+        credentials=RdsIamCredentials(
+            host=host, port=port, user=user, region=region, session=session
+        ),
+        pool=PoolOptions() if pool is None else pool,
+    )