amazon.aws.ec2_vpc_net module – Configure AWS Virtual Private Clouds
Note
This module is part of the amazon.aws collection (version 6.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 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_net
.
New in amazon.aws 1.0.0
Synopsis
Create, modify, and terminate AWS Virtual Private Clouds (VPCs).
Requirements
The below requirements are needed on the host that executes this module.
python >= 3.6
boto3 >= 1.22.0
botocore >= 1.25.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. |
|
The primary CIDR of the VPC. The first in the list will be used as the primary CIDR and is used in conjunction with name to ensure idempotence. Required when vpc_id is not set. |
|
Use a The Choices:
|
|
The id of the DHCP options to use for this VPC. |
|
Whether to enable AWS hostname support. Default value is Choices:
|
|
Whether to enable AWS DNS support. Default value is 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 |
|
Request an Amazon-provided IPv6 CIDR block with /56 prefix length. You cannot specify the range of IPv6 addresses, or the size of the CIDR block. Default value is Choices:
|
|
By default the module will not create another VPC if there is another VPC with the same name and CIDR block. Specify multi_ok=true if you want duplicate VPCs created. Choices:
|
|
The name to give your VPC. This is used in combination with cidr_block to determine if a VPC already exists. The value of name overrides any value set for At least one of name and vpc_id must be specified. name must be specified when creating a new VPC. |
|
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. |
|
Remove CIDRs that are associated with the VPC and are not specified in cidr_block. Choices:
|
|
If purge_tags=true and tags is set, existing tags will be purged from the resource to match exactly what is defined by tags parameter. If the tags parameter is not set then tags will not be modified, even if purge_tags=True. 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 |
|
The state of the VPC. Either absent or present. Choices:
|
|
A dictionary representing the tags to be applied to the resource. If the tags parameter is not set then tags will not be modified. |
|
Whether to be default or dedicated tenancy. This cannot be changed after the VPC has been created. Choices:
|
|
When set to Setting validate_certs=false is strongly discouraged, as an alternative, consider setting aws_ca_bundle instead. Choices:
|
|
The ID of the VPC. At least one of name and vpc_id must be specified. At least one of name and cidr_block must be specified. |
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: create a VPC with dedicated tenancy and a couple of tags
amazon.aws.ec2_vpc_net:
name: Module_dev2
cidr_block: 10.10.0.0/16
region: us-east-1
tags:
module: ec2_vpc_net
this: works
tenancy: dedicated
- name: create a VPC with dedicated tenancy and request an IPv6 CIDR
amazon.aws.ec2_vpc_net:
name: Module_dev2
cidr_block: 10.10.0.0/16
ipv6_cidr: True
region: us-east-1
tenancy: dedicated
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
info about the VPC that was created or deleted Returned: always |
|
The CIDR of the VPC Returned: always Sample: |
|
IPv4 CIDR blocks associated with the VPC Returned: success Sample: |
|
the id of the DHCP options associated with this VPC Returned: always Sample: |
|
VPC resource id Returned: always Sample: |
|
indicates whether VPC uses default or dedicated tenancy Returned: always Sample: |
|
IPv6 CIDR blocks associated with the VPC Returned: success Sample: |
|
indicates whether this is the default VPC Returned: always Sample: |
|
The Name tag of the VPC. Returned: When the Name tag has been set on the VPC Sample: |
|
The AWS account which owns the VPC. Returned: always Sample: |
|
state of the VPC Returned: always Sample: |
|
tags attached to the VPC, includes name Returned: always |
|
name tag for the VPC Returned: always Sample: |