/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Describes the Amazon Elastic Compute Cloud instance and related resources to
* be created using the create cloud formation stack
* operation.See Also:
AWS
* API Reference
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The name of the export snapshot record, which contains the exported Lightsail * instance snapshot that will be used as the source of the new Amazon EC2 * instance.
Use the get export snapshot records operation to
* get a list of export snapshot records that you can use to create a
* CloudFormation stack.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The instance type (e.g., t2.micro) to use for the new Amazon EC2
* instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
The port configuration to use for the new Amazon EC2 instance.
The * following configuration options are available:
* DEFAULT - Use the default firewall settings from the Lightsail
* instance blueprint.
INSTANCE - Use the
* configured firewall settings from the source Lightsail instance.
NONE - Use the default Amazon EC2 security group.
CLOSED - All ports closed.
If
* you configured lightsail-connect as a cidrListAliases
* on your instance, or if you chose to allow the Lightsail browser-based SSH or
* RDP clients to connect to your instance, that configuration is not carried over
* to your new Amazon EC2 instance.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
A launch script you can create that configures a server with additional user
* data. For example, you might want to run apt-get -y update.
Depending on the machine image you choose, the command to get software
* on your instance varies. Amazon Linux and CentOS use yum, Debian
* and Ubuntu use apt-get, and FreeBSD uses pkg.
The Availability Zone for the new Amazon EC2 instance.
*/ inline const Aws::String& GetAvailabilityZone() const{ return m_availabilityZone; } /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline bool AvailabilityZoneHasBeenSet() const { return m_availabilityZoneHasBeenSet; } /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline void SetAvailabilityZone(const Aws::String& value) { m_availabilityZoneHasBeenSet = true; m_availabilityZone = value; } /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline void SetAvailabilityZone(Aws::String&& value) { m_availabilityZoneHasBeenSet = true; m_availabilityZone = std::move(value); } /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline void SetAvailabilityZone(const char* value) { m_availabilityZoneHasBeenSet = true; m_availabilityZone.assign(value); } /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline InstanceEntry& WithAvailabilityZone(const Aws::String& value) { SetAvailabilityZone(value); return *this;} /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline InstanceEntry& WithAvailabilityZone(Aws::String&& value) { SetAvailabilityZone(std::move(value)); return *this;} /** *The Availability Zone for the new Amazon EC2 instance.
*/ inline InstanceEntry& WithAvailabilityZone(const char* value) { SetAvailabilityZone(value); return *this;} private: Aws::String m_sourceName; bool m_sourceNameHasBeenSet; Aws::String m_instanceType; bool m_instanceTypeHasBeenSet; PortInfoSourceType m_portInfoSource; bool m_portInfoSourceHasBeenSet; Aws::String m_userData; bool m_userDataHasBeenSet; Aws::String m_availabilityZone; bool m_availabilityZoneHasBeenSet; }; } // namespace Model } // namespace Lightsail } // namespace Aws