Popularity
2.8
Declining
Activity
0.0
Declining
3
3
2
Programming language: Crystal
License: MIT License
Tags:
Third-party APIs
Latest version: v0.4.0
aws-credentials alternatives and similar shards
Based on the "Third-party APIs" category.
Alternatively, view aws-credentials alternatives based on common mentions on social networks and blogs.
-
discordcr
Minimalist Discord library for Crystal. (Still WIP, but usable) -
TelegramBot
(deprecated) see https://github.com/protoncr/tourmaline instead -
twitter-crystal
A library to access the Twitter API using Crystal -
crystal_slack
Parse Slack slash commands or send incoming web hooks from Crystal -
open_exchange_rates
A library for Open Exchange Rates API -
crystal-consul
Crystal client for Consul (http://www.consul.io/) -
mollie.cr
Mollie Payments API client for Crystal http://www.mollie.com -
twilio.cr
A Crystal shard for communicating with the Twilio API -
aws-signer.cr
This library signs your HTTP requests using AWS v4 -
GDAX
๐ GDAX REST and WebSocket API wrapper to trade blockchain cryptocurrencies like bitcoin, Litecoin and Ethereum. -
soundcloud-crystal
A library to access the SoundCloud API using Crystal -
bugsnag.cr
bugsnag exception notifier written in crystal. Supports sidekiq.cr, kemal, HTTP::Server. -
web_finger
A WebFinger (https://tools.ietf.org/html/rfc7033) client for Crystal. -
crystal-connpass
:anchor: A Crystal wrapper for the Connpass API -
fantasy_football_nerd_api
Crystal library for Fantasy Football Nerd API
Static code analysis for 29 languages.
Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
Promo
www.sonarqube.org
Do you think we are missing an alternative of aws-credentials or a related project?
README
aws-credentials
Get AWS credentials in various ways.
Installation
- Add the dependency to your
shard.yml
:
dependencies:
aws-credentials:
github: y2k2mt/aws-credentials.cr
- Run
shards install
Usage
Providers
resolves credentials in order from givenProvider
.
In the example below, at first ,Providers
resolves credentials from EnvProvider ('AWS_ACCESS_KEY_ID' and 'AWS_SECRET_ACCESS_KEY' in env) and then resolves credentials from SharedCredentialFileProvider ('~/.aws/credentials').
require "aws-credentials"
include Aws::Credentials
provider = Providers.new ([
EnvProvider.new,
SharedCredentialFileProvider.new
] of Provider)
credentials = provider.credentials
# Aws::Credentials::Credentials(@access_key_id="AKIA...",@expiration=nil,@secret_access_key="mVlf...",@session_token=nil)
Current Provider
implementation is as follows:
- EnvProvider
- SharedCredentialFileProvider
- InstanceMetadataProvider
- ContainerCredentialProvider
- AssumeRoleProvider
- Usage: Please watch
spec/it/assume_role_with_sts_spec.cr
- Usage: Please watch
- SimpleCredentials (Simply holds given credentials)
Contributing
- Fork it (https://github.com/y2k2mt/aws-credentials/fork)
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request
Contributors
- y2k2mt - creator and maintainer