iam - Manage IAM users, groups, roles and keys
New in version 2.0.
Synopsis
- Allows for the management of IAM users, user API keys, groups, roles.
Requirements (on host that executes module)
- python >= 2.6
- boto
Options
parameter | required | default | choices | comments |
---|---|---|---|---|
access_key_ids | no | A list of the keys that you want impacted by the access_key_state parameter. | ||
access_key_state | no |
| When type is user, it creates, removes, deactivates or activates a user's access key(s). Note that actions apply only to keys specified. | |
aws_access_key | no | AWS access key. If not set then the value of the AWS_ACCESS_KEY_ID, AWS_ACCESS_KEY or EC2_ACCESS_KEY environment variable is used. aliases: ec2_access_key, access_key | ||
aws_secret_key | no | AWS secret key. If not set then the value of the AWS_SECRET_ACCESS_KEY, AWS_SECRET_KEY, or EC2_SECRET_KEY environment variable is used. aliases: ec2_secret_key, secret_key | ||
ec2_url | no | Url to use to connect to EC2 or your Eucalyptus cloud (by default the module will use EC2 endpoints). Ignored for modules where region is required. Must be specified for all other modules if region is not used. If not set then the value of the EC2_URL environment variable, if any, is used. | ||
groups | no | A list of groups the user should belong to. When update, will gracefully remove groups not listed. | ||
iam_type | yes |
| Type of IAM resource | |
key_count | no | 1 | When access_key_state is create it will ensure this quantity of keys are present. Defaults to 1. | |
name | yes | Name of IAM resource to create or identify | ||
new_name | no | When state is update, will replace name with new_name on IAM resource | ||
new_path | no | When state is update, will replace the path with new_path on the IAM resource | ||
password | no | When type is user and state is present, define the users login password. Also works with update. Note that always returns changed. | ||
path | no | / | When creating or updating, specify the desired path of the resource. If state is present, it will replace the current path to match what is passed in when they do not match. | |
profile (added in 1.6)
| no | Uses a boto profile. Only works with boto >= 2.24.0. | ||
security_token (added in 1.6)
| no | AWS STS security token. If not set then the value of the AWS_SECURITY_TOKEN or EC2_SECURITY_TOKEN environment variable is used. aliases: access_token | ||
state | yes |
| Whether to create, delete or update the IAM resource. Note, roles cannot be updated. | |
trust_policy (added in 2.2)
| no | The inline (JSON or YAML) trust policy document that grants an entity permission to assume the role. Mutually exclusive with trust_policy_filepath . | ||
trust_policy_filepath (added in 2.2)
| no | The path to the trust policy document that grants an entity permission to assume the role. Mutually exclusive with trust_policy . | ||
update_password | no | always |
| always will update passwords if they differ. on_create will only set the password for newly created users. |
validate_certs (added in 1.5)
| no | yes |
| When set to "no", SSL certificates will not be validated for boto versions >= 2.6.0. |
Examples
# Basic user creation example tasks: - name: Create two new IAM users with API keys iam: iam_type: user name: "{{ item }}" state: present password: "{{ temp_pass }}" access_key_state: create with_items: - jcleese - mpython # Advanced example, create two new groups and add the pre-existing user # jdavila to both groups. task: - name: Create Two Groups, Mario and Luigi iam: iam_type: group name: "{{ item }}" state: present with_items: - Mario - Luigi register: new_groups - name: iam: iam_type: user name: jdavila state: update groups: "{{ item.created_group.group_name }}" with_items: "{{ new_groups.results }}" # Example of role with custom trust policy for Lambda service - name: Create IAM role with custom trust relationship iam: iam_type: role name: AAALambdaTestRole state: present trust_policy: Version: '2012-10-17' Statement: - Action: sts:AssumeRole Effect: Allow Principal: Service: lambda.amazonaws.com
Return Values
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
role_result | the IAM.role dict returned by Boto | if iam_type=role and state=present | string | {'assume_role_policy_document': '...truncated...', 'role_name': 'my-new-role', 'create_date': '2017-09-02T14:32:23Z', 'path': '/', 'arn': 'arn:aws:iam::A1B2C3D4E5F6:role/my-new-role', 'role_id': 'AROAA1B2C3D4E5F6G7H8I'} |
roles | a list containing the name of the currently defined roles | if iam_type=role and state=present | list | ['my-new-role', 'my-existing-role-1', 'my-existing-role-2', 'my-existing-role-3', 'my-existing-role-...'] |
Notes
Note
- Currently boto does not support the removal of Managed Policies, the module will error out if your user/group/role has managed policies when you try to do state=absent. They will need to be removed manually.
- If parameters are not set within the module, the following environment variables can be used in decreasing order of precedence
AWS_URL
orEC2_URL
,AWS_ACCESS_KEY_ID
orAWS_ACCESS_KEY
orEC2_ACCESS_KEY
,AWS_SECRET_ACCESS_KEY
orAWS_SECRET_KEY
orEC2_SECRET_KEY
,AWS_SECURITY_TOKEN
orEC2_SECURITY_TOKEN
,AWS_REGION
orEC2_REGION
- Ansible uses the boto configuration file (typically ~/.boto) if no credentials are provided. See http://boto.readthedocs.org/en/latest/boto_config_tut.html
-
AWS_REGION
orEC2_REGION
can be typically be used to specify the AWS region, when required, but this can also be configured in the boto config file
Status
This module is flagged as stableinterface which means that the maintainers for this module guarantee that no backward incompatible interface changes will be made.
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.
© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.4/iam_module.html