Are there known AWS EC2 resellers

Frequently asked questions about Amazon VPC

Q: What is a standard VPC?

A standard VPC is a logically isolated virtual network in the AWS cloud that is automatically created for your AWS account when you first provision Amazon EC2 resources. If you launch an instance without specifying a subnet ID, your instance will launch in your default VPC.

Q: What are the benefits of a standard VPC?

When you commission resources in a standard VPC, you can take advantage of the advanced networking capabilities of Amazon VPC (EC2-VPC) and the ease of use of Amazon EC2 (EC2-Classic). Features such as changing the membership of security groups on the fly, filtering outbound traffic for security groups, multiple IP addresses, and multiple network interfaces without having to explicitly create a VPC and launch instances in the VPC.

Q: What accounts are enabled for a standard VPC?

If your AWS account was created after 3/18/2013, you may be able to start resources in a standard VPC. Read this announcement on the forum to see which regions support standard VPCs. In addition, accounts that were created before the dates listed can use standard VPCs in all regions activated for standard VPCs in which you have not previously launched any EC2 instances or Amazon Elastic Load Balancing, Amazon RDS, Amazon ElastiCache or Deployed Amazon Redshift resources.

Q: How do I know if my account is configured to use a standard VPC?

The Amazon EC2 console indicates which platforms you can launch instances on in the selected region and whether you have a standard VPC in that region. Make sure the region you want is selected on the navigation bar. In the Amazon EC2 console dashboard, under Account Attributes, check Supported Platforms. If the two values ​​"EC2-Classic" and "EC2-VPC" are present, you can launch instances on both platforms. If only the value "EC2-VPC" is present, you can only launch instances in EC2-VPC. The ID of your standard VPC is displayed under "Account Attributes" if your account is configured to use a standard VPC. You can also use the EC2 DescribeAccountAttributes API or command line interface to describe your supported platforms.

Q: Do I need to be familiar with Amazon VPC to use a standard VPC?

You can launch and manage EC2 instances and other AWS resources in a standard VPC using the AWS Management Console, AWS EC2 CLI, or Amazon EC2 API. AWS automatically creates a standard VPC and subnet for you in all Availability Zones in the AWS Region. Your default VPC is connected to an internet gateway and your instances are automatically assigned public IP addresses, just like with EC2-Classic.

Q: What are the differences between instances launched in EC2-Classic and EC2-VPC?

Refer to the Differences Between EC2-Classic and EC2-VPC section in the EC2 User Guide.

Q: Do I need a VPN connection to use a standard VPC?

Standard VPCs are connected to the Internet, and all instances launched in standard subnets in the standard VPC are automatically given public IP addresses. You can add a VPN connection to your standard VPC if you want.

Q: Can I create additional VPCs and use them to complement my standard VPC?

Yes. To launch an instance in non-standard VPCs, you must provide a subnet ID when launching the instance.

Q: Can I create additional subnets in my standard VPC, e.g. B. private subnets?

Yes. To start on non-standard subnets, you can specify the destination for your startups using the console or the --subnet CLI, API, or SDK option.

Q: How many standard VPCs are possible?

You can have a default VPC in any AWS Region that has the Supported Platforms attribute set to EC2-VPC.

Q: What is the IP address range of a standard VPC?

The CIDR range of a standard VPC is Standard subnets use the CIDR area "/ 20" within the CIDR area of ​​a standard VPC.

Q: How many standard subnets does a standard VPC have?

A default subnet is created in your default VPC for each Availability Zone.

Q: Can I indicate which VPC is my default VPC?

No, not at the moment.

Q: Can I specify which subnets are my default subnets?

No, not at the moment.

Q: Can I delete a standard VPC?

Yes. A standard VPC can be deleted. After deleting the default VPC, you can create a new default VPC using the VPC console or the CLI. This creates a new standard VPC for the region. This does not restore the deleted VPC.

Q: Can I delete a default subnet?

Yes, a standard subnet can be deleted. Once deleted, you can use the command line interface or the SDK to create a new default subnet in the Availability Zone. This will create a new default subnet in the specified Availability Zone. This will not restore the deleted subnet.

Q: I already have an EC2 Classic account. Can I get a standard VPC?

The easiest way to get a standard VPC is to create a new account in a region that is enabled for standard VPCs. You can also use an existing account in a region that you have not previously used, as long as the Supported Platforms attribute for that account in that region is set to EC2-VPC.

Q: I would like a standard VPC for my existing EC2 account. Is that possible?

Yes, but we can only activate an existing account for a standard VPC if you do not already have EC2-Classic resources in the respective region for this account. In addition, you must cancel all non-VPC-provisioned Elastic Load Balancer, Amazon RDS, Amazon ElastiCache, and Amazon Redshift resources in that region. After your account has been configured for a standard VPC, all resources launched in the future, including instances launched via Auto Scaling, will be assigned to your standard VPC. To request a standard VPC for your existing account, please navigate to Account and Billing -> Service: Account -> Category: Convert EC2 Classic to VPC and submit a request. We will review your request, your existing AWS services and your EC2 Classic presence and guide you through the next steps.

Q: How does a standard VPC affect IAM accounts?

If your AWS account has a default VPC, IAM accounts associated with your AWS account use the same default VPC as your AWS account.