amazon.aws.ec2_vpc_route_table_info module – Gather information about ec2 VPC route tables in AWS
Note
This module is part of the amazon.aws collection (version 7.6.1).
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 amazon.aws
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: amazon.aws.ec2_vpc_route_table_info
.
New in amazon.aws 1.0.0
Synopsis
Gather information about ec2 VPC route tables in AWS
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.6
boto3 >= 1.26.0
botocore >= 1.29.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 |
|
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. |
|
Use a The 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 |
|
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_DescribeRouteTables.html for possible filters. Default: |
|
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. |
|
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 |
|
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 VPC route tables
amazon.aws.ec2_vpc_route_table_info:
- name: Gather information about a particular VPC route table using route table ID
amazon.aws.ec2_vpc_route_table_info:
filters:
route-table-id: rtb-00112233
- name: Gather information about any VPC route table with a tag key Name and value Example
amazon.aws.ec2_vpc_route_table_info:
filters:
"tag:Name": Example
- name: Gather information about any VPC route table within VPC with ID vpc-abcdef00
amazon.aws.ec2_vpc_route_table_info:
filters:
vpc-id: vpc-abcdef00
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
A list of dictionarys describing route tables. Returned: always |
|
List of associations between the route table and one or more subnets or a gateway. Returned: always |
|
The state of the association. Returned: always |
|
The state of the association. Returned: always Sample: |
|
Additional information about the state of the association. Returned: when available Sample: |
|
ID of the internet gateway or virtual private gateway. Returned: when route table is a gateway route table Sample: |
|
Whether this is the main route table. Returned: always Sample: |
|
ID of association between route table and subnet. Returned: always Sample: |
|
ID of the route table. Returned: always Sample: |
|
ID of the subnet. Returned: when route table is a subnet route table Sample: |
|
ID of the route table (same as route_table_id for backwards compatibility). Returned: always Sample: |
|
ID of the account which owns the route table. Returned: always Sample: |
|
List of Virtual Private Gateways propagating routes. Returned: always Sample: |
|
ID of the route table. Returned: always Sample: |
|
List of routes in the route table. Returned: always |
|
CIDR block of destination. Returned: always Sample: |
|
ID of the gateway. Returned: when gateway is local or internet gateway Sample: |
|
ID of a NAT instance. Empty unless the route is via an EC2 instance. Returned: always Sample: |
|
AWS account owning the NAT instance. Empty unless the route is via an EC2 instance. Returned: always Sample: |
|
ID of the NAT gateway. Returned: when the route is via a NAT gateway. Sample: |
|
The ID of the network interface. Empty unless the route is via an EC2 instance. Returned: always Sample: |
|
mechanism through which the route is in the table. Returned: always Sample: |
|
state of the route. Returned: always Sample: |
|
Tags applied to the route table. Returned: always Sample: |
|
ID for the VPC in which the route lives. Returned: always Sample: |