Saravanan666/pypi-org huggingface dataset:
Package: aws-ssh-sync
SSH config synchronisation for AWSGeneratessh_configfiles, based on currentAmazon EC2state.FeaturesConnect to one or more regions at once.Filter EC2 instances by name. Useful for including relevant nodes only or for creating separate config sets for the same environment (e.g. use a differentUserfor different nodes).Identify hosts using tags or instance IDs:Index duplicates (e.g. in autoscaling groups) using instance launch time.Include a global name prefix and/or a region ID to identify the connection in a unique way.Use public or private IPs.Set various SSH params:Skip strict host checking, if needed. Can be useful when working with (internal) autoscaling groups.Provide a server alive interval to keep the connection from timing out.Use custom identity files.Setup a proxy command for utilizing jump hosts....Write tostdoutor amaster file with config-key substitution. Useful for working with tools, that don't support theIncludedirective.InstallationYou can install the latest package usingpip:pipinstallaws-ssh-syncUsageTo get a full list of options:aws_ssh_sync--helpPreviewThe easiest way to get apreviewof the current config in AWS is to print the output directly tostdout:aws_ssh_sync--profile<profile>--region<region>Utilising the 'Include' directiveIf you want toisolatethe generated config, you can write it to a dedicated file, andIncludeit in the main config. The base use-case is as follows:aws_ssh_sync--profile<profile>--region<region>>~/.ssh/config.d/<some_file>To extend your~/.ssh/config, add the following line:Include config.d/*Working with a single config fileSplitting config into multiple, small files keeps things elegant and clean - you should probably stick to that, if you can.Unfortunatelly, some tools may still have trouble with theIncludedirective itself. If you want to use a single file (e.g.~/.ssh/config) for keeping all configuration, then you can specify the--output-filetogether with a--config-key:aws_ssh_sync--profile<profile>--region<region>--config-key<key>--output-file<path>Behaviour:Configuration is written to the--output-filerather thanstdout.If the file doesn't exist, then it will be created.If a section identified by--config-keyexists, then it will be replaced.If no--config-keywas found, then a new section will be appended to the file.No backup file is created at the moment.ReferencesOrigin, motivation and acknowledgements- blog post.
Package: aws-ssm-commander
aws-ssm-commanderInspired byaws-ssm-treeInstallpip install aws-ssm-commanderUsageOptions:
  --debug
  --help   Show this message and exit.

Commands:
  dump   Dump the values in ssm to a param file, for backup or inspection.
  tree   Print out a tree of your SSM parameters
  write  take a yaml file, put it in to SSMdumpDumps the params on a path to a json or yaml output~> aws-ssm-commander dump /abc/123
section_a:
  username: abc123
section_b:
  password: blah
  username: foobartreeSee a visual representation of params on a path.  Useful for making sure your params out in SSM are structured as
expected~> aws-ssm-commander tree /abc/123/
abc
â””â”€â”€ 123
    â”œâ”€â”€ section_a
    â”‚   â””â”€â”€ username
    â”œâ”€â”€ section_b
    â”‚   â”œâ”€â”€ password
    â”‚   â””â”€â”€ usernamewriteTakes a yaml input file and a path prefix, and writes params to SSM.~> aws-ssm-commander write /abc/123/ my_file.ymlSaving secretsThere are two ways of saving secrets. First is by supplying a KMS key ID along with the value to encrypt. The second is to use custom KMS to store kms blobs. The former is less secure than the latter.Supplying a KMS key ID along with the value to encryptA KMS key ID can be supplied:password:
