Assertion: default | /r/HasProperty | vpc
Facets:
Source sentences:
text: In this case, you have a default VPC in each AWS Region.
text: A default VPC is ready for you to use so that you don't have to create and configure your own VPC.
text: You can immediately start launching Amazon EC2 instances into your default VPC.
text: You can also use services such as Elastic Load Balancing, Amazon RDS, and Amazon EMR in your default VPC.
text: You can modify the components of your default VPC as needed.
text: When we create a default VPC, we do the following to set it up for you:
text: Create an internet gateway and connect it to your default VPC.
text: Create a default security group and associate it with your default VPC.
text: Create a default network access control list (ACL) and associate it with your default VPC.
text: Associate the default DHCP options set for your AWS account with your default VPC.
text: The following figure illustrates the key components that we set up for a default VPC.
text: You can optionally associate an IPv6 CIDR block with your default VPC.
text: In most cases, we automatically create a new default subnet in this Availability Zone for your default VPC within a few days.
text: However, if you made any modifications to your default VPC, we do not add a new default subnet.
text: If you created your AWS account after 2013-12-04, it supports only EC2-VPC and you have a default VPC in each AWS Region.
text: Therefore, unless you create a nondefault VPC and specify it when you launch an instance, we launch your instances into your default VPC.
text: In this case, we create a default VPC in each Region in which you haven't created any AWS resources.
text: Unless you create a nondefault VPC and specify it when you launch an instance in a new Region, we launch the instance into your default VPC for that Region.
text: If an AWS account supports only EC2-VPC, any IAM accounts associated with this AWS account also support only EC2-VPC, and use the same default VPC as the AWS account.
text: If you'd still prefer to add a default VPC to a Region that doesn't have one and supports EC2-Classic, see "I really want a default VPC for my existing EC2 account.
text: If you'd still prefer to add a default VPC to a Region that doesn't have one and supports EC2-Classic, see "I really want a default VPC for my existing EC2 account.
text: You can use the Amazon EC2 console or the command line to determine whether your AWS account supports both platforms, or if you have a default VPC.
text: For example, the following indicates that the account supports the EC2-VPC platform only, and has a default VPC with the identifier vpc-1a2b3c4d .
text: If you delete your default VPC, the Default VPC value displayed is None .
text: Viewing your default VPC and default subnets
text: You can view your default VPC and subnets using the Amazon VPC console or the command line.
text: To view your default VPC and subnets using the Amazon VPC console Open the Amazon VPC console at https://console.aws.amazon.com/vpc/ .
text: Take note of the ID of the default VPC.
text: In the search bar, type the ID of the default VPC.
text: The returned subnets are subnets in your default VPC.
text: To describe your default VPC using the command line Use the describe-vpcs (AWS CLI)
text: Use the commands with the vpc-id filter and set the filter value to the ID of the default VPC.
text: Launching an EC2 instance into your default VPC
text: When you launch an EC2 instance without specifying a subnet, it's automatically launched into a default subnet in your default VPC.
text: To launch an EC2 instance into your default VPC, use these commands without specifying a subnet or an Availability Zone.
text: To launch an EC2 instance into a specific default subnet in your default VPC, specify its subnet ID or Availability Zone.
text: If you delete your default VPC, you can create a new one.
text: Alternatively, you can create a nondefault subnet in your default VPC and contact AWS Support to mark the subnet as a default subnet.
text: Creating a default VPC
text: If you delete your default VPC, you can create a new one.
text: You cannot restore a previous default VPC that you deleted, and you cannot mark an existing nondefault VPC as a default VPC.
text: If your account supports EC2-Classic, you cannot use these procedures to create a default VPC in a Region that supports EC2-Classic.
text: When you create a default VPC, it is created with the standard components of a default VPC, including a default subnet in each Availability Zone.
text: When you create a default VPC, it is created with the standard components of a default VPC, including a default subnet in each Availability Zone.
text: If you already have a default VPC in the Region, you cannot create another one.
text: For example, you might want to create a default subnet if you have deleted a default subnet, or if AWS has added a new Availability Zone and did not automatically create a default subnet for that zone in your default VPC.
text: IPv4 CIDR block in the next available contiguous space in your default VPC.
text: If there is not enough address space in your default VPC to create a size /20
text: If you've associated an IPv6 CIDR block with your default VPC, the new default subnet does not automatically receive an IPv6 CIDR block.
text: If you delete a default VPC, you might experience problems launching Amazon Elastic Compute Cloud (Amazon EC2) instances in that Region.