amazon.aws.ec2_vpc_subnet_info module – Gather information about EC2 VPC subnets in AWS
Note
This module is part of the amazon.aws collection (version 9.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 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_subnet_info
.
New in amazon.aws 1.0.0
Synopsis
Gather information about EC2 VPC subnets in AWS.
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 |
|
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_DescribeSubnets.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 |
|
A list of subnet IDs to gather information for. Default: |
|
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.
# Gather information about all VPC subnets
- amazon.aws.ec2_vpc_subnet_info:
# Gather information about a particular VPC subnet using ID
- amazon.aws.ec2_vpc_subnet_info:
subnet_ids: subnet-00112233
# Gather information about any VPC subnet with a tag key Name and value Example
- amazon.aws.ec2_vpc_subnet_info:
filters:
"tag:Name": Example
# Gather information about any VPC subnet within VPC with ID vpc-abcdef00
- amazon.aws.ec2_vpc_subnet_info:
filters:
vpc-id: vpc-abcdef00
# Gather information about a set of VPC subnets, publicA, publicB and publicC within a
# VPC with ID vpc-abcdef00 and then use the jinja map function to return the
# subnet_ids as a list.
- amazon.aws.ec2_vpc_subnet_info:
filters:
vpc-id: vpc-abcdef00
"tag:Name": "{{ item }}"
loop:
- publicA
- publicB
- publicC
register: subnet_info
- set_fact:
subnet_ids: "{{ subnet_info.results | sum(attribute='subnets', start=[]) | map(attribute='subnet_id') }}"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Returns an array of complex objects as described below. Returned: success |
|
whether IPv6 address is auto-assigned to new instances. Returned: always Sample: |
|
Availability zone of the Subnet. Returned: always Sample: |
|
The AZ ID of the subnet. Returned: always Sample: |
|
number of available IPv4 addresses. Returned: always Sample: |
|
The IPv4 CIDR of the Subnet. Returned: always Sample: |
|
indicates whether this is the default Subnet for this Availability Zone. Returned: always Sample: |
|
Indicates whether DNS queries made should return synthetic IPv6 addresses for IPv4-only destinations. Returned: success Sample: |
|
Subnet resource id. Returned: always Sample: |
|
The IPv6 association ID for the currently associated CIDR. Returned: always Sample: |
|
The IPv6 CIDR block actively associated with the Subnet. Returned: always Sample: |
|
An array of IPv6 cidr block association set information. Returned: always |
|
The association ID. Returned: always |
|
The IPv6 CIDR block that is associated with the subnet. Returned: always |
|
A hash/dict that contains a single item. The state of the cidr block association. Returned: always |
|
The CIDR block association state. Returned: always |
|
Indicates whether this is an IPv6 only subnet. Returned: success Sample: |
|
Indicates whether a network interface receives a customer-owned IPv4 address. Returned: success Sample: |
|
whether public IP is auto-assigned to new instances. Returned: always Sample: |
|
The ID of the Amazon Web Services account that owns the subnet. Returned: success Sample: |
|
The type of hostnames to assign to instances in the subnet at launch. An instance hostname is based on the IPv4 address or ID of the instance. Returned: success Sample: |
|
state of the Subnet. Returned: always Sample: |
|
The Amazon Resource Name (ARN) of the subnet. Returned: success Sample: |
|
The ID of the Subnet. Returned: always |
|
tags attached to the Subnet, includes name. Returned: always Sample: |
|
the id of the VPC where this Subnet exists. Returned: always Sample: |