community.aws.elasticache_info – Retrieve information for AWS ElastiCache clusters
Note
This plugin is part of the community.aws collection (version 1.5.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.aws
.
To use it in a playbook, specify: community.aws.elasticache_info
.
New in version 1.0.0: of community.aws
Synopsis
Retrieve information from AWS ElastiCache clusters
This module was called
elasticache_facts
before Ansible 2.9. The usage did not change.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.6
boto
Parameters
Parameter |
Comments |
---|---|
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. If profile is set this parameter is ignored. Passing the aws_access_key and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
The location of a CA Bundle to use when validating SSL certificates. Only used for boto3 based modules. Note: The CA Bundle is read ‘module’ side and may need to be explicitly copied from the controller if not run locally. |
|
A dictionary to modify the botocore configuration. Parameters can be found at https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html#botocore.config.Config. Only the ‘user_agent’ key is used for boto modules. See http://boto.cloudhackers.com/en/latest/boto_config_tut.html#boto for more boto configuration. |
|
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. If profile is set this parameter is ignored. Passing the aws_secret_key and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
Use a botocore.endpoint logger to parse the unique (rather than total) “resource:action” API calls made during a task, outputing the set to the resource_actions key in the task results. Use the aws_resource_action callback to output to total list made during a playbook. The ANSIBLE_DEBUG_BOTOCORE_LOGS environment variable may also be used. Choices:
|
|
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. |
|
The name of an ElastiCache cluster. |
|
Uses a boto profile. Only works with boto >= 2.24.0. Using profile will override aws_access_key, aws_secret_key and security_token and support for passing them at the same time as profile has been deprecated. aws_access_key, aws_secret_key and security_token will be made mutually exclusive with profile after 2022-06-01. |
|
The AWS region to use. If not specified then the value of the AWS_REGION or EC2_REGION environment variable, if any, is used. See http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region |
|
AWS STS security token. If not set then the value of the AWS_SECURITY_TOKEN or EC2_SECURITY_TOKEN environment variable is used. If profile is set this parameter is ignored. Passing the security_token and profile options at the same time has been deprecated and the options will be made mutually exclusive after 2022-06-01. |
|
When set to “no”, SSL certificates will not be validated for boto versions >= 2.6.0. Choices:
|
Notes
Note
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_PROFILE
orAWS_DEFAULT_PROFILE
,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
,AWS_CA_BUNDLE
Ansible uses the boto configuration file (typically ~/.boto) if no credentials are provided. See https://boto.readthedocs.io/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
Examples
- name: obtain all ElastiCache information
community.aws.elasticache_info:
- name: obtain all information for a single ElastiCache cluster
community.aws.elasticache_info:
name: test_elasticache
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
List of ElastiCache clusters Returned: always |
|
Whether to automatically upgrade to minor versions Returned: always Sample: true |
|
Date and time cluster was created Returned: always Sample: “2017-09-15T05:43:46.038000+00:00” |
|
ID of the cache cluster Returned: always Sample: “abcd-1234-001” |
|
Status of ElastiCache cluster Returned: always Sample: “available” |
|
Instance type of ElastiCache nodes Returned: always Sample: “cache.t2.micro” |
|
List of ElastiCache nodes in the cluster Returned: always |
|
Date and time node was created Returned: always Sample: “2017-09-15T05:43:46.038000+00:00” |
|
ID of the cache node Returned: always Sample: “0001” |
|
Status of the cache node Returned: always Sample: “available” |
|
Availability Zone in which the cache node was created Returned: always Sample: “ap-southeast-2b” |
|
Connection details for the cache node Returned: always |
|
URL of the cache node endpoint Returned: always Sample: “abcd-1234-001.bgiz2p.0001.apse2.cache.amazonaws.com” |
|
Port of the cache node endpoint Returned: always Sample: 6379 |
|
Status of the Cache Parameter Group Returned: always Sample: “in-sync” |
|
Contents of the Cache Parameter Group Returned: always |
|
Cache nodes which need to be rebooted for parameter changes to be applied Returned: always Sample: [] |
|
Name of the cache parameter group Returned: always Sample: “default.redis3.2” |
|
Status of parameter updates Returned: always Sample: “in-sync” |
|
Security Groups used by the cache Returned: always Sample: [“sg-abcd1234”] |
|
ElastiCache Subnet Group used by the cache Returned: always Sample: “abcd-subnet-group” |
|
URL of client download web page Returned: always Sample: “https://console.aws.amazon.com/elasticache/home#client-download:” |
|
Engine used by ElastiCache Returned: always Sample: “redis” |
|
Version of ElastiCache engine Returned: always Sample: “3.2.4” |
|
Configuration of notifications Returned: if notifications are enabled |
|
ARN of notification destination topic Returned: if notifications are enabled Sample: “arn:aws:sns:*:123456789012:my_topic” |
|
Name of notification destination topic Returned: if notifications are enabled Sample: “MyTopic” |
|
Number of Cache Nodes Returned: always Sample: 1 |
|
Values that are pending modification Returned: always |
|
Preferred Availability Zone Returned: always Sample: “ap-southeast-2b” |
|
Time slot for preferred maintenance window Returned: always Sample: “sat:12:00-sat:13:00” |
|
Replication Group Id Returned: always Sample: “replication-001” |
|
List of Security Groups associated with ElastiCache Returned: always |
|
Security Group ID Returned: always Sample: “sg-abcd1234” |
|
Status of Security Group Returned: always Sample: “active” |
|
Tags applied to the ElastiCache cluster Returned: always Sample: {“Application”: “web”, “Environment”: “test”} |
Authors
Will Thames (@willthames)