ecssh

fill out ~/.config/ecssh.yml

test:
  some_cluster_name:
    ssh_user: ec2-user
prod: # AWS ENVIRONMENT
  public_prod: # ECS CLUSTER NAME
    ssh_user: ec2-user
    ssh_key: ~/.ssh/aws.pem
  internal_one:
    ssh_user: ec2-user
    ssh_key: ~/.ssh/id_ed25519

Metadata

Release files for ecssh 2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ecssh 2
File	Size	Uploaded	Provenance	Actions
ecssh-2.tar.gz	2.2 kB	Sep 19, 2019	Without provenance	Details for ecssh-2.tar.gz

Release files / ecssh-2.tar.gz

Download URL	ecssh-2.tar.gz
Size	2.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`3860c3dece1cf158b8b782c8f1111b0ad1c27670899059bc922c2dd2e8cc048d`
BLAKE2b-256 checksum How to use checksums	`fdd2450cb4ad214fd49f165fcd2678d0adbbcdb2ecef0b91c49633832cb270c7`
Upload date	Sep 19, 2019
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.7.4`

Security for ecssh 2

Report project as malware

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.