aws-glue-availability
AWS Glue provides disaster / recovery through Glue ETL retry mechanism testing for the successful connector starting with the first referenced working to the last incrementally until it finds a successful connection. To ensure a certain level of high availability (all be it not in the strictest of senses) multiple connectors need to be associated across different Availability Zones.
This tool is to aid in viewing the placement of Glue Jobs through their associated Connectors Subnet information, to provide a visual aid in understanding the distribution of Glue jobs across the VPCs / Subnets within your platform.
Running
This tool is currently containing a Python interface.
#install library from PyPi
pip install awsglueavailability
#run application
#ensure AWS Credentials are setup
python -m awsglueavailability
Permissions
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AwsIamMapper",
"Action": [
"glue:ListJobs",
"glue:GetConnection",
"vpc:DescribeSubnets"
],
"Effect": "Allow",
"Resource": "*"
}
]
}
Example Output
An output is generated
References
Metadata
Release files for awsglueavailability 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awsglueavailability-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / awsglueavailability-0.1.1-py3-none-any.whl
| Download URL | awsglueavailability-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c82e6cad73821e7d3c79caa2781737ac0737291d0e53c1370f72399e24754433
|
|
BLAKE2b-256 checksum How to use checksums |
0cc3979977b0093c3232409db3877c4fdb2297f324729a7d2e1f25a1b17a86ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 15, 2025.
Transparency log