amazonka-iam: Amazon Identity and Access Management SDK.
AWS Identity and Access Management AWS Identity and Access Management (IAM) is a web service that you can use to manage users and user permissions under your AWS account. This guide provides descriptions of IAM actions that you can call programmatically. For general information about IAM, see AWS Identity and Access Management (IAM). For the user guide for IAM, see Using IAM. AWS provides SDKs that consist of libraries and sample code for various programming languages and platforms (Java, Ruby, .NET, iOS, Android, etc.). The SDKs provide a convenient way to create programmatic access to IAM and AWS. For example, the SDKs take care of tasks such as cryptographically signing requests (see below), managing errors, and retrying requests automatically. For information about the AWS SDKs, including how to download and install them, see the Tools for Amazon Web Services page. We recommend that you use the AWS SDKs to make programmatic API calls to IAM. However, you can also use the IAM Query API to make direct calls to the IAM web service. To learn more about the IAM Query API, see Making Query Requests in the Using IAM guide. IAM supports GET and POST requests for all actions. That is, the API does not require you to use GET for some actions and POST for others. However, GET requests are subject to the limitation size of a URL. Therefore, for operations that require larger sizes, use a POST request. Signing Requests Requests must be signed using an access key ID and a secret access key. We strongly recommend that you do not use your AWS account access key ID and secret access key for everyday work with IAM. You can use the access key ID and secret access key for an IAM user or you can use the AWS Security Token Service to generate temporary security credentials and use those to sign requests. To sign requests, we recommend that you use Signature Version 4. If you have an existing application that uses Signature Version 2, you do not have to update it to use Signature Version 4. However, some operations now require Signature Version 4. The documentation for operations that require version 4 indicate this requirement. Additional Resources For more information, see the following: - AWS Security Credentials. This topic provides general information about the types of credentials used for accessing AWS. - IAM Best Practices. This topic presents a list of suggestions for using the IAM service to help secure your AWS resources. - Signing AWS API Requests. This set of topics walk you through the process of signing a request using an access key ID and secret access key.
The types from this library are intended to be used with amazonka, which provides mechanisms for specifying AuthN/AuthZ information and sending requests.
Use of lenses is required for constructing and manipulating types. This is due to the amount of nesting of AWS types and transparency regarding de/serialisation into more palatable Haskell values. The provided lenses should be compatible with any of the major lens libraries such as lens or lens-family-core.
[Skip to Readme]
|Versions [faq]||0.0.0, 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 22.214.171.124, 126.96.36.199, 1.3.0, 1.3.1, 1.3.2, 1.3.3, 188.8.131.52, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.5.0, 1.6.0, 1.6.1|
|Dependencies||amazonka-core (==1.3.6.*), base (>=4.7 && <5) [details]|
|Copyright||Copyright (c) 2013-2015 Brendan Hay|
|Maintainer||Brendan Hay <firstname.lastname@example.org>|
|Category||Network, AWS, Cloud, Distributed Computing|
|Source repo||head: git clone git://github.com/brendanhay/amazonka.git|
|Uploaded||by BrendanHay at 2015-11-21T10:50:58Z|
|Distributions||LTSHaskell:1.6.1, NixOS:1.6.1, Stackage:1.6.1|
|Downloads||33183 total (15 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs available [build log]
Last success reported on 2015-12-09 [all 3 reports]
For package maintainers and hackage trustees