kms_key_id: f0e79e90-5672-431d-b100b-84b8ac8f1525
value: supersecretpasswordKeep in mind that if the params file is in git, the secret will be exposed in plain text!Using custom KMS keys to store kms blobs in the yaml fileA lot of the stuff you want to put in Param Store are secrets, and you don't store plaintext secrets in git!  Now you could encrypt and decrypt these files on your own, but aws-ssm-commander supports putting a KMS blob in a config file. To use this method, youmustuse a Customer Managed KMS key.You can put a KMS secret in your config files by prefixing a value with a!kmstagTo get a kms blob,KEY_ID=1234abcd-12ab-34cd-56ef-1234567890ab
awskmsencrypt--key-id$KEY_ID--plaintext"MY_SECRET"--outputtext--queryCiphertextBlobtake that output, then drop it in a value in a yaml file like so:my_thing:username:foobarpassword:!kmsWW05aWJHRjNZbXh2WWc9PQ==
Package: aws-ssm-copy
aws-ssm-copy-parametersCopy parameters from a AWS parameter store to anotherOptionsusage: aws-ssm-copy [options] PARAMETER [PARAMETER ...]positional arguments:PARAMETER             source pathoptional arguments:-h, --help             show this help message and exit
--one-level, -1        one-level copy
--recursive, -r        recursive copy
--overwrite, -f        existing values
--keep-going, -k       as much as possible, even after an error
--dry-run, -N          only show what is to be copied
--source-region REGION to get the parameters from
--source-profile NAME  to obtain the parameters from
--region REGION        to copy the parameters to
--profile NAME         to copy the parameters to
--target-path NAME     to copy the parameters to
--key-id ID            to use for parameter values in the destination
--clear-key-id, -C     clear the kms key id associated with the parameter
--with-tags, -W        copy the tags too, existing tags will be removedExamplesCopy all parameters under /dev to a new profile:aws-ssm-copy --profile binx-io --recursive /devCopy all parameters under /dev to /production, with a dry run first:aws-ssm-copy -r --dry-run --target-path /production /devRead moreabout copying aws ssm parameters from one account to another.
Package: aws-ssm-devlibx
This is a helper module to allow you to capture all the request/response which comes to your Flask app.pipinstallaws-ssm-devlibxHow to use# Set env vale "SERVICE" and "ENV"# Set 2 env variable ENV and Service# We will pick all SSM with path "/conf/{SERVICE}/{ENV}/v1"fromaws_ssmimportssmssm=ssm.SSM()ssm.setup_env_from_ssm()It will push all env variable in "/tmp/aws_ssm_env_devlibx" fileDebugsetexport SSM_DEBUG=trueto print SSM in logs
Package: aws-ssm-invoke
A wrapper around an AWS SSM send-command that can optionally wait for
execution success.UsageUsage on the tool can be found by executingaws-ssm-invoke-h.$ aws-ssm-invoke -h
usage: aws-ssm-invoke [-h] [--comment COMMENT]
                      (--instance-ids [INSTANCE_IDS [INSTANCE_IDS ...]] | --tags [TAGS [TAGS ...]])
                      [--wait] [--show-output]
                      command

positional arguments:
  command               The command to execute on all matching EC2 instances

optional xarguments:
  -h, --help            show this help message and exit
  --comment COMMENT
  --instance-ids [INSTANCE_IDS [INSTANCE_IDS ...]]
                        Instance ID's to execute on
  --tags [TAGS [TAGS ...]]
                        Key=Value pairs to execute on
  --wait                When supplied will poll the SSM command until it is
                        complete.
  --show-output         When supplied will show the output from each executionExamplesWaitUsing the--waitflag polls for command status until complete and
shows the state.$aws-ssm-invokeuptime--tagsName=database--waitExecutedcommand'uptime'-486a3994-db41-4817-b741-f374cffec294(Pending)-tag:Name=['database']-Pending(Pending)[0total,0complete,0error]-Success(NoInstancesInTag)[0total,0complete,0error]Show outputSome commands you want to see the output of, to do so specify the--show-outputflag.$aws-ssm-invokeuptime--tagsName=database--wait--show-outputExecutedcommand'uptime'-0b8deb73-2677-47a6-9167-a0889929d542(Pending)-tag:Business:Application=['ecommerce']-Pending(Pending)[0total,0complete,0error]-Success(Success)[1total,1complete,0error]Commandoutput-[Success]i-0ddf60260170be3c7(ip-172-31-9-100.ap-southeast-2.compute.internal)11:01:23up2days,5:41,0users,loadaverage:0.00,0.01,0.05AcknowledgementsProject Bootstrapped fromhttps://github.com/obi1kenobi/python-bootstrap
Package: aws-ssm-run-command
Welcome toaws_ssm_run_commandDocumentationUtility tool to use AWS SSM run command feature more efficiently.Example:run_command synchronouslyrun_command_on_one_ec2-run_python_scriptrun_command_on_one_ec2-run_python_script_large_payloadInstallaws_ssm_run_commandis released on PyPI, so all you need is to:$pipinstallaws-ssm-run-commandTo upgrade to latest version:$pipinstall--upgradeaws-ssm-run-command
Package: aws-ssm-tree
SSM TreeSSM Tree is a tool that provides a tree visualization of the parameters hierarchy from AWS System Manager Parameter Store.InstallationSSM Tree can be installed usingpip:$pipinstallaws-ssm-treeExampleUsageUsage: ssm-tree [OPTIONS]

  SSM Tree is a tool that provides a tree visualization of the parameters
  hierarchy from AWS System Manager Parameter Store.

