Python PostgreSQL REST API framework for AWS Lambda functions
[!NOTE] Project status:
Alpha
A REST API web framework for persisting records in a PostgreSQL database.
Supported features
- Automatic creation of
uidfields - Automatic setting of
created_atandlast_updated_attimestamps - Automatic setting of
creator_uidandlast_updater_uid - RDS with IAM credentials
Examples
Sequence diagrams
High-level infrastructure
This sequence diagram shows how a lambda function running this library is intended to be deployed.
sequenceDiagram
# Set up actors and participants
actor User
participant APIGW as API Gateway
participant Cognito as Cognito
box Purple This library
participant Lambda as Lambda Function
end
participant RDS as RDS Database
# Set up Sequences
User ->> APIGW: HTTP /resource
activate APIGW
APIGW -->> Cognito: Authenticate
activate Cognito
Cognito ->> APIGW: Authenticated
deactivate Cognito
APIGW ->> Lambda: Send proxy integration request
activate Lambda
Lambda ->> RDS: Fetch/mutate
activate RDS
RDS -->> Lambda: Return records
deactivate RDS
Lambda -->> APIGW: Return response
deactivate Lambda
APIGW -->> User: Return response
deactivate APIGW
Low-level architecture
This sequence diagram shows the layers within the library that handle request and response processing.
sequenceDiagram
Participant APIGW as API Gateway
box Purple This library as a deployed Lambda Function
Participant CONT as Controller
Participant REQM as Request Mapper
Participant RESOURCEM as Resource Mapper
Participant DBM as Database Mapper
Participant RESPONSEM as Response Mapper
end
Participant RDS
APIGW ->> CONT: Send `event` dict
activate CONT
CONT ->> REQM: Map request
activate REQM
REQM ->> CONT: Mapped request
deactivate REQM
CONT ->> RESOURCEM: Map resource
activate RESOURCEM
RESOURCEM -->> CONT: Mapped resource
deactivate RESOURCEM
CONT ->> DBM: Request resource operation
activate DBM
DBM ->> RDS: Perform resource operation
activate RDS
RDS -->> DBM: Return resources
deactivate RDS
DBM -->> CONT: Return resource
deactivate DBM
CONT ->> RESPONSEM: Map response
activate RESPONSEM
RESPONSEM -->> CONT: Mapped response
deactivate RESPONSEM
CONT -->> APIGW: Return response
deactivate CONT
Metadata
Release files for pygrestqlambda 0.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pygrestqlambda-0.0.9.tar.gz | 13.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pygrestqlambda-0.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.1 kB
Release files / pygrestqlambda-0.0.9.tar.gz
| Download URL | pygrestqlambda-0.0.9.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c8cccc5aee4c880b2b427ce3f437eaa7ff2e5a6e42294fbd08fd871b89333e6
|
|
BLAKE2b-256 checksum How to use checksums |
a8355032392ceeedd2949c242956be288c60f4944eefeee4ee9ffa1f2cc188fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2025.
Transparency logRelease files / pygrestqlambda-0.0.9-py3-none-any.whl
| Download URL | pygrestqlambda-0.0.9-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
057cdadba83a16a6415e45f5e6706b2ae141af98c9a37617a76b772b98763c1c
|
|
BLAKE2b-256 checksum How to use checksums |
cfd16ae1d5546e6eea2f7a7e0b20b50637f1c20677a0e23d64401997e8123010
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2025.
Transparency log