Saravanan666/pypi-org huggingface dataset:
Package: aws-chain-secrets
This package aims to make using AWS SecretsManager more comfortable.IntroduceThis aims to enable the use of one or more secrets from AWS SecretsManager.If more than one secret is used, the secret specified last takes precedence.For example, if you use secrets named A and B in that order, overlapping entries from A and B will later use
the value of the specified B entry.>>>A={"foo":1,"bar":2}>>>B={"bar":3}>>>secrets("bar",casting_type=int)3Install$python-mpipinstallaws_chain_secretsHow to useNoteAWS credential is required.If your credentials installed or set to environment, you can omit credentials when initializeSecretsManager.connect and fetch manuallyfromaws_chain_secretsimportSecretsManagersecrets=SecretsManager('ap-northeast-2','secret_name_1','secret_name_2',...)secrets.connect()secrets.fetch()secrets(key="A",default=None,casting_type=int)secrets.disconnect()NoteThe secret assigned last takes precedence over secrets assigned earlier.In this case,secret_name_2has a higher priority thansecret_name_1.This works likesdict.update(secret_name_1.update(secret_name_2)).use with context managerYou can omitconnect(),fetch()anddisconnect()when using context manager.fromaws_chain_secretsimportSecretsManagerwithSecretsManager('ap-northeast-2','secret_name_1','secret_name_2',...)assecrets:secrets(key="A",default=None,casting_type=int)type castingAll secret values ​​retrieved from AWS SecretsManager are string types by default.You can change it to any type you want.>>>secrets(key="A",casting_type=int)1>>>secrets(key="SOME_ARRAY",casting_type=list)['1','2','3','4']>>>secrets(key="SOME_ARRAY",casting_type=list[int])[1,2,3,4]default valueYou can specify a default value, just like when using Pythondict’sget.# if the key value of A does not exist, 0 specified as default is returned.>>>secrets(key="A",default=0)0change valueYou can change (or add) the value of a specified secret by name.>>>secrets.set('secret_name_1','key','value')update remote (AWS secrets manager) data from localYou can update (upload) the values of a specified secret by name from local to remote.>>>secrets.update('secret_name_1')
Package: aws-check-for-domain-hijacking
# aws_check_for_domain_hijacking.pyDescription:Script has been written in python 2.7
This script fetches domains from AWS
For each domain on AWS, it fetches corresponding subdomains
It checks all these subdomains if they are vulnerable to subdomain hijacking
Writes output to multiple filesUsage:Configure aws credentials on your systemrun this “sudo python2 aws_check_for_domain_hijacking.py”Future Prospects:Script will include a known endpoint check against subdomain listScript can gatehr more subdomains from publicly accessible resources like shodan, google etc
Package: awscli-mate
Welcome toawscli_mateDocumentationawscli_mateimproves the original AWS CLI.Make sure you have done:pip install awscli_mate
pip install boto3
pip install fireSet AWS Profile as DefaultIt is very common that you wants to set a profile as the default when using a tools that doesn’t support explicit--profile...argument.awscli_mateprovides a command to do this for you. It will update your.aws/configand.aws/credentialsfile and set thedefaultprofile to the one you specified.Example:awscli_mateset_profile_as_default--profile=your_profileOne Click MFA authBased on thisAWS re:Post How do I use an MFA token to authenticate access to my AWS resources through the AWS CLI?, you have to runaws stsget-session-token...command to get some token, and manually copy and paste them to either environment variable or.aws/credentialsfile. This is a bit tedious.awscli_mateprovides a one-click command to do this for you. Basically, it will use a base profile to get the token, let’s say it isyour_profile, and automatically create / update a new profile calledyour_profile_mfain your.aws/configand.aws/credentialsfile. So you can keep using theyour_profile_mfain your application.Example:awscli_matemfa_auth--profile=your_profile--mfa_code=123456--hours=12--overwrite_default=TrueNote that this command also automatically set the MFA profile as default profile. If you don’t want to set theyour_profile_mfaas default profile automatically, you can just remove the--overwrite_defaultpart.Useawscli_mateas a Python LibrarySeeexample.Useawscli_mateas a Interactive CLISet named AWS Profile as defaultDo MFA AuthenticationKeyboard shortcuts:hit Ctrl + E or UP to move item selection up.hit Ctrl + R to scroll item selection up.hit Ctrl + D or DOWN to move item selection up.hit Ctrl + F to scroll item selection up.hit Ctrl + H or LEFT to move query input cursor to the left (this won’t work on Windows).hit Ctrl + L or RIGHT to move query input cursor to the right.hit Ctrl + G to move query input cursor to the previous word.hit Ctrl + K to move query input cursor to the next word.hit Ctrl + X to clear the query input.hit Tab to auto-complete.hit BACKSPACE to delete query input backward.hit DELETE to delete query input forward.hit Enter to run it.Installawscli_mateis released on PyPI, so all you need is:$pipinstallawscli_mateTo upgrade to latest version:$pipinstall--upgradeawscli_mate
Package: aws-cli-mfa
AWS CLI MFAIt can help you to access AWS resources through AWS CLI with MFA token.PreperationAWS CLI environemnt (including configurations in ~/.aws)$curl"https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip"-o"awscliv2.zip"$unzipawscliv2.zip
$sudo./aws/installAWS profile name should follow this rule.
You need to prepare 2 profiles.
One for your original IAM user${profile}-default, and ther other is for your temporary profile, activated by MFA token.${profile}.# Let's assume your IAM user name is 'lol'# ~/.aws/credentials[lol-default]aws_access_key_id=...aws_secret_access_key=...[lol]Usageargumentdescriptionmandatorydefault--mfaMFA token code (--token-code)Y---profileAWS profile you want to use (--profile)NAWS_PROFILE in your shell--arnARN of the MFA device (--serial-number)N.credentials' mfa_device_arn# Your profile should be 'lol'$echo$AWS_PROFILElol# 1st usage: pass arn of mfa togegher# then, credentials keep your temporary information.$aws-cli-mfa--mfa${mfa-token}--arnarn:aws:iam::${account-id}:mfa/${username}# Further usage: only pass mfa token is enough$aws-cli-mfa--mfa${mfa-token}
Package: awscli-mfa-token-manager
Credentials Manager for AWS CLI v2This program helps generate Credential for IAM users with MFA enabled. It's build to ease out generating credentials and storing them in a credentials file for further use.InstallationInstall the modulepipinstallawscli_mfa_token_managerHow it worksThis tool needs a basic config file with one or more profiles and region, output settings to work. Let's say you want to generate tokens using a config file in/opt/app/cloud/.awsdirectory. When you are running it for the first time, for an IAM user that has for example, a virtual MFA device use the following argumentsmanage_credentials--profilemfa--serial-numberarn:aws:iam::[IAM-ACCOUNTID]:mfa/[IAM-USERNAME[]--credentials-dir/opt/app/cloud/.aws--tokenXXXXXX--expires86400Wheremfa: is the profile you want to useserial_number: is the MFA device ARNcredentials-diris the location ofconfigfile , this is location where credentials file will also be savedtokenis the MFA token codeexpires is lifetime duration of the token in secondsThis command would:Fetch credentials using the serial and token codeCreate thecredentialsfile in directory/opt/app/cloud/.awsUpdate theconfigfile to addmfa_serialYou can then runmanage_credentials--profilemfa--tokenXXXXXX--credentials-dir/opt/app/cloud/.awsto refresh token for this config / profileDefault ValuesThe following default values are used, which makes these parameters optionalprofile:defaultcredentials-dir: defaults to[user.home]/.awsexpires: defaults to43200(sts default value)
Package: awscli-plugin-bolt
awscli-plugin-boltThis AWS CLI plugin provides an authentication and authorization solution for accessing Bolt securely using the AWS CLI.It uses the standard AWS CLI configuration to store the URL for accessing Bolt. Active profiles disable regular S3 request signing, and instead provide a presigned STSGetCallerIdentityAPI call to securely authenticate requests using Bolt.PrerequisitesThe minimum supported version of Python is version 3.awsclimust be installed. e.g.pip3 install awscli --userInstallationTo install the plugin package, run:pip3 install awscli-plugin-bolt --user.ConfigurationTo configure the plugin after it has been installed, useaws configure:awsconfiguresetplugins.boltawscli-plugin-bolt
aws[--profilePROFILE]configuresetbolt_custom_domain<boltcustomdomain>
aws[--profilePROFILE]configuresetbolt_az<preferredavailabilityzoneID>bolt_custom_domainFor example, to activate a Bolt service using an internal load balancer hosted athttps://bolt.us-east-1.project.nfor thestagingAWS profile, run:aws--profilestagingconfiguresetbolt_custom_domainproject.n
aws--profilestagingconfiguresetbolt_azuse1-az1Alternatively, the bolt_url and bolt_hostname can be set explicitlyaws--profilestagingconfiguresetbolt_hostnamebolt.us-east-1.project.n
aws--profilestagingconfiguresetbolt_urlhttps://quicksilver.us-east-1.project.n
aws--profilestagingconfiguresetbolt_azuse1-az1AWS CLI v2This plugin has been tested for compatibility withAWS CLI version 2, but please take note of the[plugins] configuration breaking changes. In particular, you will need to add a block like:[plugins]
cli_legacy_plugin_path = /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packagesin your~/.aws/configfile for the plugin registration to succeed.To find the correct location forcli_legacy_plugin_pathafter installing the plugin, run:pip3showawscli-plugin-bolt|grepLocation:
Package: awscli-plugin-credential-mfa
awscli-plugin-credential-mfaAutomatically asks for MFA token key to retrieve temporary credentials.Installation and Usagepythonsetup.pyinstallawsconfiguresetplugins.credentialsawscli_plugin_credential_mfaAssuming your IAM user hasMFA enabledand credentials set up, you also need to setmfa_serialandsource_profilein the configuration. Below are instructions for profiledefault, adjust as
appropriate[default]mfa_serial=arn:aws:iam::123456789012:mfa/iam-user-namesource_profile=defaultHistoryPendingNew notes here1.0.1 (2018-08-18)Initial version
Package: awscli-plugin-eucalyptus
AWS CLI plugin for Eucalyptus Cloud service endpointsAn awscli plugin to enable Eucalyptus service endpoints via configuration.AWS CLI endpoint pluginThis plugin is heavily based on theAWS CLI endpoint pluginwhich can also be used with Eucalyptus clouds as per thisblogInstallationTo install the latest release of the Eucalyptus plugin:$ pip install awscli-plugin-eucalyptusTo install the Eucalyptus plugin from source:$ pip install git+https://github.com/corymbia/eucalyptus-awscli-plugin.gitThis requirespipandgitare available.ConfigurationTo enable the plugin for a profile (or default) set theufshostand other optional items:$ cat .aws/config 
[plugins]
eucalyptus = awscli_plugin_eucalyptus

[default]
ufshost = euca-10-10-10-10.euca.me
ufsport = 8773
verify_ssl = yesUsageAssuming the plugin is configured for the default profile and text output:$ aws ec2 describe-regions
REGIONS	http://euca-10-10-10-10.euca.me:8773/	eucalyptusor:$ aws sts get-caller-identity
000366223261	arn:aws:iam::000366223261:user/admin	AIDAAY3MOQOZPRWX2TU2GCommands not supported by Eucalyptus will fail.
Package: awscli-plugin-granica
awscli-plugin-granicaThis AWS CLI plugin provides an authentication and authorization solution for accessing Granica securely using the AWS CLI.It uses the standard AWS CLI configuration to store the URL for accessing Granica. Active profiles disable regular S3 request signing, and instead provide a presigned STSGetCallerIdentityAPI call to securely authenticate requests using Granica.PrerequisitesThe minimum supported version of Python is version 3.awsclimust be installed. e.g.pip3 install awscli --userInstallationTo install the plugin package, run:python3 -m pip install awscli-plugin-granica --user.ConfigurationTo configure the plugin after it has been installed, useaws configure:awsconfiguresetplugins.granicaawscli-plugin-granica
aws[--profilePROFILE]configuresetgranica_custom_domain<Granicacustomdomain>
aws[--profilePROFILE]configuresetregion<Region>For example, to activate a Granica service using an internal load balancer hosted athttps://quicksilver.us-east-1.mydomain.mycompany.comfor thestagingAWS profile, run:aws--profilestagingconfiguresetgranica_custom_domainmydomain.mycompany.com
aws--profilestagingconfiguresetregionus-east-1AWS CLI v2This plugin has been tested for compatibility withAWS CLI version 2, but please take note of the[plugins] configuration breaking changes. In particular, you will need to add a block like:[plugins]
cli_legacy_plugin_path = /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packagesin your~/.aws/configfile for the plugin registration to succeed.To find the correct location forcli_legacy_plugin_pathafter installing the plugin, run:pip3showawscli-plugin-granica|grepLocation:
Package: awscli-plugin-logs-tail
AWS CLI plugin for tailing CloudWatch LogsAn awscli plugin backporting thetail commandfrom AWS CLI v2AWS CLI Tail CommandThis plugin is a backport of thetail commandadded in AWS CLI v2.InstallationTo install the latest release of the logs tail plugin:$ pip install awscli-plugin-logs-tailTo install the plugin from source:$ pip install git+https://github.com/corymbia/logs-tail-awscli-plugin.gitThis requirespipandgitare available.ConfigurationTo enable the plugin:$ cat .aws/config 
[plugins]
logs_tail = awscli_plugin_logs_tailUsageAssuming the plugin is registered:$ aws logs tail LOG_GROUP_NAME
...
...See command help for details:$ aws logs tail help
Package: awscli-plugin-passtotp
awscli-plugin-passtotp======================This plugin enables aws-cli to directly talk to pass to acquire anOATH-TOTP code using the pass-otp extension.Dependencies------------* pass* pass-otp* python* aws-cliInstallation------------Building and installing awscli-plugin-passtotp requires a workingPython 3 installation.a) To install it from a cloned repository:$ python3 -m pip install .b) You can also install it directly from PyPi like this:$ python3 -m pip install awscli-plugin-passtotpEnabling the plugin-------------------A new entry to the plugins section in your config (~/.aws/config)must be added to enable the plugin:[plugins]passtotp = awscli_plugin_passtotpIf using aws-cli version 2 you must specify the path to where thepackage was installed. You can use the following command to findthe right location:$ pip show awscli-plugin-passtotp | grep Location:And then add the following to your config (~/.aws/config):[plugins]cli_legacy_plugin_path = /usr/local/lib/python3.10/dist-packagespasstotp = awscli_plugin_passtotpAWS CLI configuration---------------------Specify a path to a file in your passord-store in the profiles whereyou want to use the plugin.[profile bar]mfa_path = foo/aws/bar...You can ensure you have a working pass-otp entry by running:$ pass otp foo/aws/barWhere 'foo/aws/bar' is an entry added by 'pass otp', eg:$ pass otp insert foo/aws/barUsage-----Just use the aws command with a custom role and the plugin willobtain the TOTP token from pass:$ aws s3 ls --profile myprofile2013-07-11 17:08:50 mybucket2013-07-24 14:55:44 mybucket2Acknowledgements----------------This plugin was primarily based off the work of tommie-lie inhttps://github.com/tommie-lie/awscli-plugin-yubikeytotp
Package: awscli-plugin-proxy
awscli-plugin-proxyThis awscli plugin allows usage of proxy for AWS services as configured in profile configuration.InstallationThe easiest way to install awscli-plugin-proxy is to usepip:$ pip install awscli-plugin-proxyYou can also install the latest package from GitHub source which can contain changes not yet pushed to PyPI:$ pip install git+https://github.com/cyralinc/awscli-plugin-proxy.gitor, if you installawsclivia Homebrew, which bundles its own python, install as following:$ /usr/local/opt/awscli/libexec/bin/pip install awscli-plugin-proxyGetting StartedBefore using awscli-plugin-proxy plugin, you need toconfigure awsclifirst.MUST: Once that's done, to enableawscli-plugin-proxyplugin for S3, you can run:$ aws configure set plugins.s3-proxy awscli_plugin_proxyThe above command adds below section to your aws config file. You can also directly edit your~/.aws/configwith below configuration.[plugins]
s3-proxy = awscli_plugin_s3_proxyTo add proxy configure to a profile (assuming you have atestprofile), you can run:$ aws configure --profile test set s3.proxy http://proxy-host.com:8080The above command adds below section to your profile:[profile test]
s3 =
	proxy = http://proxy-host.com:8080