Options:
  -p, --path TEXT       The hierarchy for the parameter. Hierarchies start
                        with a forward slash (/) and end with the parameter
                        name. Here is an example of a hierarchy: /Servers/Prod
                        [required]
  -s, --show-encrypted  Show encrypted parameters with a '*' symbol.
  --no-recursion        Prevent recursion into descending levels.
  --region TEXT         Specify which AWS Region to send this request to.
  --version             Shows the version and exit.
  --help                Shows this message and exit.LicenseThis project is licensed under the MIT License - see theLICENSEfile for details
Package: aws-ssm-tunnel-agent
ssm-tunnel-agentThis file / package should be installed on the EC2 instance
through which you want to tunnel traffic to its VPC.It is useless on its own, it should be used with[ssm-tunnel]fromaws-ssm-tools.InstallationThe agent requires Python 2.7 or newer and has no external dependencies. It should
work out of the box on any recently installedAmazon Linux 2instance.The easiest way to install the agent is fromPyPIrepository:sudo pip install aws-ssm-tunnel-agentIfpipcommand is not available you can download it straight from GitHub:sudo curl -o /usr/local/bin/ssm-tunnel-agent https://raw.githubusercontent.com/mludvig/aws-ssm-tools/master/ssm-tunnel-agent
sudo chmod +x /usr/local/bin/ssm-tunnel-agentHint: these commands can becopy & pastedto anec2-sessioncommand prompt :)Author and LicenseThis script was written byMichael Ludvigand is released underApache License 2.0.
Package: aws-sso
AWS Single Sign OnExample Usage$pipinstallaws-sso
$aws-ssositeadd--domainexample.com--username{your_name}$aws-ssodiscover--domainexample.com--skip-names
$aws-ssologin--domainexample.com$pipinstallawscli
$cdpath/to/project
$echo"export AWS_PROFILE=sbx">.envrc
$direnvallow
$awss3lsCode QualityRun the following commands to analyze the project with sonar.dockerrun-d--namesonarqube-p9000:9000sonarqube
nosetests--with-xunit--with-coverage--cover-xml
sonar-scanner-Dproject.settings=cicd/sonar-project.propertiesLinksblogcode
Package: aws-sso-cli
aws-sso-cliA program to simplify logging in and setting credentials using AWS
SSO.InstallationThis can be installed viapip:pip install aws-sso-cliYou can also find wheels from thereleases page on
gitlab.UsageRunningaws-sso-cliwith no arguments will check if you are logged
in, and log in withaws sso loginif you are not. It will
additionally create or update your credentials file (in either$AWS_SHARED_CREDENTIALS_FILEif defined or defaulting to$HOME/.aws/credentials) after logging in and will attempt to log you
into AWS ECR if docker is running.You can use a different profile thandefaultor the normalAWS_PROFILEenvironment variable by using the--profileflag.If you want to log in even if you are already logged in, pass the--forceflag.If you want to log into AWS ECR only, pass the--docker-forceflag.
This is useful if you start the docker daemon after already runningaws-sso-cli.RequirementsActually signing in to AWS requires theaws-cliprogram. This also requires
Python to be installed and the boto3 library.DevelopmentRunmake testto generate a virtual environment and run tests.
Package: aws-sso-cred-restore
aws-sso-cred-restoreThis is script is inspired fromaws2-wrapand solve problem with old sdk's  like aws-sdk-go and turn safe our
work with tools like terraform.the problemWork with terraform is more safe if we use only profile configuration and  work withworkspacesfeature.provider"aws"{profile="${terraform.env}"region="${var.region}"}But aws sso cli command cannot configure credentials file, and aws-sdk-go cannot work with new model of profile config.Using environment variables, the configuration overwrite profile option on provider block on terraform, and this isdangerous.This wrapper solvetemporary(hello aws and hashicorp, solve this plis!!) this problem.Install usingpiphttps://pypi.org/project/aws-sso-cred-restorepip install aws-sso-cred-restore==<VERSION>Run a command using AWS SSO credentialsaws-sso-cred-restore --profile <awsprofilename-or-prefix>or run to all profiles in your configaws-sso-cred-restoreThis command will get credentials using active aws sso access key section file
and restore in~/.aws/credentialsExport the credentialsThere may be circumstances when it is easier/better to set the appropriate environment variables so that they can be re-used by anyawscommand.Since the script cannot directly set the environment variables in the calling shell process, it is necessary to use the following syntax:eval "$(aws-sso-cred-restore --profile <awsprofilename-or-prefix> --export)"
Package: awsssolib
A template to create python librariesDocumentation:https://awsssolib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODO0.0.1 (24-07-2020)First Release0.0.2 (27-07-2020)bumped awsauthenticationlib0.1.0 (10-09-2020)New feature added for deleting permission set and permission set policy0.1.1 (16-10-2020)Bumped dependencies0.1.2 (18-11-2020)Fixed bug regarding permission sets0.2.0 (02-12-2020)Bumped awsauthenticationlib0.3.0 (25-01-2021)Bumped awsauthenticationlib0.4.0 (28-01-2021)Implemented explicit region passing.
Package: awsssomanager
aws-sso-managerSimple AWS SSO Manager that makes authenticating between multiple profiles and roles a breeze.Overviewaws-sso-manageris a simple cli to manage auth for aws sso accounts and roles.Setuppip3installawsssomanager
or
poetryaddawsssomanagerConfig fileCreate a config file. You can create a config file for eachssoDomain.default:loginAccount:'1234567890'ssoDomain:'myssodomain'region:'us-east-1'role_priority:-"ViewOnlyAccess"-"PowerUserAccess"-"PowerUserPlus"-"AdministratorAccess"Configure ssoDomain$aws-sso-managerconfigure/path/to/config/fileAll done!Daily OperationWhenever your tokens expire, you will need to run the command:$aws-sso-managerloginEasy ProfilesProfiles are automatically generated in the following formats and can be used directly after credentials are acquired:<account_id>_<role_name>
<account_id>
<account_name>Usage$AWS_PROFILE=<proile_name>awss3lsExample1234567890=dev

