Expand description
Data structures used by operation inputs/outputs.
Modules§
- builders
- Builders
Structs§
- Accelerator
Count The minimum and maximum number of accelerators (GPUs, FPGAs, or Amazon Web Services Inferentia chips) on an instance.
- Accelerator
Count Request The minimum and maximum number of accelerators (GPUs, FPGAs, or Amazon Web Services Inferentia chips) on an instance. To exclude accelerator-enabled instance types, set
Max
to0
.- Accelerator
Total Memory MiB The minimum and maximum amount of total accelerator memory, in MiB.
- Accelerator
Total Memory MiBRequest The minimum and maximum amount of total accelerator memory, in MiB.
- Access
Scope Analysis Finding Describes a finding for a Network Access Scope.
- Access
Scope Path Describes a path.
- Access
Scope Path Request Describes a path.
- Account
Attribute Describes an account attribute.
- Account
Attribute Value Describes a value of an account attribute.
- Active
Instance Describes a running instance in a Spot Fleet.
- Active
VpnTunnel Status Contains information about the current security configuration of an active VPN tunnel.
- AddIpam
Operating Region Add an operating Region to an IPAM. Operating Regions are Amazon Web Services Regions where the IPAM is allowed to manage IP address CIDRs. IPAM only discovers and monitors resources in the Amazon Web Services Regions you select as operating Regions.
For more information about operating Regions, see Create an IPAM in the Amazon VPC IPAM User Guide.
- AddIpam
Organizational Unit Exclusion Add an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
- AddPrefix
List Entry An entry for a prefix list.
- Added
Principal Describes a principal.
- Additional
Detail Describes an additional detail for a path analysis. For more information, see Reachability Analyzer additional detail codes.
- Address
Describes an Elastic IP address, or a carrier IP address.
- Address
Attribute The attributes associated with an Elastic IP address.
- Address
Transfer Details on the Elastic IP address transfer. For more information, see Transfer Elastic IP addresses in the Amazon VPC User Guide.
- Allowed
Principal Describes a principal.
- Alternate
Path Hint Describes an potential intermediate component of a feasible path.
- Analysis
AclRule Describes a network access control (ACL) rule.
- Analysis
Component Describes a path component.
- Analysis
Load Balancer Listener Describes a load balancer listener.
- Analysis
Load Balancer Target Describes a load balancer target.
- Analysis
Packet Header Describes a header. Reflects any changes made by a component as traffic passes through. The fields of an inbound header are null except for the first component of a path.
- Analysis
Route Table Route Describes a route table route.
- Analysis
Security Group Rule Describes a security group rule.
- AsnAssociation
An Autonomous System Number (ASN) and BYOIP CIDR association.
- AsnAuthorization
Context Provides authorization for Amazon to bring an Autonomous System Number (ASN) to a specific Amazon Web Services account using bring your own ASN (BYOASN). For details on the format of the message and signature, see Tutorial: Bring your ASN to IPAM in the Amazon VPC IPAM guide.
- Assigned
Private IpAddress Describes the private IP addresses assigned to a network interface.
- Associated
Role Information about the associated IAM roles.
- Associated
Target Network Describes a target network that is associated with a Client VPN endpoint. A target network is a subnet in a VPC.
- Association
Status Describes the state of a target network association.
- Athena
Integration Describes integration options for Amazon Athena.
- Attachment
EnaSrd Specification ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the maximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. With ENA Express, you can communicate between two EC2 instances in the same subnet within the same account, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
To improve the reliability of network packet delivery, ENA Express reorders network packets on the receiving end by default. However, some UDP-based applications are designed to handle network packets that are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express is enabled, you can specify whether UDP network traffic uses it.
- Attachment
EnaSrd UdpSpecification ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic automatically uses it. However, some UDP-based applications are designed to handle network packets that are out of order, without a need for retransmission, such as live video broadcasting or other near-real-time applications. For UDP traffic, you can specify whether to use ENA Express, based on your application environment needs.
- Attribute
Boolean Value Describes a value for a resource attribute that is a Boolean value.
- Attribute
Summary A summary report for the attribute across all Regions.
- Attribute
Value Describes a value for a resource attribute that is a String.
- Authorization
Rule Information about an authorization rule.
- Availability
Zone Describes Availability Zones, Local Zones, and Wavelength Zones.
- Availability
Zone Message Describes a message about an Availability Zone, Local Zone, or Wavelength Zone.
- Available
Capacity The capacity information for instances that can be launched onto the Dedicated Host.
- Baseline
EbsBandwidth Mbps The minimum and maximum baseline bandwidth to Amazon EBS, in Mbps. For more information, see Amazon EBS–optimized instances in the Amazon EC2 User Guide.
- Baseline
EbsBandwidth Mbps Request The minimum and maximum baseline bandwidth to Amazon EBS, in Mbps. For more information, see Amazon EBS–optimized instances in the Amazon EC2 User Guide.
- Baseline
Performance Factors The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Amazon EC2 uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application.
Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying
c6i
would use the CPU performance of thec6i
family as the baseline reference.- Baseline
Performance Factors Request The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Amazon EC2 uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application.
Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying
c6i
would use the CPU performance of thec6i
family as the baseline reference.- Blob
Attribute Value - Block
Device Mapping Describes a block device mapping, which defines the EBS volumes and instance store volumes to attach to an instance at launch.
- Block
Device Mapping Response Describes a block device mapping, which defines the EBS volumes and instance store volumes to attach to an instance at launch.
- Block
Public Access States The state of VPC Block Public Access (BPA).
- Bundle
Task Describes a bundle task.
- Bundle
Task Error Describes an error for
BundleInstance
.- Byoasn
The Autonomous System Number (ASN) and BYOIP CIDR association.
- Byoip
Cidr Information about an address range that is provisioned for use with your Amazon Web Services resources through bring your own IP addresses (BYOIP).
- Cancel
Capacity Reservation Fleet Error Describes a Capacity Reservation Fleet cancellation error.
- Cancel
Spot Fleet Requests Error Describes a Spot Fleet error.
- Cancel
Spot Fleet Requests Error Item Describes a Spot Fleet request that was not successfully canceled.
- Cancel
Spot Fleet Requests Success Item Describes a Spot Fleet request that was successfully canceled.
- Cancelled
Spot Instance Request Describes a request to cancel a Spot Instance.
- Capacity
Allocation Information about instance capacity usage for a Capacity Reservation.
- Capacity
Block Extension Describes a Capacity Block extension. With an extension, you can extend the duration of time for an existing Capacity Block.
- Capacity
Block Extension Offering The recommended Capacity Block extension that fits your search requirements.
- Capacity
Block Offering The recommended Capacity Block that fits your search requirements.
- Capacity
Reservation Describes a Capacity Reservation.
- Capacity
Reservation Billing Request Information about a request to assign billing of the unused capacity of a Capacity Reservation.
- Capacity
Reservation Commitment Info Information about your commitment for a future-dated Capacity Reservation.
- Capacity
Reservation Fleet Information about a Capacity Reservation Fleet.
- Capacity
Reservation Fleet Cancellation State Describes a Capacity Reservation Fleet that was successfully cancelled.
- Capacity
Reservation Group Describes a resource group to which a Capacity Reservation has been added.
- Capacity
Reservation Info Information about a Capacity Reservation.
- Capacity
Reservation Options Describes the strategy for using unused Capacity Reservations for fulfilling On-Demand capacity.
This strategy can only be used if the EC2 Fleet is of type
instant
.For more information about Capacity Reservations, see On-Demand Capacity Reservations in the Amazon EC2 User Guide. For examples of using Capacity Reservations in an EC2 Fleet, see EC2 Fleet example configurations in the Amazon EC2 User Guide.
- Capacity
Reservation Options Request Describes the strategy for using unused Capacity Reservations for fulfilling On-Demand capacity.
This strategy can only be used if the EC2 Fleet is of type
instant
.For more information about Capacity Reservations, see On-Demand Capacity Reservations in the Amazon EC2 User Guide. For examples of using Capacity Reservations in an EC2 Fleet, see EC2 Fleet example configurations in the Amazon EC2 User Guide.
- Capacity
Reservation Specification Describes an instance's Capacity Reservation targeting option.
Use the
CapacityReservationPreference
parameter to configure the instance to run as an On-Demand Instance, to run in anyopen
Capacity Reservation that has matching attributes, or to run only in a Capacity Reservation or Capacity Reservation group. Use theCapacityReservationTarget
parameter to explicitly target a specific Capacity Reservation or a Capacity Reservation group.You can only specify
CapacityReservationPreference
andCapacityReservationTarget
if theCapacityReservationPreference
iscapacity-reservations-only
.- Capacity
Reservation Specification Response Describes the instance's Capacity Reservation targeting preferences. The action returns the
capacityReservationPreference
response element if the instance is configured to run in On-Demand capacity, or if it is configured in run in anyopen
Capacity Reservation that has matching attributes (instance type, platform, Availability Zone). The action returns thecapacityReservationTarget
response element if the instance explicily targets a specific Capacity Reservation or Capacity Reservation group.- Capacity
Reservation Target Describes a target Capacity Reservation or Capacity Reservation group.
- Capacity
Reservation Target Response Describes a target Capacity Reservation or Capacity Reservation group.
- Carrier
Gateway Describes a carrier gateway.
- Certificate
Authentication Information about the client certificate used for authentication.
- Certificate
Authentication Request Information about the client certificate to be used for authentication.
- Cidr
Authorization Context Provides authorization for Amazon to bring a specific IP address range to a specific Amazon Web Services account using bring your own IP addresses (BYOIP). For more information, see Configuring your BYOIP address range in the Amazon EC2 User Guide.
- Cidr
Block Describes an IPv4 CIDR block.
- Classic
Link DnsSupport Deprecated.
Describes the ClassicLink DNS support status of a VPC.
- Classic
Link Instance Deprecated.
Describes a linked EC2-Classic instance.
- Classic
Load Balancer Describes a Classic Load Balancer.
- Classic
Load Balancers Config Describes the Classic Load Balancers to attach to a Spot Fleet. Spot Fleet registers the running Spot Instances with these Classic Load Balancers.
- Client
Certificate Revocation List Status Describes the state of a client certificate revocation list.
- Client
Connect Options The options for managing connection authorization for new client connections.
- Client
Connect Response Options The options for managing connection authorization for new client connections.
- Client
Data Describes the client-specific data.
- Client
Login Banner Options Options for enabling a customizable text banner that will be displayed on Amazon Web Services provided clients when a VPN session is established.
- Client
Login Banner Response Options Current state of options for customizable text banner that will be displayed on Amazon Web Services provided clients when a VPN session is established.
- Client
Route Enforcement Options Client Route Enforcement is a feature of Client VPN that helps enforce administrator defined routes on devices connected through the VPN. This feature helps improve your security posture by ensuring that network traffic originating from a connected client is not inadvertently sent outside the VPN tunnel.
Client Route Enforcement works by monitoring the route table of a connected device for routing policy changes to the VPN connection. If the feature detects any VPN routing policy modifications, it will automatically force an update to the route table, reverting it back to the expected route configurations.
- Client
Route Enforcement Response Options The current status of Client Route Enforcement.
- Client
VpnAuthentication Describes the authentication methods used by a Client VPN endpoint. For more information, see Authentication in the Client VPN Administrator Guide.
- Client
VpnAuthentication Request Describes the authentication method to be used by a Client VPN endpoint. For more information, see Authentication in the Client VPN Administrator Guide.
- Client
VpnAuthorization Rule Status Describes the state of an authorization rule.
- Client
VpnConnection Describes a client connection.
- Client
VpnConnection Status Describes the status of a client connection.
- Client
VpnEndpoint Describes a Client VPN endpoint.
- Client
VpnEndpoint Attribute Status Describes the status of the Client VPN endpoint attribute.
- Client
VpnEndpoint Status Describes the state of a Client VPN endpoint.
- Client
VpnRoute Information about a Client VPN endpoint route.
- Client
VpnRoute Status Describes the state of a Client VPN endpoint route.
- Cloud
Watch LogOptions Options for sending VPN tunnel logs to CloudWatch.
- Cloud
Watch LogOptions Specification Options for sending VPN tunnel logs to CloudWatch.
- Coip
Address Usage Describes address usage for a customer-owned address pool.
- Coip
Cidr Information about a customer-owned IP address range.
- Coip
Pool Describes a customer-owned address pool.
- Connection
LogOptions Describes the client connection logging options for the Client VPN endpoint.
- Connection
LogResponse Options Information about the client connection logging options for a Client VPN endpoint.
- Connection
Notification Describes a connection notification for a VPC endpoint or VPC endpoint service.
- Connection
Tracking Configuration A security group connection tracking configuration that enables you to set the idle timeout for connection tracking on an Elastic network interface. For more information, see Connection tracking timeouts in the Amazon EC2 User Guide.
- Connection
Tracking Specification A security group connection tracking specification that enables you to set the idle timeout for connection tracking on an Elastic network interface. For more information, see Connection tracking timeouts in the Amazon EC2 User Guide.
- Connection
Tracking Specification Request A security group connection tracking specification request that enables you to set the idle timeout for connection tracking on an Elastic network interface. For more information, see Connection tracking timeouts in the Amazon EC2 User Guide.
- Connection
Tracking Specification Response A security group connection tracking specification response that enables you to set the idle timeout for connection tracking on an Elastic network interface. For more information, see Connection tracking timeouts in the Amazon EC2 User Guide.
- Conversion
Task Describes a conversion task.
- CpuOptions
The CPU options for the instance.
- CpuOptions
Request The CPU options for the instance. Both the core count and threads per core must be specified in the request.
- CpuPerformance
Factor The CPU performance to consider, using an instance family as the baseline reference.
- CpuPerformance
Factor Request The CPU performance to consider, using an instance family as the baseline reference.
- Create
Fleet Error Describes the instances that could not be launched by the fleet.
- Create
Fleet Instance Describes the instances that were launched by the fleet.
- Create
Transit Gateway Connect Request Options The options for a Connect attachment.
- Create
Transit Gateway Multicast Domain Request Options The options for the transit gateway multicast domain.
- Create
Transit Gateway Peering Attachment Request Options Describes whether dynamic routing is enabled or disabled for the transit gateway peering request.
- Create
Transit Gateway VpcAttachment Request Options Describes the options for a VPC attachment.
- Create
Verified Access Endpoint Cidr Options Describes the CIDR options for a Verified Access endpoint.
- Create
Verified Access Endpoint EniOptions Describes the network interface options when creating an Amazon Web Services Verified Access endpoint using the
network-interface
type.- Create
Verified Access Endpoint Load Balancer Options Describes the load balancer options when creating an Amazon Web Services Verified Access endpoint using the
load-balancer
type.- Create
Verified Access Endpoint Port Range Describes the port range for a Verified Access endpoint.
- Create
Verified Access Endpoint RdsOptions Describes the RDS options for a Verified Access endpoint.
- Create
Verified Access Native Application Oidc Options Describes the OpenID Connect (OIDC) options.
- Create
Verified Access Trust Provider Device Options Describes the options when creating an Amazon Web Services Verified Access trust provider using the
device
type.- Create
Verified Access Trust Provider Oidc Options Describes the options when creating an Amazon Web Services Verified Access trust provider using the
user
type.- Create
Volume Permission Describes the user or group to be added or removed from the list of create volume permissions for a volume.
- Create
Volume Permission Modifications Describes modifications to the list of create volume permissions for a volume.
- Credit
Specification Describes the credit option for CPU usage of a T instance.
- Credit
Specification Request The credit option for CPU usage of a T instance.
- Customer
Gateway Describes a customer gateway.
- Data
Query A query used for retrieving network health data.
- Data
Response The response to a
DataQuery
.- Declarative
Policies Report Describes the metadata of the account status report.
- Delete
Fleet Error Describes an EC2 Fleet error.
- Delete
Fleet Error Item Describes an EC2 Fleet that was not successfully deleted.
- Delete
Fleet Success Item Describes an EC2 Fleet that was successfully deleted.
- Delete
Launch Template Versions Response Error Item Describes a launch template version that could not be deleted.
- Delete
Launch Template Versions Response Success Item Describes a launch template version that was successfully deleted.
- Delete
Queued Reserved Instances Error Describes the error for a Reserved Instance whose queued purchase could not be deleted.
- Delete
Snapshot Return Code The snapshot ID and its deletion result code.
- Deregister
Instance TagAttribute Request Information about the tag keys to deregister for the current Region. You can either specify individual tag keys or deregister all tag keys in the current Region. You must specify either
IncludeAllTagsOfInstance
orInstanceTagKeys
in the request- Describe
Fast Launch Images Success Item Describe details about a Windows image with Windows fast launch enabled that meets the requested criteria. Criteria are defined by the
DescribeFastLaunchImages
action filters.- Describe
Fast Snapshot Restore Success Item Describes fast snapshot restores for a snapshot.
- Describe
Fleet Error Describes the instances that could not be launched by the fleet.
- Describe
Fleets Instances Describes the instances that were launched by the fleet.
- Destination
Options Request Describes the destination options for a flow log.
- Destination
Options Response Describes the destination options for a flow log.
- Device
Options Describes the options for an Amazon Web Services Verified Access device-identity based trust provider.
- Dhcp
Configuration Describes a DHCP configuration option.
- Dhcp
Options The set of DHCP options.
- Directory
Service Authentication Describes an Active Directory.
- Directory
Service Authentication Request Describes the Active Directory to be used for client authentication.
- Disable
Fast Snapshot Restore Error Item Contains information about the errors that occurred when disabling fast snapshot restores.
- Disable
Fast Snapshot Restore State Error Describes an error that occurred when disabling fast snapshot restores.
- Disable
Fast Snapshot Restore State Error Item Contains information about an error that occurred when disabling fast snapshot restores.
- Disable
Fast Snapshot Restore Success Item Describes fast snapshot restores that were successfully disabled.
- Disk
Image Describes a disk image.
- Disk
Image Description Describes a disk image.
- Disk
Image Detail Describes a disk image.
- Disk
Image Volume Description Describes a disk image volume.
- Disk
Info Describes a disk.
- DnsEntry
Describes a DNS entry.
- DnsOptions
Describes the DNS options for an endpoint.
- DnsOptions
Specification Describes the DNS options for an endpoint.
- DnsServers
Options Modify Structure Information about the DNS server to be used.
- EbsBlock
Device Describes a block device for an EBS volume.
- EbsBlock
Device Response Describes a block device for an EBS volume.
- EbsInfo
Describes the Amazon EBS features supported by the instance type.
- EbsInstance
Block Device Describes a parameter used to set up an EBS volume in a block device mapping.
- EbsInstance
Block Device Specification Describes information used to set up an EBS volume specified in a block device mapping.
- EbsOptimized
Info Describes the optimized EBS performance for supported instance types.
- EbsStatus
Details Describes the attached EBS status check for an instance.
- EbsStatus
Summary Provides a summary of the attached EBS volume status for an instance.
- Ec2Instance
Connect Endpoint The EC2 Instance Connect Endpoint.
- EfaInfo
Describes the Elastic Fabric Adapters for the instance type.
- Egress
Only Internet Gateway Describes an egress-only internet gateway.
- Elastic
GpuAssociation Amazon Elastic Graphics reached end of life on January 8, 2024.
Describes the association between an instance and an Elastic Graphics accelerator.
- Elastic
GpuHealth Amazon Elastic Graphics reached end of life on January 8, 2024.
Describes the status of an Elastic Graphics accelerator.
- Elastic
GpuSpecification Amazon Elastic Graphics reached end of life on January 8, 2024.
A specification for an Elastic Graphics accelerator.
- Elastic
GpuSpecification Response Deprecated.
Amazon Elastic Graphics reached end of life on January 8, 2024.
- Elastic
Gpus Amazon Elastic Graphics reached end of life on January 8, 2024.
Describes an Elastic Graphics accelerator.
- Elastic
Inference Accelerator Amazon Elastic Inference is no longer available.
Describes an elastic inference accelerator.
- Elastic
Inference Accelerator Association Amazon Elastic Inference is no longer available.
Describes the association between an instance and an elastic inference accelerator.
- EnaSrd
Specification ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the maximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. With ENA Express, you can communicate between two EC2 instances in the same subnet within the same account, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
To improve the reliability of network packet delivery, ENA Express reorders network packets on the receiving end by default. However, some UDP-based applications are designed to handle network packets that are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express is enabled, you can specify whether UDP network traffic uses it.
- EnaSrd
Specification Request Launch instances with ENA Express settings configured from your launch template.
- EnaSrd
UdpSpecification ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic automatically uses it. However, some UDP-based applications are designed to handle network packets that are out of order, without a need for retransmission, such as live video broadcasting or other near-real-time applications. For UDP traffic, you can specify whether to use ENA Express, based on your application environment needs.
- EnaSrd
UdpSpecification Request Configures ENA Express for UDP network traffic from your launch template.
- Enable
Fast Snapshot Restore Error Item Contains information about the errors that occurred when enabling fast snapshot restores.
- Enable
Fast Snapshot Restore State Error Describes an error that occurred when enabling fast snapshot restores.
- Enable
Fast Snapshot Restore State Error Item Contains information about an error that occurred when enabling fast snapshot restores.
- Enable
Fast Snapshot Restore Success Item Describes fast snapshot restores that were successfully enabled.
- Enclave
Options Indicates whether the instance is enabled for Amazon Web Services Nitro Enclaves.
- Enclave
Options Request Indicates whether the instance is enabled for Amazon Web Services Nitro Enclaves. For more information, see What is Amazon Web Services Nitro Enclaves? in the Amazon Web Services Nitro Enclaves User Guide.
- Event
Information Describes an EC2 Fleet or Spot Fleet event.
- Explanation
Describes an explanation code for an unreachable path. For more information, see Reachability Analyzer explanation codes.
- Export
Image Task Describes an export image task.
- Export
Task Describes an export instance task.
- Export
Task S3Location Describes the destination for an export image task.
- Export
Task S3Location Request Describes the destination for an export image task.
- Export
ToS3 Task Describes the format and location for the export task.
- Export
ToS3 Task Specification Describes an export instance task.
- Failed
Capacity Reservation Fleet Cancellation Result Describes a Capacity Reservation Fleet that could not be cancelled.
- Failed
Queued Purchase Deletion Describes a Reserved Instance whose queued purchase was not deleted.
- Fast
Launch Launch Template Specification Request Request to create a launch template for a Windows fast launch enabled AMI.
Note - You can specify either the
LaunchTemplateName
or theLaunchTemplateId
, but not both.- Fast
Launch Launch Template Specification Response Identifies the launch template that the AMI uses for Windows fast launch.
- Fast
Launch Snapshot Configuration Request Configuration settings for creating and managing pre-provisioned snapshots for a Windows fast launch enabled AMI.
- Fast
Launch Snapshot Configuration Response Configuration settings for creating and managing pre-provisioned snapshots for a Windows fast launch enabled Windows AMI.
- Federated
Authentication Describes the IAM SAML identity providers used for federated authentication.
- Federated
Authentication Request The IAM SAML identity provider used for federated authentication.
- Filter
A filter name and value pair that is used to return a more specific list of results from a describe operation. Filters can be used to match a set of resources by specific criteria, such as tags, attributes, or IDs.
If you specify multiple filters, the filters are joined with an
AND
, and the request returns only results that match all of the specified filters.For more information, see List and filter using the CLI and API in the Amazon EC2 User Guide.
- Filter
Port Range Describes a port range.
- Firewall
Stateful Rule Describes a stateful rule.
- Firewall
Stateless Rule Describes a stateless rule.
- Fleet
Block Device Mapping Request Describes a block device mapping, which defines the EBS volumes and instance store volumes to attach to an instance at launch.
To override a block device mapping specified in the launch template:
-
Specify the exact same
DeviceName
here as specified in the launch template. -
Only specify the parameters you want to change.
-
Any parameters you don't specify here will keep their original launch template values.
To add a new block device mapping:
-
Specify a
DeviceName
that doesn't exist in the launch template. -
Specify all desired parameters here.
-
- Fleet
Capacity Reservation Information about a Capacity Reservation in a Capacity Reservation Fleet.
- Fleet
Data Describes an EC2 Fleet.
- Fleet
EbsBlock Device Request Describes a block device for an EBS volume.
- Fleet
Launch Template Config Describes a launch template and overrides.
- Fleet
Launch Template Config Request Describes a launch template and overrides.
- Fleet
Launch Template Overrides Describes overrides for a launch template.
- Fleet
Launch Template Overrides Request Describes overrides for a launch template.
- Fleet
Launch Template Specification The Amazon EC2 launch template that can be used by a Spot Fleet to configure Amazon EC2 instances. You must specify either the ID or name of the launch template in the request, but not both.
For information about launch templates, see Launch an instance from a launch template in the Amazon EC2 User Guide.
- Fleet
Launch Template Specification Request The Amazon EC2 launch template that can be used by an EC2 Fleet to configure Amazon EC2 instances. You must specify either the ID or name of the launch template in the request, but not both.
For information about launch templates, see Launch an instance from a launch template in the Amazon EC2 User Guide.
- Fleet
Spot Capacity Rebalance The strategy to use when Amazon EC2 emits a signal that your Spot Instance is at an elevated risk of being interrupted.
- Fleet
Spot Capacity Rebalance Request The Spot Instance replacement strategy to use when Amazon EC2 emits a rebalance notification signal that your Spot Instance is at an elevated risk of being interrupted. For more information, see Capacity rebalancing in the Amazon EC2 User Guide.
- Fleet
Spot Maintenance Strategies The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
- Fleet
Spot Maintenance Strategies Request The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
- FlowLog
Describes a flow log.
- Fpga
Device Info Describes the FPGA accelerator for the instance type.
- Fpga
Device Memory Info Describes the memory for the FPGA accelerator for the instance type.
- Fpga
Image Describes an Amazon FPGA image (AFI).
- Fpga
Image Attribute Describes an Amazon FPGA image (AFI) attribute.
- Fpga
Image State Describes the state of the bitstream generation process for an Amazon FPGA image (AFI).
- Fpga
Info Describes the FPGAs for the instance type.
- GpuDevice
Info Describes the GPU accelerators for the instance type.
- GpuDevice
Memory Info Describes the memory available to the GPU accelerator.
- GpuInfo
Describes the GPU accelerators for the instance type.
- Group
Identifier Describes a security group.
- Hibernation
Options Indicates whether your instance is configured for hibernation. This parameter is valid only if the instance meets the hibernation prerequisites. For more information, see Hibernate your Amazon EC2 instance in the Amazon EC2 User Guide.
- Hibernation
Options Request Indicates whether your instance is configured for hibernation. This parameter is valid only if the instance meets the hibernation prerequisites. For more information, see Hibernate your Amazon EC2 instance in the Amazon EC2 User Guide.
- History
Record Describes an event in the history of the Spot Fleet request.
- History
Record Entry Describes an event in the history of an EC2 Fleet.
- Host
Describes the properties of the Dedicated Host.
- Host
Instance Describes an instance running on a Dedicated Host.
- Host
Offering Details about the Dedicated Host Reservation offering.
- Host
Properties Describes the properties of a Dedicated Host.
- Host
Reservation Details about the Dedicated Host Reservation and associated Dedicated Hosts.
- IamInstance
Profile Describes an IAM instance profile.
- IamInstance
Profile Association Describes an association between an IAM instance profile and an instance.
- IamInstance
Profile Specification Describes an IAM instance profile.
- Icmp
Type Code Describes the ICMP type and code.
- IdFormat
Describes the ID format for a resource.
- IkeVersions
List Value The internet key exchange (IKE) version permitted for the VPN tunnel.
- IkeVersions
Request List Value The IKE version that is permitted for the VPN tunnel.
- Image
Describes an image.
- Image
Criterion The list of criteria that are evaluated to determine whch AMIs are discoverable and usable in the account in the specified Amazon Web Services Region. Currently, the only criteria that can be specified are AMI providers.
Up to 10
imageCriteria
objects can be specified, and up to a total of 200 values for allimageProviders
. For more information, see JSON configuration for the Allowed AMIs criteria in the Amazon EC2 User Guide.- Image
Criterion Request The list of criteria that are evaluated to determine whch AMIs are discoverable and usable in the account in the specified Amazon Web Services Region. Currently, the only criteria that can be specified are AMI providers.
Up to 10
imageCriteria
objects can be specified, and up to a total of 200 values for allimageProviders
. For more information, see JSON configuration for the Allowed AMIs criteria in the Amazon EC2 User Guide.- Image
Disk Container Describes the disk container object for an import image task.
- Image
Metadata Information about the AMI.
- Image
Recycle BinInfo Information about an AMI that is currently in the Recycle Bin.
- Import
Image License Configuration Request The request information of license configurations.
- Import
Image License Configuration Response The response information for license configurations.
- Import
Image Task Describes an import image task.
- Import
Instance Launch Specification Describes the launch specification for VM import.
- Import
Instance Task Details Describes an import instance task.
- Import
Instance Volume Detail Item Describes an import volume task.
- Import
Snapshot Task Describes an import snapshot task.
- Import
Volume Task Details Describes an import volume task.
- Inference
Accelerator Info Amazon Elastic Inference is no longer available.
Describes the Inference accelerators for the instance type.
- Inference
Device Info Amazon Elastic Inference is no longer available.
Describes the Inference accelerators for the instance type.
- Inference
Device Memory Info Amazon Elastic Inference is no longer available.
Describes the memory available to the inference accelerator.
- Instance
Describes an instance.
- Instance
Attachment EnaSrd Specification ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the maximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. With ENA Express, you can communicate between two EC2 instances in the same subnet within the same account, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
To improve the reliability of network packet delivery, ENA Express reorders network packets on the receiving end by default. However, some UDP-based applications are designed to handle network packets that are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express is enabled, you can specify whether UDP network traffic uses it.
- Instance
Attachment EnaSrd UdpSpecification ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic automatically uses it. However, some UDP-based applications are designed to handle network packets that are out of order, without a need for retransmission, such as live video broadcasting or other near-real-time applications. For UDP traffic, you can specify whether to use ENA Express, based on your application environment needs.
- Instance
Block Device Mapping Describes a block device mapping.
- Instance
Block Device Mapping Specification Describes a block device mapping entry.
- Instance
Capacity Information about the number of instances that can be launched onto the Dedicated Host.
- Instance
Count Describes a Reserved Instance listing state.
- Instance
Credit Specification Describes the credit option for CPU usage of a burstable performance instance.
- Instance
Credit Specification Request Describes the credit option for CPU usage of a burstable performance instance.
- Instance
Event Window The event window.
- Instance
Event Window Association Request One or more targets associated with the specified event window. Only one type of target (instance ID, instance tag, or Dedicated Host ID) can be associated with an event window.
- Instance
Event Window Association Target One or more targets associated with the event window.
- Instance
Event Window Disassociation Request The targets to disassociate from the specified event window.
- Instance
Event Window State Change The state of the event window.
- Instance
Event Window Time Range The start day and time and the end day and time of the time range, in UTC.
- Instance
Event Window Time Range Request The start day and time and the end day and time of the time range, in UTC.
- Instance
Export Details Describes an instance to export.
- Instance
Family Credit Specification Describes the default credit option for CPU usage of a burstable performance instance family.
- Instance
Image Metadata Information about the instance and the AMI used to launch the instance.
- Instance
Ipv4 Prefix Information about an IPv4 prefix.
- Instance
Ipv6 Address Describes an IPv6 address.
- Instance
Ipv6 Address Request Describes an IPv6 address.
- Instance
Ipv6 Prefix Information about an IPv6 prefix.
- Instance
Maintenance Options The maintenance options for the instance.
- Instance
Maintenance Options Request The maintenance options for the instance.
- Instance
Market Options Request Describes the market (purchasing) option for the instances.
- Instance
Metadata Defaults Response The default instance metadata service (IMDS) settings that were set at the account level in the specified Amazon Web Services Region.
- Instance
Metadata Options Request The metadata options for the instance.
- Instance
Metadata Options Response The metadata options for the instance.
- Instance
Monitoring Describes the monitoring of an instance.
- Instance
Network Interface Describes a network interface.
- Instance
Network Interface Association Describes association information for an Elastic IP address (IPv4).
- Instance
Network Interface Attachment Describes a network interface attachment.
- Instance
Network Interface Specification Describes a network interface.
- Instance
Network Performance Options With network performance options, you can adjust your bandwidth preferences to meet the needs of the workload that runs on your instance.
- Instance
Network Performance Options Request Configure network performance options for your instance that are geared towards performance improvements based on the workload that it runs.
- Instance
Private IpAddress Describes a private IPv4 address.
- Instance
Requirements The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with these attributes.
You must specify
VCpuCount
andMemoryMiB
. All other attributes are optional. Any unspecified optional attribute is set to its default.When you specify multiple attributes, you get instance types that satisfy all of the specified attributes. If you specify multiple values for an attribute, you get instance types that satisfy any of the specified values.
To limit the list of instance types from which Amazon EC2 can identify matching instance types, you can use one of the following parameters, but not both in the same request:
-
AllowedInstanceTypes
- The instance types to include in the list. All other instance types are ignored, even if they match your specified attributes. -
ExcludedInstanceTypes
- The instance types to exclude from the list, even if they match your specified attributes.
If you specify
InstanceRequirements
, you can't specifyInstanceType
.Attribute-based instance type selection is only supported when using Auto Scaling groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in the launch instance wizard or with the RunInstances API, you can't specify
InstanceRequirements
.For more information, see Create mixed instances group using attribute-based instance type selection in the Amazon EC2 Auto Scaling User Guide, and also Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot placement score in the Amazon EC2 User Guide.
-
- Instance
Requirements Request The attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with these attributes.
You must specify
VCpuCount
andMemoryMiB
. All other attributes are optional. Any unspecified optional attribute is set to its default.When you specify multiple attributes, you get instance types that satisfy all of the specified attributes. If you specify multiple values for an attribute, you get instance types that satisfy any of the specified values.
To limit the list of instance types from which Amazon EC2 can identify matching instance types, you can use one of the following parameters, but not both in the same request:
-
AllowedInstanceTypes
- The instance types to include in the list. All other instance types are ignored, even if they match your specified attributes. -
ExcludedInstanceTypes
- The instance types to exclude from the list, even if they match your specified attributes.
If you specify
InstanceRequirements
, you can't specifyInstanceType
.Attribute-based instance type selection is only supported when using Auto Scaling groups, EC2 Fleet, and Spot Fleet to launch instances. If you plan to use the launch template in the launch instance wizard, or with the RunInstances API or AWS::EC2::Instance Amazon Web Services CloudFormation resource, you can't specify
InstanceRequirements
.For more information, see Specify attributes for instance type selection for EC2 Fleet or Spot Fleet and Spot placement score in the Amazon EC2 User Guide.
-
- Instance
Requirements With Metadata Request The architecture type, virtualization type, and other attributes for the instance types. When you specify instance attributes, Amazon EC2 will identify instance types with those attributes.
If you specify
InstanceRequirementsWithMetadataRequest
, you can't specifyInstanceTypes
.- Instance
Specification The instance details to specify which volumes should be snapshotted.
- Instance
State Describes the current state of an instance.
- Instance
State Change Describes an instance state change.
- Instance
Status Describes the status of an instance.
- Instance
Status Details Describes the instance status.
- Instance
Status Event Describes a scheduled event for an instance.
- Instance
Status Summary Describes the status of an instance.
- Instance
Storage Info Describes the instance store features that are supported by the instance type.
- Instance
TagNotification Attribute Describes the registered tag keys for the current Region.
- Instance
Topology Information about the instance topology.
- Instance
Type Info Describes the instance type.
- Instance
Type Info From Instance Requirements The list of instance types with the specified instance attributes.
- Instance
Type Offering The instance types offered.
- Instance
Usage Information about the Capacity Reservation usage.
- Integrate
Services Describes service integrations with VPC Flow logs.
- Internet
Gateway Describes an internet gateway.
- Internet
Gateway Attachment Describes the attachment of a VPC to an internet gateway or an egress-only internet gateway.
- IpPermission
Describes the permissions for a security group rule.
- IpRange
Describes an IPv4 address range.
- Ipam
IPAM is a VPC feature that you can use to automate your IP address management workflows including assigning, tracking, troubleshooting, and auditing IP addresses across Amazon Web Services Regions and accounts throughout your Amazon Web Services Organization. For more information, see What is IPAM? in the Amazon VPC IPAM User Guide.
- Ipam
Address History Record The historical record of a CIDR within an IPAM scope. For more information, see View the history of IP addresses in the Amazon VPC IPAM User Guide.
- Ipam
Cidr Authorization Context A signed document that proves that you are authorized to bring the specified IP address range to Amazon using BYOIP.
- Ipam
Discovered Account An IPAM discovered account. A discovered account is an Amazon Web Services account that is monitored under a resource discovery. If you have integrated IPAM with Amazon Web Services Organizations, all accounts in the organization are discovered accounts.
- Ipam
Discovered Public Address A public IP Address discovered by IPAM.
- Ipam
Discovered Resource Cidr An IPAM discovered resource CIDR. A discovered resource is a resource CIDR monitored under a resource discovery. The following resources can be discovered: VPCs, Public IPv4 pools, VPC subnets, and Elastic IP addresses. The discovered resource CIDR is the IP address range in CIDR notation that is associated with the resource.
- Ipam
Discovery Failure Reason The discovery failure reason.
- Ipam
External Resource Verification Token A verification token is an Amazon Web Services-generated random value that you can use to prove ownership of an external resource. For example, you can use a verification token to validate that you control a public IP address range when you bring an IP address range to Amazon Web Services (BYOIP).
- Ipam
Operating Region The operating Regions for an IPAM. Operating Regions are Amazon Web Services Regions where the IPAM is allowed to manage IP address CIDRs. IPAM only discovers and monitors resources in the Amazon Web Services Regions you select as operating Regions.
For more information about operating Regions, see Create an IPAM in the Amazon VPC IPAM User Guide.
- Ipam
Organizational Unit Exclusion If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion.
- Ipam
Pool In IPAM, a pool is a collection of contiguous IP addresses CIDRs. Pools enable you to organize your IP addresses according to your routing and security needs. For example, if you have separate routing and security needs for development and production applications, you can create a pool for each.
- Ipam
Pool Allocation In IPAM, an allocation is a CIDR assignment from an IPAM pool to another IPAM pool or to a resource.
- Ipam
Pool Cidr A CIDR provisioned to an IPAM pool.
- Ipam
Pool Cidr Failure Reason Details related to why an IPAM pool CIDR failed to be provisioned.
- Ipam
Pool Source Resource The resource used to provision CIDRs to a resource planning pool.
- Ipam
Pool Source Resource Request The resource used to provision CIDRs to a resource planning pool.
- Ipam
Public Address Security Group The security group that the resource with the public IP address is in.
- Ipam
Public Address Tag A tag for a public IP address discovered by IPAM.
- Ipam
Public Address Tags Tags for a public IP address discovered by IPAM.
- Ipam
Resource Cidr The CIDR for an IPAM resource.
- Ipam
Resource Discovery A resource discovery is an IPAM component that enables IPAM to manage and monitor resources that belong to the owning account.
- Ipam
Resource Discovery Association An IPAM resource discovery association. An associated resource discovery is a resource discovery that has been associated with an IPAM. IPAM aggregates the resource CIDRs discovered by the associated resource discovery.
- Ipam
Resource Tag The key/value combination of a tag assigned to the resource. Use the tag key in the filter name and the tag value as the filter value. For example, to find all resources that have a tag with the key
Owner
and the valueTeamA
, specifytag:Owner
for the filter name andTeamA
for the filter value.- Ipam
Scope In IPAM, a scope is the highest-level container within IPAM. An IPAM contains two default scopes. Each scope represents the IP space for a single network. The private scope is intended for all private IP address space. The public scope is intended for all public IP address space. Scopes enable you to reuse IP addresses across multiple unconnected networks without causing IP address overlap or conflict.
For more information, see How IPAM works in the Amazon VPC IPAM User Guide.
- Ipv4
Prefix Specification Describes an IPv4 prefix.
- Ipv4
Prefix Specification Request Describes the IPv4 prefix option for a network interface.
- Ipv4
Prefix Specification Response Information about the IPv4 delegated prefixes assigned to a network interface.
- Ipv6
Cidr Association Describes an IPv6 CIDR block association.
- Ipv6
Cidr Block Describes an IPv6 CIDR block.
- Ipv6
Pool Describes an IPv6 address pool.
- Ipv6
Prefix Specification Describes the IPv6 prefix.
- Ipv6
Prefix Specification Request Describes the IPv6 prefix option for a network interface.
- Ipv6
Prefix Specification Response Information about the IPv6 delegated prefixes assigned to a network interface.
- Ipv6
Range Describes an IPv6 address range.
- KeyPair
Info Describes a key pair.
- Last
Error The last error that occurred for a VPC endpoint.
- Launch
Permission Describes a launch permission.
- Launch
Permission Modifications Describes a launch permission modification.
- Launch
Specification Describes the launch specification for an instance.
- Launch
Template Describes a launch template.
- Launch
Template AndOverrides Response Describes a launch template and overrides.
- Launch
Template Block Device Mapping Describes a block device mapping.
- Launch
Template Block Device Mapping Request Describes a block device mapping.
- Launch
Template Capacity Reservation Specification Request Describes an instance's Capacity Reservation targeting option. You can specify only one option at a time. Use the
CapacityReservationPreference
parameter to configure the instance to run in On-Demand capacity or to run in anyopen
Capacity Reservation that has matching attributes (instance type, platform, Availability Zone). Use theCapacityReservationTarget
parameter to explicitly target a specific Capacity Reservation or a Capacity Reservation group.- Launch
Template Capacity Reservation Specification Response Information about the Capacity Reservation targeting option.
- Launch
Template Config Describes a launch template and overrides.
- Launch
Template CpuOptions The CPU options for the instance.
- Launch
Template CpuOptions Request The CPU options for the instance. Both the core count and threads per core must be specified in the request.
- Launch
Template EbsBlock Device Describes a block device for an EBS volume.
- Launch
Template EbsBlock Device Request The parameters for a block device for an EBS volume.
- Launch
Template Elastic Inference Accelerator Amazon Elastic Inference is no longer available.
Describes an elastic inference accelerator.
- Launch
Template Elastic Inference Accelerator Response Amazon Elastic Inference is no longer available.
Describes an elastic inference accelerator.
- Launch
Template EnaSrd Specification ENA Express uses Amazon Web Services Scalable Reliable Datagram (SRD) technology to increase the maximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. With ENA Express, you can communicate between two EC2 instances in the same subnet within the same account, or in different accounts. Both sending and receiving instances must have ENA Express enabled.
To improve the reliability of network packet delivery, ENA Express reorders network packets on the receiving end by default. However, some UDP-based applications are designed to handle network packets that are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express is enabled, you can specify whether UDP network traffic uses it.
- Launch
Template EnaSrd UdpSpecification ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic automatically uses it. However, some UDP-based applications are designed to handle network packets that are out of order, without a need for retransmission, such as live video broadcasting or other near-real-time applications. For UDP traffic, you can specify whether to use ENA Express, based on your application environment needs.
- Launch
Template Enclave Options Indicates whether the instance is enabled for Amazon Web Services Nitro Enclaves.
- Launch
Template Enclave Options Request Indicates whether the instance is enabled for Amazon Web Services Nitro Enclaves. For more information, see What is Nitro Enclaves? in the Amazon Web Services Nitro Enclaves User Guide.
- Launch
Template Hibernation Options Indicates whether an instance is configured for hibernation.
- Launch
Template Hibernation Options Request Indicates whether the instance is configured for hibernation. This parameter is valid only if the instance meets the hibernation prerequisites.
- Launch
Template IamInstance Profile Specification Describes an IAM instance profile.
- Launch
Template IamInstance Profile Specification Request An IAM instance profile.
- Launch
Template Instance Maintenance Options The maintenance options of your instance.
- Launch
Template Instance Maintenance Options Request The maintenance options of your instance.
- Launch
Template Instance Market Options The market (purchasing) option for the instances.
- Launch
Template Instance Market Options Request The market (purchasing) option for the instances.
- Launch
Template Instance Metadata Options The metadata options for the instance. For more information, see Use instance metadata to manage your EC2 instance in the Amazon EC2 User Guide.
- Launch
Template Instance Metadata Options Request The metadata options for the instance. For more information, see Use instance metadata to manage your EC2 instance in the Amazon EC2 User Guide.
- Launch
Template Instance Network Interface Specification Describes a network interface.
- Launch
Template Instance Network Interface Specification Request The parameters for a network interface.
- Launch
Template License Configuration Describes a license configuration.
- Launch
Template License Configuration Request Describes a license configuration.
- Launch
Template Network Performance Options With network performance options, you can adjust your bandwidth preferences to meet the needs of the workload that runs on your instance at launch.
- Launch
Template Network Performance Options Request When you configure network performance options in your launch template, your instance is geared for performance improvements based on the workload that it runs as soon as it's available.
- Launch
Template Overrides Describes overrides for a launch template.
- Launch
Template Placement Describes the placement of an instance.
- Launch
Template Placement Request Describes the placement of an instance.
- Launch
Template Private DnsName Options Describes the options for instance hostnames.
- Launch
Template Private DnsName Options Request Describes the options for instance hostnames.
- Launch
Template Specification Describes the launch template to use.
- Launch
Template Spot Market Options The options for Spot Instances.
- Launch
Template Spot Market Options Request The options for Spot Instances.
- Launch
Template TagSpecification The tags specification for the launch template.
- Launch
Template TagSpecification Request The tags specification for the resources that are created during instance launch.
- Launch
Template Version Describes a launch template version.
- Launch
Templates Monitoring Describes the monitoring for the instance.
- Launch
Templates Monitoring Request Describes the monitoring for the instance.
- License
Configuration Describes a license configuration.
- License
Configuration Request Describes a license configuration.
- Load
Balancers Config Describes the Classic Load Balancers and target groups to attach to a Spot Fleet request.
- Load
Permission Describes a load permission.
- Load
Permission Modifications Describes modifications to the load permissions of an Amazon FPGA image (AFI).
- Load
Permission Request Describes a load permission.
- Local
Gateway Describes a local gateway.
- Local
Gateway Route Describes a route for a local gateway route table.
- Local
Gateway Route Table Describes a local gateway route table.
- Local
Gateway Route Table Virtual Interface Group Association Describes an association between a local gateway route table and a virtual interface group.
- Local
Gateway Route Table VpcAssociation Describes an association between a local gateway route table and a VPC.
- Local
Gateway Virtual Interface Describes a local gateway virtual interface.
- Local
Gateway Virtual Interface Group Describes a local gateway virtual interface group.
- Locked
Snapshots Info Information about a locked snapshot.
- MacHost
Information about the EC2 Mac Dedicated Host.
- MacModification
Task Information about a System Integrity Protection (SIP) modification task or volume ownership delegation task for an Amazon EC2 Mac instance.
- MacSystem
Integrity Protection Configuration Describes the configuration for a System Integrity Protection (SIP) modification task.
- MacSystem
Integrity Protection Configuration Request Describes a custom configuration for a System Integrity Protection (SIP) modification task.
- Maintenance
Details Details for Site-to-Site VPN tunnel endpoint maintenance events.
- Managed
Prefix List Describes a managed prefix list.
- Media
Accelerator Info Describes the media accelerators for the instance type.
- Media
Device Info Describes the media accelerators for the instance type.
- Media
Device Memory Info Describes the memory available to the media accelerator.
- Memory
GiBPerV Cpu The minimum and maximum amount of memory per vCPU, in GiB.
- Memory
GiBPerV CpuRequest The minimum and maximum amount of memory per vCPU, in GiB.
- Memory
Info Describes the memory for the instance type.
- Memory
MiB The minimum and maximum amount of memory, in MiB.
- Memory
MiBRequest The minimum and maximum amount of memory, in MiB.
- Metric
Point Indicates whether the network was healthy or degraded at a particular point. The value is aggregated from the
startDate
to theendDate
. Currently onlyfive_minutes
is supported.- Modify
Transit Gateway Options The transit gateway options.
- Modify
Transit Gateway VpcAttachment Request Options Describes the options for a VPC attachment.
- Modify
Verified Access Endpoint Cidr Options The CIDR options for a Verified Access endpoint.
- Modify
Verified Access Endpoint EniOptions Describes the options when modifying a Verified Access endpoint with the
network-interface
type.- Modify
Verified Access Endpoint Load Balancer Options Describes a load balancer when creating an Amazon Web Services Verified Access endpoint using the
load-balancer
type.- Modify
Verified Access Endpoint Port Range Describes the port range for a Verified Access endpoint.
- Modify
Verified Access Endpoint RdsOptions The RDS options for a Verified Access endpoint.
- Modify
Verified Access Native Application Oidc Options Describes the OpenID Connect (OIDC) options.
- Modify
Verified Access Trust Provider Device Options Modifies the configuration of the specified device-based Amazon Web Services Verified Access trust provider.
- Modify
Verified Access Trust Provider Oidc Options Options for an OpenID Connect-compatible user-identity trust provider.
- Modify
VpnTunnel Options Specification The Amazon Web Services Site-to-Site VPN tunnel options to modify.
- Monitoring
Describes the monitoring of an instance.
- Moving
Address Status This action is deprecated.
Describes the status of a moving Elastic IP address.
- NatGateway
Describes a NAT gateway.
- NatGateway
Address Describes the IP addresses and network interface associated with a NAT gateway.
- Native
Application Oidc Options Describes the OpenID Connect (OIDC) options.
- Network
Acl Describes a network ACL.
- Network
AclAssociation Describes an association between a network ACL and a subnet.
- Network
AclEntry Describes an entry in a network ACL.
- Network
Bandwidth Gbps The minimum and maximum amount of network bandwidth, in gigabits per second (Gbps).
Setting the minimum bandwidth does not guarantee that your instance will achieve the minimum bandwidth. Amazon EC2 will identify instance types that support the specified minimum bandwidth, but the actual bandwidth of your instance might go below the specified minimum at times. For more information, see Available instance bandwidth in the Amazon EC2 User Guide.
- Network
Bandwidth Gbps Request The minimum and maximum amount of network bandwidth, in gigabits per second (Gbps).
Setting the minimum bandwidth does not guarantee that your instance will achieve the minimum bandwidth. Amazon EC2 will identify instance types that support the specified minimum bandwidth, but the actual bandwidth of your instance might go below the specified minimum at times. For more information, see Available instance bandwidth in the Amazon EC2 User Guide.
- Network
Card Info Describes the network card support of the instance type.
- Network
Info Describes the networking features of the instance type.
- Network
Insights Access Scope Describes a Network Access Scope.
- Network
Insights Access Scope Analysis Describes a Network Access Scope analysis.
- Network
Insights Access Scope Content Describes the Network Access Scope content.
- Network
Insights Analysis Describes a network insights analysis.
- Network
Insights Path Describes a path.
- Network
Interface Describes a network interface.
- Network
Interface Association Describes association information for an Elastic IP address (IPv4 only), or a Carrier IP address (for a network interface which resides in a subnet in a Wavelength Zone).
- Network
Interface Attachment Describes a network interface attachment.
- Network
Interface Attachment Changes Describes an attachment change.
- Network
Interface Count The minimum and maximum number of network interfaces.
- Network
Interface Count Request The minimum and maximum number of network interfaces.
- Network
Interface Ipv6 Address Describes an IPv6 address associated with a network interface.
- Network
Interface Permission Describes a permission for a network interface.
- Network
Interface Permission State Describes the state of a network interface permission.
- Network
Interface Private IpAddress Describes the private IPv4 address of a network interface.
- Neuron
Device Core Info Describes the cores available to the neuron accelerator.
- Neuron
Device Info Describes the neuron accelerators for the instance type.
- Neuron
Device Memory Info Describes the memory available to the neuron accelerator.
- Neuron
Info Describes the neuron accelerators for the instance type.
- NewDhcp
Configuration Describes a DHCP configuration option.
- Nitro
TpmInfo Describes the supported NitroTPM versions for the instance type.
- Oidc
Options Describes the options for an OpenID Connect-compatible user-identity trust provider.
- OnDemand
Options Describes the configuration of On-Demand Instances in an EC2 Fleet.
- OnDemand
Options Request Describes the configuration of On-Demand Instances in an EC2 Fleet.
- Operator
Request The service provider that manages the resource.
- Operator
Response Describes whether the resource is managed by a service provider and, if so, describes the service provider that manages it.
- Outpost
Lag Describes an Outpost link aggregation group (LAG).
- Packet
Header Statement Describes a packet header statement.
- Packet
Header Statement Request Describes a packet header statement.
- Path
Component Describes a path component.
- Path
Filter Describes a set of filters for a path analysis. Use path filters to scope the analysis when there can be multiple resulting paths.
- Path
Request Filter Describes a set of filters for a path analysis. Use path filters to scope the analysis when there can be multiple resulting paths.
- Path
Statement Describes a path statement.
- Path
Statement Request Describes a path statement.
- PciId
Describes the data that identifies an Amazon FPGA image (AFI) on the PCI bus.
- Peering
Attachment Status The status of the transit gateway peering attachment.
- Peering
Connection Options Describes the VPC peering connection options.
- Peering
Connection Options Request The VPC peering connection options.
- Peering
TgwInfo Information about the transit gateway in the peering attachment.
- Performance
Factor Reference Specify an instance family to use as the baseline reference for CPU performance. All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture.
Currently, only one instance family can be specified in the list.
- Performance
Factor Reference Request Specify an instance family to use as the baseline reference for CPU performance. All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture.
Currently, only one instance family can be specified in the list.
- Phase1
DhGroup Numbers List Value The Diffie-Hellmann group number for phase 1 IKE negotiations.
- Phase1
DhGroup Numbers Request List Value Specifies a Diffie-Hellman group number for the VPN tunnel for phase 1 IKE negotiations.
- Phase1
Encryption Algorithms List Value The encryption algorithm for phase 1 IKE negotiations.
- Phase1
Encryption Algorithms Request List Value Specifies the encryption algorithm for the VPN tunnel for phase 1 IKE negotiations.
- Phase1
Integrity Algorithms List Value The integrity algorithm for phase 1 IKE negotiations.
- Phase1
Integrity Algorithms Request List Value Specifies the integrity algorithm for the VPN tunnel for phase 1 IKE negotiations.
- Phase2
DhGroup Numbers List Value The Diffie-Hellmann group number for phase 2 IKE negotiations.
- Phase2
DhGroup Numbers Request List Value Specifies a Diffie-Hellman group number for the VPN tunnel for phase 2 IKE negotiations.
- Phase2
Encryption Algorithms List Value The encryption algorithm for phase 2 IKE negotiations.
- Phase2
Encryption Algorithms Request List Value Specifies the encryption algorithm for the VPN tunnel for phase 2 IKE negotiations.
- Phase2
Integrity Algorithms List Value The integrity algorithm for phase 2 IKE negotiations.
- Phase2
Integrity Algorithms Request List Value Specifies the integrity algorithm for the VPN tunnel for phase 2 IKE negotiations.
- Placement
Describes the placement of an instance.
- Placement
Group Describes a placement group.
- Placement
Group Info Describes the placement group support of the instance type.
- Placement
Response Describes the placement of an instance.
- Pool
Cidr Block Describes a CIDR block for an address pool.
- Port
Range Describes a range of ports.
- Prefix
List Describes prefixes for Amazon Web Services services.
- Prefix
List Association Describes the resource with which a prefix list is associated.
- Prefix
List Entry Describes a prefix list entry.
- Prefix
List Id Describes a prefix list ID.
- Price
Schedule Describes the price for a Reserved Instance.
- Price
Schedule Specification Describes the price for a Reserved Instance.
- Pricing
Detail Describes a Reserved Instance offering.
- Principal
IdFormat PrincipalIdFormat description
- Private
DnsDetails Information about the Private DNS name for interface endpoints.
- Private
DnsName Configuration Information about the private DNS name for the service endpoint.
- Private
DnsName Options OnLaunch Describes the options for instance hostnames.
- Private
DnsName Options Request Describes the options for instance hostnames.
- Private
DnsName Options Response Describes the options for instance hostnames.
- Private
IpAddress Specification Describes a secondary private IPv4 address for a network interface.
- Processor
Info Describes the processor used by the instance type.
- Product
Code Describes a product code.
- Propagating
Vgw Describes a virtual private gateway propagating route.
- Provisioned
Bandwidth Reserved. If you need to sustain traffic greater than the documented limits, contact Amazon Web Services Support.
- PtrUpdate
Status The status of an updated pointer (PTR) record for an Elastic IP address.
- Public
IpDns Name Options Public hostname type options. For more information, see EC2 instance hostnames, DNS names, and domains in the Amazon EC2 User Guide.
- Public
Ipv4 Pool Describes an IPv4 address pool.
- Public
Ipv4 Pool Range Describes an address range of an IPv4 address pool.
- Purchase
Describes the result of the purchase.
- Purchase
Request Describes a request to purchase Scheduled Instances.
- Recurring
Charge Describes a recurring charge.
- Referenced
Security Group Describes the security group that is referenced in the security group rule.
- Region
Describes a Region.
- Regional
Summary A summary report for the attribute for a Region.
- Register
Instance TagAttribute Request Information about the tag keys to register for the current Region. You can either specify individual tag keys or register all tag keys in the current Region. You must specify either
IncludeAllTagsOfInstance
orInstanceTagKeys
in the request- Remove
Ipam Operating Region Remove an operating Region from an IPAM. Operating Regions are Amazon Web Services Regions where the IPAM is allowed to manage IP address CIDRs. IPAM only discovers and monitors resources in the Amazon Web Services Regions you select as operating Regions.
For more information about operating Regions, see Create an IPAM in the Amazon VPC IPAM User Guide
- Remove
Ipam Organizational Unit Exclusion Remove an Organizational Unit (OU) exclusion to your IPAM. If your IPAM is integrated with Amazon Web Services Organizations and you add an organizational unit (OU) exclusion, IPAM will not manage the IP addresses in accounts in that OU exclusion. There is a limit on the number of exclusions you can create. For more information, see Quotas for your IPAM in the Amazon VPC IPAM User Guide.
- Remove
Prefix List Entry An entry for a prefix list.
- Replace
Root Volume Task Information about a root volume replacement task.
- Request
Filter Port Range Describes a port range.
- Request
Ipam Resource Tag A tag on an IPAM resource.
- Request
Launch Template Data The information to include in the launch template.
You must specify at least one parameter for the launch template data.
- Request
Spot Launch Specification Describes the launch specification for an instance.
- Reservation
Describes a launch request for one or more instances, and includes owner, requester, and security group information that applies to all instances in the launch request.
- Reservation
Fleet Instance Specification Information about an instance type to use in a Capacity Reservation Fleet.
- Reservation
Value The cost associated with the Reserved Instance.
- Reserved
Instance Limit Price Describes the limit price of a Reserved Instance offering.
- Reserved
Instance Reservation Value The total value of the Convertible Reserved Instance.
- Reserved
Instances Describes a Reserved Instance.
- Reserved
Instances Configuration Describes the configuration settings for the modified Reserved Instances.
- Reserved
Instances Id Describes the ID of a Reserved Instance.
- Reserved
Instances Listing Describes a Reserved Instance listing.
- Reserved
Instances Modification Describes a Reserved Instance modification.
- Reserved
Instances Modification Result Describes the modification request/s.
- Reserved
Instances Offering Describes a Reserved Instance offering.
- Resource
Statement Describes a resource statement.
- Resource
Statement Request Describes a resource statement.
- Response
Error Describes the error that's returned when you cannot delete a launch template version.
- Response
Launch Template Data The information for a launch template.
- Revoked
Security Group Rule A security group rule removed with RevokeSecurityGroupEgress or RevokeSecurityGroupIngress.
- Route
Describes a route in a route table.
- Route
Server Describes a route server and its configuration.
Amazon VPC Route Server simplifies routing for traffic between workloads that are deployed within a VPC and its internet gateways. With this feature, VPC Route Server dynamically updates VPC and internet gateway route tables with your preferred IPv4 or IPv6 routes to achieve routing fault tolerance for those workloads. This enables you to automatically reroute traffic within a VPC, which increases the manageability of VPC routing and interoperability with third-party workloads.
Route server supports the follow route table types:
-
VPC route tables not associated with subnets
-
Subnet route tables
-
Internet gateway route tables
Route server does not support route tables associated with virtual private gateways. To propagate routes into a transit gateway route table, use Transit Gateway Connect.
-
- Route
Server Association Describes the association between a route server and a VPC.
A route server association is the connection established between a route server and a VPC.
- Route
Server BfdStatus The current status of Bidirectional Forwarding Detection (BFD) for a BGP session.
- Route
Server BgpOptions The BGP configuration options for a route server peer.
- Route
Server BgpOptions Request The BGP configuration options requested for a route server peer.
- Route
Server BgpStatus The current status of a BGP session.
- Route
Server Endpoint Describes a route server endpoint and its properties.
A route server endpoint is an Amazon Web Services-managed component inside a subnet that facilitates BGP (Border Gateway Protocol) connections between your route server and your BGP peers.
- Route
Server Peer Describes a BGP peer configuration for a route server endpoint.
A route server peer is a session between a route server endpoint and the device deployed in Amazon Web Services (such as a firewall appliance or other network security function running on an EC2 instance). The device must meet these requirements:
-
Have an elastic network interface in the VPC
-
Support BGP (Border Gateway Protocol)
-
Can initiate BGP sessions
-
- Route
Server Propagation Describes the route propagation configuration between a route server and a route table.
When enabled, route server propagation installs the routes in the FIB on the route table you've specified. Route server supports IPv4 and IPv6 route propagation.
- Route
Server Route Describes a route in the route server's routing database.
- Route
Server Route Installation Detail Describes the installation status of a route in a route table.
- Route
Table Describes a route table.
- Route
Table Association Describes an association between a route table and a subnet or gateway.
- Route
Table Association State Describes the state of an association between a route table and a subnet or gateway.
- Rule
Group Rule Options Pair Describes the rule options for a stateful rule group.
- Rule
Group Type Pair Describes the type of a stateful rule group.
- Rule
Option Describes additional settings for a stateful rule.
- RunInstances
Monitoring Enabled Describes the monitoring of an instance.
- S3Object
Tag The tags to apply to the AMI object that will be stored in the Amazon S3 bucket. For more information, see Categorizing your storage using tags in the Amazon Simple Storage Service User Guide.
- S3Storage
Describes the storage parameters for Amazon S3 and Amazon S3 buckets for an instance store-backed AMI.
- Scheduled
Instance Describes a Scheduled Instance.
- Scheduled
Instance Availability Describes a schedule that is available for your Scheduled Instances.
- Scheduled
Instance Recurrence Describes the recurring schedule for a Scheduled Instance.
- Scheduled
Instance Recurrence Request Describes the recurring schedule for a Scheduled Instance.
- Scheduled
Instances Block Device Mapping Describes a block device mapping for a Scheduled Instance.
- Scheduled
Instances Ebs Describes an EBS volume for a Scheduled Instance.
- Scheduled
Instances IamInstance Profile Describes an IAM instance profile for a Scheduled Instance.
- Scheduled
Instances Ipv6 Address Describes an IPv6 address.
- Scheduled
Instances Launch Specification Describes the launch specification for a Scheduled Instance.
If you are launching the Scheduled Instance in EC2-VPC, you must specify the ID of the subnet. You can specify the subnet using either
SubnetId
orNetworkInterface
.- Scheduled
Instances Monitoring Describes whether monitoring is enabled for a Scheduled Instance.
- Scheduled
Instances Network Interface Describes a network interface for a Scheduled Instance.
- Scheduled
Instances Placement Describes the placement for a Scheduled Instance.
- Scheduled
Instances Private IpAddress Config Describes a private IPv4 address for a Scheduled Instance.
- Security
Group Describes a security group.
- Security
Group ForVpc A security group that can be used by interfaces in the VPC.
- Security
Group Identifier Describes a security group.
- Security
Group Reference Describes a VPC with a security group that references your security group.
- Security
Group Rule Describes a security group rule.
- Security
Group Rule Description Describes the description of a security group rule.
You can use this when you want to update the security group rule description for either an inbound or outbound rule.
- Security
Group Rule Request Describes a security group rule.
You must specify exactly one of the following parameters, based on the rule type:
-
CidrIpv4
-
CidrIpv6
-
PrefixListId
-
ReferencedGroupId
Amazon Web Services canonicalizes IPv4 and IPv6 CIDRs. For example, if you specify 100.68.0.18/18 for the CIDR block, Amazon Web Services canonicalizes the CIDR block to 100.68.0.0/18. Any subsequent DescribeSecurityGroups and DescribeSecurityGroupRules calls will return the canonicalized form of the CIDR block. Additionally, if you attempt to add another rule with the non-canonical form of the CIDR (such as 100.68.0.18/18) and there is already a rule for the canonicalized form of the CIDR block (such as 100.68.0.0/18), the API throws an duplicate rule error.
When you modify a rule, you cannot change the rule type. For example, if the rule uses an IPv4 address range, you must use
CidrIpv4
to specify a new IPv4 address range.-
- Security
Group Rule Update Describes an update to a security group rule.
- Security
Group VpcAssociation A security group association with a VPC that you made with AssociateSecurityGroupVpc.
- Service
Configuration Describes a service configuration for a VPC endpoint service.
- Service
Detail Describes a VPC endpoint service.
- Service
Link Virtual Interface Describes the service link virtual interfaces that establish connectivity between Amazon Web Services Outpost and on-premises networks.
- Service
Type Detail Describes the type of service for a VPC endpoint.
- Slot
Date Time Range Request Describes the time period for a Scheduled Instance to start its first schedule. The time period must span less than one day.
- Slot
Start Time Range Request Describes the time period for a Scheduled Instance to start its first schedule.
- Snapshot
Describes a snapshot.
- Snapshot
Detail Describes the snapshot created from the imported disk.
- Snapshot
Disk Container The disk container object for the import snapshot request.
- Snapshot
Info Information about a snapshot.
- Snapshot
Recycle BinInfo Information about a snapshot that is currently in the Recycle Bin.
- Snapshot
Task Detail Details about the import snapshot task.
- Snapshot
Tier Status Provides information about a snapshot's storage tier.
- Spot
Capacity Rebalance The Spot Instance replacement strategy to use when Amazon EC2 emits a signal that your Spot Instance is at an elevated risk of being interrupted. For more information, see Capacity rebalancing in the Amazon EC2 User Guide.
- Spot
Datafeed Subscription Describes the data feed for a Spot Instance.
- Spot
Fleet Launch Specification Describes the launch specification for one or more Spot Instances. If you include On-Demand capacity in your fleet request or want to specify an EFA network device, you can't use
SpotFleetLaunchSpecification
; you must use LaunchTemplateConfig.- Spot
Fleet Monitoring Describes whether monitoring is enabled.
- Spot
Fleet Request Config Describes a Spot Fleet request.
- Spot
Fleet Request Config Data Describes the configuration of a Spot Fleet request.
- Spot
Fleet TagSpecification The tags for a Spot Fleet resource.
- Spot
Instance Request Describes a Spot Instance request.
- Spot
Instance State Fault Describes a Spot Instance state change.
- Spot
Instance Status Describes the status of a Spot Instance request.
- Spot
Maintenance Strategies The strategies for managing your Spot Instances that are at an elevated risk of being interrupted.
- Spot
Market Options The options for Spot Instances.
- Spot
Options Describes the configuration of Spot Instances in an EC2 Fleet.
- Spot
Options Request Describes the configuration of Spot Instances in an EC2 Fleet request.
- Spot
Placement Describes Spot Instance placement.
- Spot
Placement Score The Spot placement score for this Region or Availability Zone. The score is calculated based on the assumption that the
capacity-optimized
allocation strategy is used and that all of the Availability Zones in the Region can be used.- Spot
Price The maximum price per unit hour that you are willing to pay for a Spot Instance. We do not recommend using this parameter because it can lead to increased interruptions. If you do not specify this parameter, you will pay the current Spot price.
If you specify a maximum price, your instances will be interrupted more frequently than if you do not specify this parameter.
- Stale
IpPermission Describes a stale rule in a security group.
- Stale
Security Group Describes a stale security group (a security group that contains stale rules).
- State
Reason Describes a state change.
- Storage
Describes the storage location for an instance store-backed AMI.
- Storage
Location Describes a storage location in Amazon S3.
- Store
Image Task Result The information about the AMI store task, including the progress of the task.
- Subnet
Describes a subnet.
- Subnet
Association Describes the subnet association with the transit gateway multicast domain.
- Subnet
Cidr Block State Describes the state of a CIDR block.
- Subnet
Cidr Reservation Describes a subnet CIDR reservation.
- Subnet
Configuration Describes the configuration of a subnet for a VPC endpoint.
- Subnet
IpPrefixes Prefixes of the subnet IP.
- Subnet
Ipv6 Cidr Block Association Describes an association between a subnet and an IPv6 CIDR block.
- Subscription
Describes an Infrastructure Performance subscription.
- Successful
Instance Credit Specification Item Describes the burstable performance instance whose credit option for CPU usage was successfully modified.
- Successful
Queued Purchase Deletion Describes a Reserved Instance whose queued purchase was successfully deleted.
- Supported
Region Detail Describes a supported Region.
- Tag
Describes a tag.
- TagDescription
Describes a tag.
- TagSpecification
The tags to apply to a resource when the resource is being created. When you specify a tag, you must specify the resource type to tag, otherwise the request will fail.
The
Valid Values
lists all the resource types that can be tagged. However, the action you're using might not support tagging all of these resource types. If you try to tag a resource type that is unsupported for the action you're using, you'll get an error.- Target
Capacity Specification The number of units to request. You can choose to set the target capacity in terms of instances or a performance characteristic that is important to your application workload, such as vCPUs, memory, or I/O. If the request type is
maintain
, you can specify a target capacity of 0 and add capacity later.You can use the On-Demand Instance
MaxTotalPrice
parameter, the Spot InstanceMaxTotalPrice
, or both to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, EC2 Fleet will launch instances until it reaches the maximum amount that you're willing to pay. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasn’t met the target capacity. TheMaxTotalPrice
parameters are located in OnDemandOptions and SpotOptions.- Target
Capacity Specification Request The number of units to request. You can choose to set the target capacity as the number of instances. Or you can set the target capacity to a performance characteristic that is important to your application workload, such as vCPUs, memory, or I/O. If the request type is
maintain
, you can specify a target capacity of 0 and add capacity later.You can use the On-Demand Instance
MaxTotalPrice
parameter, the Spot InstanceMaxTotalPrice
parameter, or both parameters to ensure that your fleet cost does not exceed your budget. If you set a maximum price per hour for the On-Demand Instances and Spot Instances in your request, EC2 Fleet will launch instances until it reaches the maximum amount that you're willing to pay. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasn't met the target capacity. TheMaxTotalPrice
parameters are located in OnDemandOptionsRequest and SpotOptionsRequest.- Target
Configuration Information about the Convertible Reserved Instance offering.
- Target
Configuration Request Details about the target configuration.
- Target
Group Describes a load balancer target group.
- Target
Groups Config Describes the target groups to attach to a Spot Fleet. Spot Fleet registers the running Spot Instances with these target groups.
- Target
Network Describes a target network associated with a Client VPN endpoint.
- Target
Reservation Value The total value of the new Convertible Reserved Instances.
- Terminate
Connection Status Information about a terminated Client VPN endpoint client connection.
- Through
Resources Statement Describes a through resource statement.
- Through
Resources Statement Request Describes a through resource statement.
- Total
Local Storage Gb The minimum and maximum amount of total local storage, in GB.
- Total
Local Storage GbRequest The minimum and maximum amount of total local storage, in GB.
- Traffic
Mirror Filter Describes the Traffic Mirror filter.
- Traffic
Mirror Filter Rule Describes the Traffic Mirror rule.
- Traffic
Mirror Port Range Describes the Traffic Mirror port range.
- Traffic
Mirror Port Range Request Information about the Traffic Mirror filter rule port range.
- Traffic
Mirror Session Describes a Traffic Mirror session.
- Traffic
Mirror Target Describes a Traffic Mirror target.
- Transit
Gateway Describes a transit gateway.
- Transit
Gateway Association Describes an association between a resource attachment and a transit gateway route table.
- Transit
Gateway Attachment Describes an attachment between a resource and a transit gateway.
- Transit
Gateway Attachment Association Describes an association.
- Transit
Gateway Attachment BgpConfiguration The BGP configuration information.
- Transit
Gateway Attachment Propagation Describes a propagation route table.
- Transit
Gateway Connect Describes a transit gateway Connect attachment.
- Transit
Gateway Connect Options Describes the Connect attachment options.
- Transit
Gateway Connect Peer Describes a transit gateway Connect peer.
- Transit
Gateway Connect Peer Configuration Describes the Connect peer details.
- Transit
Gateway Connect Request BgpOptions The BGP options for the Connect attachment.
- Transit
Gateway Multicast Deregistered Group Members Describes the deregistered transit gateway multicast group members.
- Transit
Gateway Multicast Deregistered Group Sources Describes the deregistered transit gateway multicast group sources.
- Transit
Gateway Multicast Domain Describes the transit gateway multicast domain.
- Transit
Gateway Multicast Domain Association Describes the resources associated with the transit gateway multicast domain.
- Transit
Gateway Multicast Domain Associations Describes the multicast domain associations.
- Transit
Gateway Multicast Domain Options Describes the options for a transit gateway multicast domain.
- Transit
Gateway Multicast Group Describes the transit gateway multicast group resources.
- Transit
Gateway Multicast Registered Group Members Describes the registered transit gateway multicast group members.
- Transit
Gateway Multicast Registered Group Sources Describes the members registered with the transit gateway multicast group.
- Transit
Gateway Options Describes the options for a transit gateway.
- Transit
Gateway Peering Attachment Describes the transit gateway peering attachment.
- Transit
Gateway Peering Attachment Options Describes dynamic routing for the transit gateway peering attachment.
- Transit
Gateway Policy Rule Describes a rule associated with a transit gateway policy.
- Transit
Gateway Policy Rule Meta Data Describes the meta data tags associated with a transit gateway policy rule.
- Transit
Gateway Policy Table Describes a transit gateway policy table.
- Transit
Gateway Policy Table Association Describes a transit gateway policy table association.
- Transit
Gateway Policy Table Entry Describes a transit gateway policy table entry
- Transit
Gateway Prefix List Attachment Describes a transit gateway prefix list attachment.
- Transit
Gateway Prefix List Reference Describes a prefix list reference.
- Transit
Gateway Propagation Describes route propagation.
- Transit
Gateway Request Options Describes the options for a transit gateway.
- Transit
Gateway Route Describes a route for a transit gateway route table.
- Transit
Gateway Route Attachment Describes a route attachment.
- Transit
Gateway Route Table Describes a transit gateway route table.
- Transit
Gateway Route Table Announcement Describes a transit gateway route table announcement.
- Transit
Gateway Route Table Association Describes an association between a route table and a resource attachment.
- Transit
Gateway Route Table Propagation Describes a route table propagation.
- Transit
Gateway Route Table Route Describes a route in a transit gateway route table.
- Transit
Gateway VpcAttachment Describes a VPC attachment.
- Transit
Gateway VpcAttachment Options Describes the VPC attachment options.
- Trunk
Interface Association Information about an association between a branch network interface with a trunk network interface.
- Tunnel
Option The VPN tunnel options.
- Unsuccessful
Instance Credit Specification Item Describes the burstable performance instance whose credit option for CPU usage was not modified.
- Unsuccessful
Instance Credit Specification Item Error Information about the error for the burstable performance instance whose credit option for CPU usage was not modified.
- Unsuccessful
Item Information about items that were not successfully processed in a batch call.
- Unsuccessful
Item Error Information about the error that occurred. For more information about errors, see Error codes.
- User
Bucket Describes the Amazon S3 bucket for the disk image.
- User
Bucket Details Describes the Amazon S3 bucket for the disk image.
- User
Data Describes the user data for an instance.
- User
IdGroup Pair Describes a security group and Amazon Web Services account ID pair.
- VCpu
Count Range The minimum and maximum number of vCPUs.
- VCpu
Count Range Request The minimum and maximum number of vCPUs.
- VCpu
Info Describes the vCPU configurations for the instance type.
- Validation
Error The error code and error message that is returned for a parameter or parameter combination that is not valid when a new launch template or new version of a launch template is created.
- Validation
Warning The error codes and error messages that are returned for the parameters or parameter combinations that are not valid when a new launch template or new version of a launch template is created.
- Verified
Access Endpoint An Amazon Web Services Verified Access endpoint specifies the application that Amazon Web Services Verified Access provides access to. It must be attached to an Amazon Web Services Verified Access group. An Amazon Web Services Verified Access endpoint must also have an attached access policy before you attached it to a group.
- Verified
Access Endpoint Cidr Options Describes the CIDR options for a Verified Access endpoint.
- Verified
Access Endpoint EniOptions Options for a network-interface type endpoint.
- Verified
Access Endpoint Load Balancer Options Describes a load balancer when creating an Amazon Web Services Verified Access endpoint using the
load-balancer
type.- Verified
Access Endpoint Port Range Describes a port range.
- Verified
Access Endpoint RdsOptions Describes the RDS options for a Verified Access endpoint.
- Verified
Access Endpoint Status Describes the status of a Verified Access endpoint.
- Verified
Access Endpoint Target Describes the targets for the specified Verified Access endpoint.
- Verified
Access Group Describes a Verified Access group.
- Verified
Access Instance Describes a Verified Access instance.
- Verified
Access Instance Custom SubDomain Describes a custom subdomain for a network CIDR endpoint for Verified Access.
- Verified
Access Instance Logging Configuration Describes logging options for an Amazon Web Services Verified Access instance.
- Verified
Access Instance Open VpnClient Configuration Describes a set of routes.
- Verified
Access Instance Open VpnClient Configuration Route Describes a route.
- Verified
Access Instance User Trust Provider Client Configuration Describes the trust provider.
- Verified
Access LogCloud Watch Logs Destination Options for CloudWatch Logs as a logging destination.
- Verified
Access LogCloud Watch Logs Destination Options Options for CloudWatch Logs as a logging destination.
- Verified
Access LogDelivery Status Describes a log delivery status.
- Verified
Access LogKinesis Data Firehose Destination Options for Kinesis as a logging destination.
- Verified
Access LogKinesis Data Firehose Destination Options Describes Amazon Kinesis Data Firehose logging options.
- Verified
Access LogOptions Options for Verified Access logs.
- Verified
Access LogS3 Destination Options for Amazon S3 as a logging destination.
- Verified
Access LogS3 Destination Options Options for Amazon S3 as a logging destination.
- Verified
Access Logs Describes the options for Verified Access logs.
- Verified
Access SseSpecification Request Verified Access provides server side encryption by default to data at rest using Amazon Web Services-owned KMS keys. You also have the option of using customer managed KMS keys, which can be specified using the options below.
- Verified
Access SseSpecification Response The options in use for server side encryption.
- Verified
Access Trust Provider Describes a Verified Access trust provider.
- Verified
Access Trust Provider Condensed Condensed information about a trust provider.
- VgwTelemetry
Describes telemetry for a VPN tunnel.
- Volume
Describes a volume.
- Volume
Attachment Describes volume attachment details.
- Volume
Detail Describes an EBS volume.
- Volume
Modification Describes the modification status of an EBS volume.
- Volume
Status Action Describes a volume status operation code.
- Volume
Status Attachment Status Information about the instances to which the volume is attached.
- Volume
Status Details Describes a volume status.
- Volume
Status Event Describes a volume status event.
- Volume
Status Info Describes the status of a volume.
- Volume
Status Item Describes the volume status.
- Vpc
Describes a VPC.
- VpcAttachment
Describes an attachment between a virtual private gateway and a VPC.
- VpcBlock
Public Access Exclusion A VPC BPA exclusion is a mode that can be applied to a single VPC or subnet that exempts it from the account’s BPA mode and will allow bidirectional or egress-only access. You can create BPA exclusions for VPCs and subnets even when BPA is not enabled on the account to ensure that there is no traffic disruption to the exclusions when VPC BPA is turned on. To learn more about VPC BPA, see Block public access to VPCs and subnets in the Amazon VPC User Guide.
- VpcBlock
Public Access Options VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. To learn more about VPC BPA, see Block public access to VPCs and subnets in the Amazon VPC User Guide.
- VpcCidr
Block Association Describes an IPv4 CIDR block associated with a VPC.
- VpcCidr
Block State Describes the state of a CIDR block.
- VpcClassic
Link Deprecated.
Describes whether a VPC is enabled for ClassicLink.
- VpcEncryption
Control - VpcEncryption
Control Exclusion - VpcEncryption
Control Exclusions - VpcEndpoint
Describes a VPC endpoint.
- VpcEndpoint
Association Describes the VPC resources, VPC endpoint services, Lattice services, or service networks associated with the VPC endpoint.
- VpcEndpoint
Connection Describes a VPC endpoint connection to a service.
- VpcIpv6
Cidr Block Association Describes an IPv6 CIDR block associated with a VPC.
- VpcPeering
Connection Describes a VPC peering connection.
- VpcPeering
Connection Options Description Describes the VPC peering connection options.
- VpcPeering
Connection State Reason Describes the status of a VPC peering connection.
- VpcPeering
Connection VpcInfo Describes a VPC in a VPC peering connection.
- VpnConnection
Describes a VPN connection.
- VpnConnection
Device Type List of customer gateway devices that have a sample configuration file available for use. You can also see the list of device types with sample configuration files available under Your customer gateway device in the Amazon Web Services Site-to-Site VPN User Guide.
- VpnConnection
Options Describes VPN connection options.
- VpnConnection
Options Specification Describes VPN connection options.
- VpnGateway
Describes a virtual private gateway.
- VpnStatic
Route Describes a static route for a VPN connection.
- VpnTunnel
LogOptions Options for logging VPN tunnel activity.
- VpnTunnel
LogOptions Specification Options for logging VPN tunnel activity.
- VpnTunnel
Options Specification The tunnel options for a single VPN tunnel.
Enums§
- Accelerator
Manufacturer - When writing a match expression against
AcceleratorManufacturer
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Accelerator
Name - When writing a match expression against
AcceleratorName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Accelerator
Type - When writing a match expression against
AcceleratorType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Account
Attribute Name - When writing a match expression against
AccountAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Activity
Status - When writing a match expression against
ActivityStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Address
Attribute Name - When writing a match expression against
AddressAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Address
Family - When writing a match expression against
AddressFamily
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Address
Transfer Status - When writing a match expression against
AddressTransferStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Affinity
- When writing a match expression against
Affinity
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allocation
State - When writing a match expression against
AllocationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allocation
Strategy - When writing a match expression against
AllocationStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allocation
Type - When writing a match expression against
AllocationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allowed
Images Settings Disabled State - When writing a match expression against
AllowedImagesSettingsDisabledState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allowed
Images Settings Enabled State - When writing a match expression against
AllowedImagesSettingsEnabledState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Allows
Multiple Instance Types - When writing a match expression against
AllowsMultipleInstanceTypes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - AmdSev
SnpSpecification - When writing a match expression against
AmdSevSnpSpecification
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Analysis
Status - When writing a match expression against
AnalysisStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Appliance
Mode Support Value - When writing a match expression against
ApplianceModeSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Architecture
Type - When writing a match expression against
ArchitectureType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Architecture
Values - When writing a match expression against
ArchitectureValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - AsnAssociation
State - When writing a match expression against
AsnAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - AsnState
- When writing a match expression against
AsnState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Associated
Network Type - When writing a match expression against
AssociatedNetworkType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Association
Status Code - When writing a match expression against
AssociationStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Attachment
Status - When writing a match expression against
AttachmentStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Auto
Accept Shared Associations Value - When writing a match expression against
AutoAcceptSharedAssociationsValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Auto
Accept Shared Attachments Value - When writing a match expression against
AutoAcceptSharedAttachmentsValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Auto
Placement - When writing a match expression against
AutoPlacement
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Availability
Zone OptIn Status - When writing a match expression against
AvailabilityZoneOptInStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Availability
Zone State - When writing a match expression against
AvailabilityZoneState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bandwidth
Weighting Type - When writing a match expression against
BandwidthWeightingType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bare
Metal - When writing a match expression against
BareMetal
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Batch
State - When writing a match expression against
BatchState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - BgpStatus
- When writing a match expression against
BgpStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Block
Public Access Mode - When writing a match expression against
BlockPublicAccessMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Boot
Mode Type - When writing a match expression against
BootModeType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Boot
Mode Values - When writing a match expression against
BootModeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Bundle
Task State - When writing a match expression against
BundleTaskState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Burstable
Performance - When writing a match expression against
BurstablePerformance
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Byoip
Cidr State - When writing a match expression against
ByoipCidrState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Caller
Role - When writing a match expression against
CallerRole
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Cancel
Batch Error Code - When writing a match expression against
CancelBatchErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Cancel
Spot Instance Request State - When writing a match expression against
CancelSpotInstanceRequestState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Block Extension Status - When writing a match expression against
CapacityBlockExtensionStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Billing Request Status - When writing a match expression against
CapacityReservationBillingRequestStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Delivery Preference - When writing a match expression against
CapacityReservationDeliveryPreference
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Fleet State - When writing a match expression against
CapacityReservationFleetState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Instance Platform - When writing a match expression against
CapacityReservationInstancePlatform
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Preference - When writing a match expression against
CapacityReservationPreference
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation State - When writing a match expression against
CapacityReservationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Tenancy - When writing a match expression against
CapacityReservationTenancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Capacity
Reservation Type - When writing a match expression against
CapacityReservationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Carrier
Gateway State - When writing a match expression against
CarrierGatewayState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
Certificate Revocation List Status Code - When writing a match expression against
ClientCertificateRevocationListStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnAuthentication Type - When writing a match expression against
ClientVpnAuthenticationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnAuthorization Rule Status Code - When writing a match expression against
ClientVpnAuthorizationRuleStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnConnection Status Code - When writing a match expression against
ClientVpnConnectionStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnEndpoint Attribute Status Code - When writing a match expression against
ClientVpnEndpointAttributeStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnEndpoint Status Code - When writing a match expression against
ClientVpnEndpointStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Client
VpnRoute Status Code - When writing a match expression against
ClientVpnRouteStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Connection
Notification State - When writing a match expression against
ConnectionNotificationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Connection
Notification Type - When writing a match expression against
ConnectionNotificationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Connectivity
Type - When writing a match expression against
ConnectivityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Container
Format - When writing a match expression against
ContainerFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Conversion
Task State - When writing a match expression against
ConversionTaskState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Copy
Tags From Source - When writing a match expression against
CopyTagsFromSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - CpuManufacturer
- When writing a match expression against
CpuManufacturer
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Currency
Code Values - When writing a match expression against
CurrencyCodeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Datafeed
Subscription State - When writing a match expression against
DatafeedSubscriptionState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Default
Instance Metadata Endpoint State - When writing a match expression against
DefaultInstanceMetadataEndpointState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Default
Instance Metadata Tags State - When writing a match expression against
DefaultInstanceMetadataTagsState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Default
Route Table Association Value - When writing a match expression against
DefaultRouteTableAssociationValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Default
Route Table Propagation Value - When writing a match expression against
DefaultRouteTablePropagationValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Default
Target Capacity Type - When writing a match expression against
DefaultTargetCapacityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Delete
Fleet Error Code - When writing a match expression against
DeleteFleetErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Delete
Queued Reserved Instances Error Code - When writing a match expression against
DeleteQueuedReservedInstancesErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Destination
File Format - When writing a match expression against
DestinationFileFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Device
Trust Provider Type - When writing a match expression against
DeviceTrustProviderType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Device
Type - When writing a match expression against
DeviceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Disk
Image Format - When writing a match expression against
DiskImageFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Disk
Type - When writing a match expression against
DiskType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - DnsName
State - When writing a match expression against
DnsNameState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - DnsRecord
IpType - When writing a match expression against
DnsRecordIpType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - DnsSupport
Value - When writing a match expression against
DnsSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Domain
Type - When writing a match expression against
DomainType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dynamic
Routing Value - When writing a match expression against
DynamicRoutingValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EbsEncryption
Support - When writing a match expression against
EbsEncryptionSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EbsNvme
Support - When writing a match expression against
EbsNvmeSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EbsOptimized
Support - When writing a match expression against
EbsOptimizedSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ec2Instance
Connect Endpoint State - When writing a match expression against
Ec2InstanceConnectEndpointState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EkPub
KeyFormat - When writing a match expression against
EkPubKeyFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EkPub
KeyType - When writing a match expression against
EkPubKeyType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Elastic
GpuState - When writing a match expression against
ElasticGpuState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Elastic
GpuStatus - When writing a match expression against
ElasticGpuStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EnaSupport
- When writing a match expression against
EnaSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - EndDate
Type - When writing a match expression against
EndDateType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ephemeral
Nvme Support - When writing a match expression against
EphemeralNvmeSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
Code - When writing a match expression against
EventCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
Type - When writing a match expression against
EventType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Excess
Capacity Termination Policy - When writing a match expression against
ExcessCapacityTerminationPolicy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Export
Environment - When writing a match expression against
ExportEnvironment
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Export
Task State - When writing a match expression against
ExportTaskState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fast
Launch Resource Type - When writing a match expression against
FastLaunchResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fast
Launch State Code - When writing a match expression against
FastLaunchStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fast
Snapshot Restore State Code - When writing a match expression against
FastSnapshotRestoreStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Findings
Found - When writing a match expression against
FindingsFound
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Activity Status - When writing a match expression against
FleetActivityStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Capacity Reservation Tenancy - When writing a match expression against
FleetCapacityReservationTenancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Capacity Reservation Usage Strategy - When writing a match expression against
FleetCapacityReservationUsageStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Event Type - When writing a match expression against
FleetEventType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Excess Capacity Termination Policy - When writing a match expression against
FleetExcessCapacityTerminationPolicy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Instance Match Criteria - When writing a match expression against
FleetInstanceMatchCriteria
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
OnDemand Allocation Strategy - When writing a match expression against
FleetOnDemandAllocationStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Replacement Strategy - When writing a match expression against
FleetReplacementStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
State Code - When writing a match expression against
FleetStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fleet
Type - When writing a match expression against
FleetType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Flexible
EnaQueues Support - When writing a match expression against
FlexibleEnaQueuesSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Flow
Logs Resource Type - When writing a match expression against
FlowLogsResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fpga
Image Attribute Name - When writing a match expression against
FpgaImageAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fpga
Image State Code - When writing a match expression against
FpgaImageStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Gateway
Association State - When writing a match expression against
GatewayAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Gateway
Type - When writing a match expression against
GatewayType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Host
Maintenance - When writing a match expression against
HostMaintenance
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Host
Recovery - When writing a match expression against
HostRecovery
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Host
Tenancy - When writing a match expression against
HostTenancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Hostname
Type - When writing a match expression against
HostnameType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Http
Tokens State - When writing a match expression against
HttpTokensState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Hypervisor
Type - When writing a match expression against
HypervisorType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - IamInstance
Profile Association State - When writing a match expression against
IamInstanceProfileAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Igmpv2
Support Value - When writing a match expression against
Igmpv2SupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
Attribute Name - When writing a match expression against
ImageAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
Block Public Access Disabled State - When writing a match expression against
ImageBlockPublicAccessDisabledState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
Block Public Access Enabled State - When writing a match expression against
ImageBlockPublicAccessEnabledState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
State - When writing a match expression against
ImageState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Image
Type Values - When writing a match expression against
ImageTypeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Imds
Support Values - When writing a match expression against
ImdsSupportValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Attribute Name - When writing a match expression against
InstanceAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Auto Recovery State - When writing a match expression against
InstanceAutoRecoveryState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Bandwidth Weighting - When writing a match expression against
InstanceBandwidthWeighting
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Boot Mode Values - When writing a match expression against
InstanceBootModeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Event Window State - When writing a match expression against
InstanceEventWindowState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Generation - When writing a match expression against
InstanceGeneration
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Health Status - When writing a match expression against
InstanceHealthStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Interruption Behavior - When writing a match expression against
InstanceInterruptionBehavior
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Lifecycle - When writing a match expression against
InstanceLifecycle
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Lifecycle Type - When writing a match expression against
InstanceLifecycleType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Match Criteria - When writing a match expression against
InstanceMatchCriteria
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Metadata Endpoint State - When writing a match expression against
InstanceMetadataEndpointState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Metadata Options State - When writing a match expression against
InstanceMetadataOptionsState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Metadata Protocol State - When writing a match expression against
InstanceMetadataProtocolState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Metadata Tags State - When writing a match expression against
InstanceMetadataTagsState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Reboot Migration State - When writing a match expression against
InstanceRebootMigrationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
State Name - When writing a match expression against
InstanceStateName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Storage Encryption Support - When writing a match expression against
InstanceStorageEncryptionSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Type - When writing a match expression against
InstanceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Instance
Type Hypervisor - When writing a match expression against
InstanceTypeHypervisor
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Interface
Permission Type - When writing a match expression against
InterfacePermissionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Interface
Protocol Type - When writing a match expression against
InterfaceProtocolType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Internet
Gateway Block Mode - When writing a match expression against
InternetGatewayBlockMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Internet
Gateway Exclusion Mode - When writing a match expression against
InternetGatewayExclusionMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - IpAddress
Type - When writing a match expression against
IpAddressType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - IpSource
- When writing a match expression against
IpSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Address History Resource Type - When writing a match expression against
IpamAddressHistoryResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Associated Resource Discovery Status - When writing a match expression against
IpamAssociatedResourceDiscoveryStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Compliance Status - When writing a match expression against
IpamComplianceStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Discovery Failure Code - When writing a match expression against
IpamDiscoveryFailureCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
External Resource Verification Token State - When writing a match expression against
IpamExternalResourceVerificationTokenState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Management State - When writing a match expression against
IpamManagementState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Metered Account - When writing a match expression against
IpamMeteredAccount
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Network Interface Attachment Status - When writing a match expression against
IpamNetworkInterfaceAttachmentStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Overlap Status - When writing a match expression against
IpamOverlapStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool Allocation Resource Type - When writing a match expression against
IpamPoolAllocationResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool AwsService - When writing a match expression against
IpamPoolAwsService
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool Cidr Failure Code - When writing a match expression against
IpamPoolCidrFailureCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool Cidr State - When writing a match expression against
IpamPoolCidrState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool Public IpSource - When writing a match expression against
IpamPoolPublicIpSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool Source Resource Type - When writing a match expression against
IpamPoolSourceResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Pool State - When writing a match expression against
IpamPoolState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Public Address Association Status - When writing a match expression against
IpamPublicAddressAssociationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Public Address AwsService - When writing a match expression against
IpamPublicAddressAwsService
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Public Address Type - When writing a match expression against
IpamPublicAddressType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Resource Cidr IpSource - When writing a match expression against
IpamResourceCidrIpSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Resource Discovery Association State - When writing a match expression against
IpamResourceDiscoveryAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Resource Discovery State - When writing a match expression against
IpamResourceDiscoveryState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Resource Type - When writing a match expression against
IpamResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Scope State - When writing a match expression against
IpamScopeState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Scope Type - When writing a match expression against
IpamScopeType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
State - When writing a match expression against
IpamState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipam
Tier - When writing a match expression against
IpamTier
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipv6
Address Attribute - When writing a match expression against
Ipv6AddressAttribute
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Ipv6
Support Value - When writing a match expression against
Ipv6SupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - KeyFormat
- When writing a match expression against
KeyFormat
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - KeyType
- When writing a match expression against
KeyType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Auto Recovery State - When writing a match expression against
LaunchTemplateAutoRecoveryState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Error Code - When writing a match expression against
LaunchTemplateErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Http Tokens State - When writing a match expression against
LaunchTemplateHttpTokensState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Instance Metadata Endpoint State - When writing a match expression against
LaunchTemplateInstanceMetadataEndpointState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Instance Metadata Options State - When writing a match expression against
LaunchTemplateInstanceMetadataOptionsState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Instance Metadata Protocol Ipv6 - When writing a match expression against
LaunchTemplateInstanceMetadataProtocolIpv6
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Launch
Template Instance Metadata Tags State - When writing a match expression against
LaunchTemplateInstanceMetadataTagsState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Listing
State - When writing a match expression against
ListingState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Listing
Status - When writing a match expression against
ListingStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Gateway Route State - When writing a match expression against
LocalGatewayRouteState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Gateway Route Table Mode - When writing a match expression against
LocalGatewayRouteTableMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Gateway Route Type - When writing a match expression against
LocalGatewayRouteType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Gateway Virtual Interface Configuration State - When writing a match expression against
LocalGatewayVirtualInterfaceConfigurationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Gateway Virtual Interface Group Configuration State - When writing a match expression against
LocalGatewayVirtualInterfaceGroupConfigurationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Storage - When writing a match expression against
LocalStorage
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Local
Storage Type - When writing a match expression against
LocalStorageType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Location
Type - When writing a match expression against
LocationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Lock
Mode - When writing a match expression against
LockMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Lock
State - When writing a match expression against
LockState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - LogDestination
Type - When writing a match expression against
LogDestinationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - MacModification
Task State - When writing a match expression against
MacModificationTaskState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - MacModification
Task Type - When writing a match expression against
MacModificationTaskType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - MacSystem
Integrity Protection Setting Status - When writing a match expression against
MacSystemIntegrityProtectionSettingStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Managed
By - When writing a match expression against
ManagedBy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Market
Type - When writing a match expression against
MarketType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Membership
Type - When writing a match expression against
MembershipType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metadata
Default Http Tokens State - When writing a match expression against
MetadataDefaultHttpTokensState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metric
Type - When writing a match expression against
MetricType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Modify
Availability Zone OptIn Status - When writing a match expression against
ModifyAvailabilityZoneOptInStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Monitoring
State - When writing a match expression against
MonitoringState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Move
Status - When writing a match expression against
MoveStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Multicast
Support Value - When writing a match expression against
MulticastSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - NatGateway
Address Status - When writing a match expression against
NatGatewayAddressStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - NatGateway
State - When writing a match expression against
NatGatewayState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Interface Attribute - When writing a match expression against
NetworkInterfaceAttribute
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Interface Creation Type - When writing a match expression against
NetworkInterfaceCreationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Interface Permission State Code - When writing a match expression against
NetworkInterfacePermissionStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Interface Status - When writing a match expression against
NetworkInterfaceStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Network
Interface Type - When writing a match expression against
NetworkInterfaceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Nitro
Enclaves Support - When writing a match expression against
NitroEnclavesSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Nitro
TpmSupport - When writing a match expression against
NitroTpmSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Offering
Class Type - When writing a match expression against
OfferingClassType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Offering
Type Values - When writing a match expression against
OfferingTypeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - OnDemand
Allocation Strategy - When writing a match expression against
OnDemandAllocationStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Operation
Type - When writing a match expression against
OperationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Partition
Load Frequency - When writing a match expression against
PartitionLoadFrequency
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Payer
Responsibility - When writing a match expression against
PayerResponsibility
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Payment
Option - When writing a match expression against
PaymentOption
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Period
Type - When writing a match expression against
PeriodType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Permission
Group - When writing a match expression against
PermissionGroup
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - PhcSupport
- When writing a match expression against
PhcSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Placement
Group State - When writing a match expression against
PlacementGroupState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Placement
Group Strategy - When writing a match expression against
PlacementGroupStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Placement
Strategy - When writing a match expression against
PlacementStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Platform
Values - When writing a match expression against
PlatformValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Prefix
List State - When writing a match expression against
PrefixListState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Principal
Type - When writing a match expression against
PrincipalType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Product
Code Values - When writing a match expression against
ProductCodeValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Protocol
- When writing a match expression against
Protocol
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Protocol
Value - When writing a match expression against
ProtocolValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Public
IpDns Option - When writing a match expression against
PublicIpDnsOption
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Reboot
Migration Support - When writing a match expression against
RebootMigrationSupport
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Recurring
Charge Frequency - When writing a match expression against
RecurringChargeFrequency
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replace
Root Volume Task State - When writing a match expression against
ReplaceRootVolumeTaskState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Replacement
Strategy - When writing a match expression against
ReplacementStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Report
Instance Reason Codes - When writing a match expression against
ReportInstanceReasonCodes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Report
State - When writing a match expression against
ReportState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Report
Status Type - When writing a match expression against
ReportStatusType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Reservation
State - When writing a match expression against
ReservationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Reserved
Instance State - When writing a match expression against
ReservedInstanceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Reset
Fpga Image Attribute Name - When writing a match expression against
ResetFpgaImageAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Reset
Image Attribute Name - When writing a match expression against
ResetImageAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Resource
Type - When writing a match expression against
ResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - RiProduct
Description - When writing a match expression against
RiProductDescription
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Root
Device Type - When writing a match expression against
RootDeviceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Origin - When writing a match expression against
RouteOrigin
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Association State - When writing a match expression against
RouteServerAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server BfdState - When writing a match expression against
RouteServerBfdState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server BgpState - When writing a match expression against
RouteServerBgpState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Endpoint State - When writing a match expression against
RouteServerEndpointState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Peer Liveness Mode - When writing a match expression against
RouteServerPeerLivenessMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Peer State - When writing a match expression against
RouteServerPeerState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Persist Routes Action - When writing a match expression against
RouteServerPersistRoutesAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Persist Routes State - When writing a match expression against
RouteServerPersistRoutesState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Propagation State - When writing a match expression against
RouteServerPropagationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Route Installation Status - When writing a match expression against
RouteServerRouteInstallationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server Route Status - When writing a match expression against
RouteServerRouteStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Server State - When writing a match expression against
RouteServerState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
State - When writing a match expression against
RouteState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Route
Table Association State Code - When writing a match expression against
RouteTableAssociationStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Rule
Action - When writing a match expression against
RuleAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Scope
- When writing a match expression against
Scope
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Security
Group Referencing Support Value - When writing a match expression against
SecurityGroupReferencingSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Security
Group VpcAssociation State - When writing a match expression against
SecurityGroupVpcAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Self
Service Portal - When writing a match expression against
SelfServicePortal
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Service
Connectivity Type - When writing a match expression against
ServiceConnectivityType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Service
Link Virtual Interface Configuration State - When writing a match expression against
ServiceLinkVirtualInterfaceConfigurationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Service
Managed - When writing a match expression against
ServiceManaged
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Service
State - When writing a match expression against
ServiceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Service
Type - When writing a match expression against
ServiceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Shutdown
Behavior - When writing a match expression against
ShutdownBehavior
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Snapshot
Attribute Name - When writing a match expression against
SnapshotAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Snapshot
Block Public Access State - When writing a match expression against
SnapshotBlockPublicAccessState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Snapshot
Location Enum - When writing a match expression against
SnapshotLocationEnum
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Snapshot
Return Codes - When writing a match expression against
SnapshotReturnCodes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Snapshot
State - When writing a match expression against
SnapshotState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Spot
Allocation Strategy - When writing a match expression against
SpotAllocationStrategy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Spot
Instance Interruption Behavior - When writing a match expression against
SpotInstanceInterruptionBehavior
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Spot
Instance State - When writing a match expression against
SpotInstanceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Spot
Instance Type - When writing a match expression against
SpotInstanceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Spread
Level - When writing a match expression against
SpreadLevel
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - SseType
- When writing a match expression against
SseType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - State
- When writing a match expression against
State
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Static
Sources Support Value - When writing a match expression against
StaticSourcesSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Statistic
Type - When writing a match expression against
StatisticType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Status
- When writing a match expression against
Status
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Status
Name - When writing a match expression against
StatusName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Status
Type - When writing a match expression against
StatusType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Storage
Tier - When writing a match expression against
StorageTier
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Subnet
Cidr Block State Code - When writing a match expression against
SubnetCidrBlockStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Subnet
Cidr Reservation Type - When writing a match expression against
SubnetCidrReservationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Subnet
State - When writing a match expression against
SubnetState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Summary
Status - When writing a match expression against
SummaryStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Supported
Additional Processor Feature - When writing a match expression against
SupportedAdditionalProcessorFeature
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Target
Capacity Unit Type - When writing a match expression against
TargetCapacityUnitType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Target
Storage Tier - When writing a match expression against
TargetStorageTier
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Telemetry
Status - When writing a match expression against
TelemetryStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Tenancy
- When writing a match expression against
Tenancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Tiering
Operation Status - When writing a match expression against
TieringOperationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Token
State - When writing a match expression against
TokenState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - TpmSupport
Values - When writing a match expression against
TpmSupportValues
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Direction - When writing a match expression against
TrafficDirection
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Mirror Filter Rule Field - When writing a match expression against
TrafficMirrorFilterRuleField
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Mirror Network Service - When writing a match expression against
TrafficMirrorNetworkService
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Mirror Rule Action - When writing a match expression against
TrafficMirrorRuleAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Mirror Session Field - When writing a match expression against
TrafficMirrorSessionField
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Mirror Target Type - When writing a match expression against
TrafficMirrorTargetType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Traffic
Type - When writing a match expression against
TrafficType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transfer
Type - When writing a match expression against
TransferType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Association State - When writing a match expression against
TransitGatewayAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Attachment Resource Type - When writing a match expression against
TransitGatewayAttachmentResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Attachment State - When writing a match expression against
TransitGatewayAttachmentState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Connect Peer State - When writing a match expression against
TransitGatewayConnectPeerState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Mulitcast Domain Association State - When writing a match expression against
TransitGatewayMulitcastDomainAssociationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Multicast Domain State - When writing a match expression against
TransitGatewayMulticastDomainState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Policy Table State - When writing a match expression against
TransitGatewayPolicyTableState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Prefix List Reference State - When writing a match expression against
TransitGatewayPrefixListReferenceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Propagation State - When writing a match expression against
TransitGatewayPropagationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Route State - When writing a match expression against
TransitGatewayRouteState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Route Table Announcement Direction - When writing a match expression against
TransitGatewayRouteTableAnnouncementDirection
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Route Table Announcement State - When writing a match expression against
TransitGatewayRouteTableAnnouncementState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Route Table State - When writing a match expression against
TransitGatewayRouteTableState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway Route Type - When writing a match expression against
TransitGatewayRouteType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transit
Gateway State - When writing a match expression against
TransitGatewayState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Transport
Protocol - When writing a match expression against
TransportProtocol
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Trust
Provider Type - When writing a match expression against
TrustProviderType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Tunnel
Inside IpVersion - When writing a match expression against
TunnelInsideIpVersion
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Unlimited
Supported Instance Family - When writing a match expression against
UnlimitedSupportedInstanceFamily
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Unsuccessful
Instance Credit Specification Error Code - When writing a match expression against
UnsuccessfulInstanceCreditSpecificationErrorCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Usage
Class Type - When writing a match expression against
UsageClassType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - User
Trust Provider Type - When writing a match expression against
UserTrustProviderType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verification
Method - When writing a match expression against
VerificationMethod
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verified
Access Endpoint Attachment Type - When writing a match expression against
VerifiedAccessEndpointAttachmentType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verified
Access Endpoint Protocol - When writing a match expression against
VerifiedAccessEndpointProtocol
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verified
Access Endpoint Status Code - When writing a match expression against
VerifiedAccessEndpointStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verified
Access Endpoint Type - When writing a match expression against
VerifiedAccessEndpointType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Verified
Access LogDelivery Status Code - When writing a match expression against
VerifiedAccessLogDeliveryStatusCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Virtualization
Type - When writing a match expression against
VirtualizationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Attachment State - When writing a match expression against
VolumeAttachmentState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Attribute Name - When writing a match expression against
VolumeAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Modification State - When writing a match expression against
VolumeModificationState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
State - When writing a match expression against
VolumeState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Status Info Status - When writing a match expression against
VolumeStatusInfoStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Status Name - When writing a match expression against
VolumeStatusName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Volume
Type - When writing a match expression against
VolumeType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcAttribute
Name - When writing a match expression against
VpcAttributeName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcBlock
Public Access Exclusion State - When writing a match expression against
VpcBlockPublicAccessExclusionState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcBlock
Public Access Exclusions Allowed - When writing a match expression against
VpcBlockPublicAccessExclusionsAllowed
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcBlock
Public Access State - When writing a match expression against
VpcBlockPublicAccessState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcCidr
Block State Code - When writing a match expression against
VpcCidrBlockStateCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcEncryption
Control Exclusion State - When writing a match expression against
VpcEncryptionControlExclusionState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcEncryption
Control Mode - When writing a match expression against
VpcEncryptionControlMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcEncryption
Control State - When writing a match expression against
VpcEncryptionControlState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcEndpoint
Type - When writing a match expression against
VpcEndpointType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcPeering
Connection State Reason Code - When writing a match expression against
VpcPeeringConnectionStateReasonCode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcState
- When writing a match expression against
VpcState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpcTenancy
- When writing a match expression against
VpcTenancy
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpnEcmp
Support Value - When writing a match expression against
VpnEcmpSupportValue
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpnProtocol
- When writing a match expression against
VpnProtocol
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpnState
- When writing a match expression against
VpnState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpnStatic
Route Source - When writing a match expression against
VpnStaticRouteSource
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - VpnTunnel
Provisioning Status - When writing a match expression against
VpnTunnelProvisioningStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - WeekDay
- When writing a match expression against
WeekDay
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.