s3api =
	proxy = http://proxy-host.com:8080Now you can access S3 using proxy with profile:$ aws s3 ls --profile testIf You want to use profile without passing it every time as parameter, use environment variable, ex:export AWS_PROFILE=testAlternative (classic) methodYou can follow theguide by AWSwhich describes how to use proxy using system environment variables. Here is the example:export http_proxy=http://proxy-host.com:8080
export https_proxy=http://proxy-host.com:8080
export HTTP_PROXY=http://proxy-host.com:8080
export HTTPS_PROXY=http://proxy-host.com:8080Remember that after setting these variables,ALLclients using this settings will be going through proxy!Additionally, if You are using awscli on EC2 host, addNO_PROXYvariable to allow awscli communicate with metadata endpoint:NO_PROXY=169.254.169.254
Package: awscli-plugin-s3-proxy
awscli-plugin-s3-proxy=============This awscli plugin allows usage of proxy for S3 service stored in profile configuration.------------Installation------------The easiest way to install awscli-plugin-s3-proxy is to use `pip`:$ pip install awscli-plugin-s3-proxyYou can also install the latest package from GitHub source which can contain changes not yet pushed to PyPI:$ pip install git+https://github.com/nowak-ninja/awscli-plugin-s3-proxy.gitor, if you install `awscli` via Homebrew, which bundles its own python, install as following:$ /usr/local/opt/awscli/libexec/bin/pip install awscli-plugin-s3-proxy---------------Getting Started---------------Before using awscli-plugin-s3-proxy plugin, you need to [configure awscli](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) first.**MUST**: Once that's done, to enable `awscli-plugin-s3-proxy` plugin, you can run:$ aws configure set plugins.s3-proxy awscli_plugin_s3_proxyThe above command adds below section to your aws config file. You can also directly edit your `~/.aws/config` with below configuration.[plugins]s3-proxy = awscli_plugin_s3_proxyTo add proxy configure to a profile (assuming you have a **test** profile), you can run:$ aws configure --profile test set s3.proxy http://proxy-host.com:8080The above command adds below section to your profile:[profile test]s3 =proxy = http://proxy-host.com:8080Now you can access S3 using proxy with profile:$ aws s3 ls --profile testIf You want to use profile without passing it every time as parameter, use environment variable, ex:export AWS_PROFILE=testAlternative (classic) method------------------You can follow the [guide by AWS](https://docs.aws.amazon.com/cli/latest/userguide/cli-http-proxy.html) which describes how to use proxy using system environment variables. Here is the example:export http_proxy=http://proxy-host.com:8080export https_proxy=http://proxy-host.com:8080export HTTP_PROXY=http://proxy-host.com:8080export HTTPS_PROXY=http://proxy-host.com:8080Remember that after setting these variables, `ALL` awscli requests will be going through proxy!Additionally, if You are using awscli on EC2 host, add `NO_PROXY` variable to allow awscli communicate with metadata endpoint:NO_PROXY=169.254.169.254
Package: awscli-plugin-tls
awscli-plugin-tlsA plugin for configuring TLS parameters advertised byawscliThis awscli plugin allows users to configure TLS versions and
cipher suites used when connecting to AWS services via the CLI.
It can additionally be used by boto3 applications to enable
those configurations through their~/.aws/config.Most users will not need this plugin, as theurllib3utilizes secure defaults
for these settings.DisclaimerYou are responsible for properly configuring this plugin to ensure secure
cipher suites are used when negotiating the TLS connection.
Using this plugin, it is possible for clients to configure less-secure cipher
suites than what is provided by default. Please only use this plugin if you
have a requirement to enforce specific cipher suites or TLS versions in your
applications, and are familiar with how to utilize OpenSSL's cipherlist to select
cipher suites. Be sure to test and ensure you are not advertising insecure
cipher suites before using in a production setting.Installationpip install .ConfigurationEdit your~/.aws/configto include the following plugin definition:If you are using the v1 AWS CLI, you can just add the plugin:[plugins]
tls = awscli_plugin_tlsIf you are using the v2 AWS CLI, you need to also specify thecli_legacy_plugin_path, which should
specify where yourpippackages are installed.[plugins]
cli_legacy_plugin_path = <path to your python3.7/site-packages>
tls = awscli_plugin_tlsAdditionally, under any profile (either a named profile or[default], configure
the appropriate settings:[default]
tls_ciphers = ECDHE+AES256+AESGCM
tls_version = 1.2
...other settingsUsageAWS CLIOnce configured, you can use your AWS CLI as normal:aws s3 lsBoto3You can also patch boto3 applications by calling thepatch_botocoremethod directly:import boto3
from awscli_plugin_tls import patch_botocore
patch_botocore()

s3 = boto3.client('s3')
print(s3.list_buckets())If your boto3 application needs to use a named profile, you can pass in your own
session object using that profile name:import boto3
from awscli_plugin_tls import patch_botocore
session = botocore.session.Session(profile="your-named-profile")
patch_botocore(session)

s3 = boto3.client('s3')
print(s3.list_buckets())
botocore.session.Session(profile=profile)SecuritySeeCONTRIBUTINGfor more information.LicenseThis project is licensed under the Apache-2.0 License.
Package: awscli-saml
AWS SAML CLIAuthenticate AWS CLI with SAML.InstallPippipinstallawscli-samlRun asaws-samlDockerdockerpullrivethealth/aws-samlRun asdockerrun-it-v~/.aws:/root/.awsrivethealth/aws-samlUsageObtain a SAML authentication response (e.g. using Chrome extensionhttps://github.com/rivethealth/chrome-saml).Runaws-samlcommand, providing the base64-encoded SAML response.Credentials are now saved to~/.aws/credentials, which will be used by the AWS CLI.OptionsOptions may be provided on the command line, or be saved in the profile configuration in~/.aws/config.usage: aws-saml [-h] [-p PROFILE] [-e REGION] [-d SESSION_DURATION] [-i IDP_ARN]
                [-r ROLE_ARN] [-v]
                [saml]

positional arguments:
  saml                  Base64 encoded SAML assertion. Defaults to
                        SAML_ASSERTION, or stdin.

optional arguments:
  -h, --help            show this help message and exit
  -p PROFILE, --profile PROFILE
                        AWS profile name. Defaults to AWS_PROFILE or
                        'default'.
  -e REGION, --region   REGION
                        AWS region. Defaults to AWS_DEFAULT_REGION.
  -d SESSION_DURATION, --session-duration SESSION_DURATION
                        Session duration in seconds. Defaults to
                        saml.session_duration or 3600.
  -i IDP_ARN, --idp-arn IDP_ARN
                        Authenticating SAML provider ARN. Defaults to
                        saml.idp_arn.
  -r ROLE_ARN, --role-arn ROLE_ARN
                        Assumed IAM role ARN. Defaults to saml.role_arn.
  -v, --version         show program's version number and exit