aws_api_gateway - Manage AWS API Gateway APIs
New in version 2.4.
Synopsis
- Allows for the management of API Gatway APIs
- Normally you should give the api_id since there is no other stable guaranteed unique identifier for the API. If you do not give api_id then a new API will be create each time this is run.
- Beware that there are very hard limits on the rate that you can call API Gateway’s REST API. You may need to patch your boto. See https://github.com/boto/boto3/issues/876 and discuss with your AWS rep.
- swagger_file and swagger_text are passed directly on to AWS transparently whilst swagger_dict is an ansible dict which is converted to JSON before the API definitions are uploaded.
Requirements (on host that executes module)
- boto
- boto3
- python >= 2.6
Options
parameter | required | default | choices | comments |
---|---|---|---|---|
api_id | no | The ID of the API you want to manage. | ||
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 | ||
deploy_desc | no | Automatic deployment by Ansible. | Description of the deployment - recorded and visible in the AWS console. | |
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. | ||
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 | ||
stage | no | The name of the stage the API should be deployed to. | ||
state | no | present |
| NOT IMPLEMENTED Create or delete API - currently we always create. |
swagger_dict | no | Swagger definitions API ansible dictionary which will be converted to JSON and uploaded. | ||
swagger_file | no | JSON or YAML file containing swagger definitions for API. Exactly one of swagger_file, swagger_text or swagger_dict must be present. | ||
swagger_text | no | Swagger definitions for API in JSON or YAML as a string direct from playbook. | ||
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
# Update API resources for development tasks: - name: update API aws_api_gateway: api_id: 'abc123321cba' state: present swagger_file: my_api.yml # update definitions and deploy API to production tasks: - name: deploy API aws_api_gateway: api_id: 'abc123321cba' state: present swagger_file: my_api.yml stage: production deploy_desc: Make auth fix available.
Return Values
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
output | the data returned by put_restapi in boto3 | success | dict | {'data': {'id': 'abc123321cba', 'name': 'MY REST API', 'createdDate': 1484233401}} |
Notes
Note
- A future version of this module will probably use tags or another ID so that an API can be create only once.
- As an early work around an intermediate version will probably do the same using a tag embedded in the API name.
- 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 preview which means that it is not guaranteed to have a backwards compatible interface.
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/aws_api_gateway_module.html