$AWS_PROFILE=devawss3ls
$AWS_PROFILE=1234567890awss3ls
$AWS_PROFILE=1234567890_AdministratorAccessawss3lsPythonAWS_AIOSESSION=AioSession(profile='dev')AWS_SESSION=Session(profile_name='dev')Help :construction_worker:Join us in discussionsI use GitHub Discussions to talk about all sorts of topics related to this repo.Open an issueFirst, check out theexisting issues. If you spot
something new, open an issue. We'll use the issue to have a conversation about the problem you want
to fix, and I'll try to get to it as soon as I can.
Package: aws_ssooidc
OverviewCreate temporary credentials with AWS SSO-OIDC access tokens.PrerequisitesPython >= 3.6boto3 (https://pypi.org/project/boto3/) >= 1.17.78Required (Positional) ArgumentsPosition 1: sso_url (the start URL for your AWS SSO login)Optional (Keyword) Argumentsclient_nameDescription: Arbitrary name of the SSO client to create.Type: StringDefault: ‘ssoclient’regionDescription: Your AWS region.Type: StringDefault: ‘us-east-1’timeoutDescription: Number of tries before giving up.Type: IntegerDefault: 30UsageInstallation:pip3installaws-ssooidc# orpython3-mpipinstallaws-ssooidcIn Python3:importaws_ssooidcasssoresponse=sso.gettoken('<sso_url>')access_token=response['accessToken']In BASH:python[/path/to/]aws_ssooidc\-u<sso_url>
Package: awsssoreporting
awsssoreporting.pyDescriptionAWS IAM Identity Center (FKA AWS SSO) connects an IdP to an AWS Organization. Identities are granted access (in the form of Permission Sets) to accounts. The combined identity/permission set/account binding is called anassignment. It is challenging to use the AWS Console to generate a report of all granted access. This package provides a way of reporting this access to the terminal or a CSV.Installationpython3 -m pip install boto3python3 -m pip install awsssoreportingUsageBecause this utility uses the AWS IAM Identity Center and Organization APIs, it must be run from the Organization management account.export AWS_PROFILE=<your AWS profile. This must have read access to the sso-admin, identitystore, and organizations API.>export AWS_DEFALT_REGION=<region AWS Identity Center is configured in>awsssoreporting.py [-a | -u] -c -f myfile.csv -q-a  Report access by AWS account-u  Report access by identity-c  Write the results to a CSV-f  The filename to write the CSV to. Otherwise, the default (aws_sso_reporting-<date>.csv) is used-q  Quite mode. No results printed to terminal. The default is False.TODOSupport more than one AWS Identity Center Instance
Package: aws-sso-util
aws-sso-utilMaking life with Identity Center a little easierAWS IAM Identity Center(formerly AWS SSO) has some rough edges, andaws-sso-utilis here to smooth them out, hopefully temporarily until AWS makes it better.aws-sso-utilcontains utilities for the following:Configuring.aws/configLogging in/outAWS SDK supportLooking up identifiersCloudFormationThe underlying Python library for Identity Center authentication isaws-sso-lib, which has useful functions like interactive login, creating a boto3 session for specific a account and role, and the programmatic versions of thelookupfunctions inaws-sso-util.aws-sso-utilsupersedesaws-sso-credential-process, which is still available in its original formhere.
Read the updated docs foraws-sso-util credential-processhere.QuickstartI recommend you installpipx, which installs the tool in an isolated virtualenv while linking the script you need.Macand Linux:brewinstallpipx
pipxensurepathOther:python3-mpipinstall--userpipx
python3-mpipxensurepathInstallpipxinstallaws-sso-utilLearnaws-sso-util--helpDocumentationSee the full docs athttps://github.com/benkehoe/aws-sso-util
Package: aws-stash
aws-stashAn attempt to make AWS SSM Parameter Store interaction easier and exploit its full potential.Several tools likechamberare already available to provide applications with secrets and other configuration values stored in AWS SSM Parameter Store as environment variables, but they were missing some handy features and flexible output formats, and I was struggling to find any that would also be able to set them.Usage$ aws-stash --help
usage: aws-stash [-h] [-p PARAMS [PARAMS ...]] [-w [WRITE]] [-m] [-f]
                 [-d DESCRIPTION] [-k KMS] [-c] [-o {text,json,export}] [-l]
                 [-r] [--delete] [-q] [--full] [-v]
                 path

positional arguments:
  path                  Path to the parameter key or folder containing
                        parameter keys

optional arguments:
  -h, --help            show this help message and exit
  -p PARAMS [PARAMS ...], --params PARAMS [PARAMS ...]
                        Parameter keys
  -w [WRITE], --write [WRITE]
                        Write parameter value, leave it empty to input it from
                        STDIN
  -m, --multi-line      Accept multi-line value from STDIN, end input with
                        CTRL+D
  -f, --force           Force overwrite existing value
  -d DESCRIPTION, --description DESCRIPTION
                        Add a description to the parameter
  -k KMS, --kms KMS     KMS key alias to encrypt the value
  -c, --copy            Copy value to the clipboard instead of showing it
  -o {text,json,export}, --output {text,json,export}
                        Output format
  -l, --list            List all paramaters under same level path
  -r, --recursive       Process all paramaters recursively starting from path
  --delete              Delete a single parameter or all parameters
                        recursively starting from path if using --recurise
  -q, --quiet           Output only the values of the parameters
  --full                Output fully qualified parameter path
  -v, --verbose         Output parameters detailsAWS credentialsThis tool combines nicely withaws-vaultto provide AWS credentials in a more secure and convenient way than storing them in~/.aws/credentialsfiles.List keys recursively$ aws-vault exec my-aws-profile -- aws-stash -r -l /
/dev/
/dev/application-bar/
/dev/application-bar/ENV_VAR_XXX
/dev/application-bar/SECRET_YYY
/dev/application-foo/
/dev/application-foo/ENV_VAR_XXX
/staging/
/staging/application-bar/
/staging/application-bar/ENV_VAR_XXX
/staging/application-bar/SECRET_YYY
/staging/application-foo/
/staging/application-foo/ENV_VAR_ZZZInstallation from sourcegit clone https://github.com/askainet/aws-stash
pip install aws-stash/