community.aws.ec2_carrier_gateway_info module – Gather information about carrier gateways in AWS
Note
This module is part of the community.aws collection (version 10.1.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.ec2_carrier_gateway_info.
New in community.aws 6.0.0
Synopsis
- Gather information about carrier gateways in AWS.
Requirements
The below requirements are needed on the host that executes this module.
- python >= 3.6
- boto3 >= 1.34.0
- botocore >= 1.34.0
Parameters
Parameter | Comments |
|---|---|
access_key aliases: aws_access_key_id, aws_access_key string | 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. |
aws_ca_bundle path | The location of a CA Bundle to use when validating SSL certificates. The |
aws_config dictionary | 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. |
carrier_gateway_ids list / elements=string | Get details of specific Carrier Gateway ID. |
debug_botocore_endpoint_logs boolean | Use a The Choices:
|
endpoint_url aliases: aws_endpoint_url string | 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 |
filters dictionary | A dict of filters to apply. Each dict item consists of a filter key and a filter value. See https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeCarrierGateways.html for possible filters. Default: |
profile aliases: aws_profile string | 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 session_token options. |
region aliases: aws_region string | 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. |
secret_key aliases: aws_secret_access_key, aws_secret_key string | 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. |
session_token aliases: aws_session_token string | 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 session_token and profile options are mutually exclusive. |
validate_certs boolean | When set to Setting validate_certs=false is strongly discouraged, as an alternative, consider setting aws_ca_bundle instead. Choices:
|
Notes
Note
- 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
# # Note: These examples do not set authentication details, see the AWS Guide for details.
- name: Gather information about all Carrier Gateways for an account or profile
community.aws.ec2_carrier_gateway_info:
region: ap-southeast-2
register: cagw_info
- name: Gather information about a filtered list of Carrier Gateways
community.aws.ec2_carrier_gateway_info:
region: ap-southeast-2
filters:
"tag:Name": "cagw-123"
register: cagw_info
- name: Gather information about a specific carrier gateway by CarrierGatewayId
community.aws.ec2_carrier_gateway_info:
region: ap-southeast-2
carrier_gateway_ids: cagw-c1231234
register: cagw_info
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key | Description |
|---|---|
carrier_gateways complex | The carrier gateways for the account. Returned: always |
|
carrier_gateway_id string |
The ID of the carrier gateway. Returned: state=present Sample: |
|
tags dictionary |
Any tags assigned to the carrier gateway. Returned: state=present Sample: |
|
vpc_id string |
The ID of the VPC. Returned: state=present Sample: |
changed boolean | True if listing the carrier gateways succeeds. Returned: always Sample: |
Collection links
© 2012–2018 Michael DeHaan
© 2018–2025 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/projects/ansible/latest/collections/community/aws/ec2_carrier_gateway_info_module.html