community.aws.redshift module – create, delete, or modify an Amazon Redshift instance
Note
This module is part of the community.aws collection (version 9.0.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
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.aws.redshift
.
New in community.aws 1.0.0
Synopsis
Creates, deletes, or modifies Amazon Redshift cluster instances.
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.6
boto3 >= 1.28.0
botocore >= 1.31.0
Parameters
Parameter |
Comments |
---|---|
AWS access key ID. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The aws_access_key and profile options are mutually exclusive. The aws_access_key_id alias was added in release 5.1.0 for consistency with the AWS botocore SDK. The ec2_access_key alias has been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
When allow_version_upgrade=true the cluster may be automatically upgraded during the maintenance window. Choices:
|
|
The number of days that automated snapshots are retained. |
|
Availability zone in which to launch cluster. |
|
The location of a CA Bundle to use when validating SSL certificates. The |
|
A dictionary to modify the botocore configuration. Parameters can be found in the AWS documentation https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html#botocore.config.Config. |
|
Name of the cluster parameter group. |
|
In which security group the cluster belongs. |
|
Which subnet to place the cluster. |
|
The type of cluster. Choices:
|
|
Which version the cluster should have. Choices:
|
|
Specifies the action to take. Choices:
|
|
Name of the database. |
|
Use a The Choices:
|
|
An Elastic IP to use for the cluster. |
|
If the cluster is encrypted or not. Choices:
|
|
URL to connect to instead of the default AWS endpoints. While this can be used to connection to other AWS-compatible services the amazon.aws and community.aws collections are only tested against AWS. The The ec2_url and s3_url aliases have been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
Whether the cluster should have enhanced VPC routing enabled. Choices:
|
|
Identifier of the final snapshot to be created before deleting the cluster. If this parameter is provided, skip_final_cluster_snapshot must be Used only when command=delete. |
|
Redshift cluster identifier. |
|
Only used when command=modify. |
|
The node type of the cluster. Require when command=create. Choices:
|
|
Number of nodes. Only used when cluster_type=multi-node. |
|
Master database password. Used only when command=create. |
|
Which port the cluster is listening on. |
|
Maintenance window in format of Times are specified in UTC. If not specified then a random 30 minute maintenance window is assigned. |
|
A named AWS profile to use for authentication. See the AWS documentation for more information about named profiles https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html. The The profile option is mutually exclusive with the aws_access_key, aws_secret_key and security_token options. |
|
If the cluster is accessible publicly or not. Choices:
|
|
If If the Tag keys beginning with Choices:
|
|
The AWS region to use. For global services such as IAM, Route53 and CloudFront, region is ignored. The See the Amazon AWS documentation for more information http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region. The Support for the |
|
AWS secret access key. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The secret_key and profile options are mutually exclusive. The aws_secret_access_key alias was added in release 5.1.0 for consistency with the AWS botocore SDK. The ec2_secret_key alias has been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
AWS STS session token for use with temporary credentials. See the AWS documentation for more information about access tokens https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys. The The security_token and profile options are mutually exclusive. Aliases aws_session_token and session_token were added in release 3.2.0, with the parameter being renamed from security_token to session_token in release 6.0.0. The security_token, aws_security_token, and access_token aliases have been deprecated and will be removed in a release after 2024-12-01. Support for the |
|
Skip a final snapshot before deleting the cluster. Used only when command=delete. Choices:
|
|
A dictionary representing the tags to be applied to the resource. If the |
|
Master database username. Used only when command=create. |
|
When set to Setting validate_certs=false is strongly discouraged, as an alternative, consider setting aws_ca_bundle instead. Choices:
|
|
VPC security group |
|
When command=create, command=modify or command=restore then wait for the database to enter the ‘available’ state. When command=delete wait for the database to be terminated. Choices:
|
|
When wait=true defines how long in seconds before giving up. Default: |
Notes
Note
Support for tags and purge_tags was added in release 1.3.0.
Caution: For modules, environment variables and configuration files are read from the Ansible ‘host’ context and not the ‘controller’ context. As such, files may need to be explicitly copied to the ‘host’. For lookup and connection plugins, environment variables and configuration files are read from the Ansible ‘controller’ context and not the ‘host’ context.
The AWS SDK (boto3) that Ansible uses may also read defaults for credentials and other settings, such as the region, from its configuration files in the Ansible ‘host’ context (typically
~/.aws/credentials
). See https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html for more information.
Examples
- name: Basic cluster provisioning example
community.aws.redshift:
command: create
node_type: ds1.xlarge
identifier: new_cluster
username: cluster_admin
password: 1nsecure
- name: Cluster delete example
community.aws.redshift:
command: delete
identifier: new_cluster
skip_final_cluster_snapshot: true
wait: true
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
dictionary containing all the cluster information Returned: success |
|
Amazon availability zone where the cluster is located. “None” until cluster is available. Returned: success Sample: |
|
Time of the cluster creation as timestamp. Returned: success Sample: |
|
Name of the database. Returned: success Sample: |
|
status of the enhanced vpc routing feature. Returned: success |
|
Id of the cluster. Returned: success Sample: |
|
Time frame when maintenance/upgrade are done. Returned: success Sample: |
|
Port of the cluster. “None” until cluster is available. Returned: success Sample: |
|
Private IP address of the main node. Returned: success Sample: |
|
Public IP address of the main node. “None” when enhanced_vpc_routing is enabled. Returned: success Sample: |
|
Status of the cluster. Returned: success Sample: |
|
aws tags for cluster. Returned: success |
|
FQDN of the main cluster node. “None” until cluster is available. Returned: success Sample: |