diff --git a/VERSION b/VERSION index c718e9d8228..a18d6424584 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.11.393 \ No newline at end of file +1.11.394 \ No newline at end of file diff --git a/generated/src/aws-cpp-sdk-appconfig/include/aws/appconfig/AppConfigClient.h b/generated/src/aws-cpp-sdk-appconfig/include/aws/appconfig/AppConfigClient.h index b13888aef8e..77db83be1fc 100644 --- a/generated/src/aws-cpp-sdk-appconfig/include/aws/appconfig/AppConfigClient.h +++ b/generated/src/aws-cpp-sdk-appconfig/include/aws/appconfig/AppConfigClient.h @@ -381,8 +381,12 @@ namespace AppConfig } /** - *
Creates a new configuration in the AppConfig hosted configuration - * store.
Deletes an application. Deleting an application does not delete a - * configuration from a host.
Deletes a configuration profile. Deleting a configuration profile does not - * delete a configuration from a host.
To prevent users from unintentionally + * deleting actively-used configuration profiles, enable deletion + * protection.
Deletes a deployment strategy. Deleting a deployment strategy does not delete - * a configuration from a host.
Deletes an environment. Deleting an environment does not delete a - * configuration from a host.
To prevent users from unintentionally deleting + * actively-used environments, enable deletion + * protection.
Returns information about the status of the DeletionProtection
+ * parameter.
Retrieves information about an application.
Updates the value of the DeletionProtection
+ * parameter.
Updates an application.
A parameter to configure deletion protection. If enabled, deletion protection + * prevents a user from deleting a configuration profile if your application has + * called either GetLatestConfiguration + * or for the configuration profile during the specified interval.
This + * parameter supports the following values:
BYPASS
:
+ * Instructs AppConfig to bypass the deletion protection check and delete a
+ * configuration profile even if deletion protection would have otherwise prevented
+ * it.
APPLY
: Instructs the deletion protection
+ * check to run, even if deletion protection is disabled at the account level.
+ * APPLY
also forces the deletion protection check to run against
+ * resources created in the past hour, which are normally excluded from deletion
+ * protection checks.
ACCOUNT_DEFAULT
: The default
+ * setting, which instructs AppConfig to implement the deletion protection value
+ * specified in the UpdateAccountSettings
API.
The ID of the environment that you want to delete.
+ */ + inline const Aws::String& GetEnvironmentId() const{ return m_environmentId; } + inline bool EnvironmentIdHasBeenSet() const { return m_environmentIdHasBeenSet; } + inline void SetEnvironmentId(const Aws::String& value) { m_environmentIdHasBeenSet = true; m_environmentId = value; } + inline void SetEnvironmentId(Aws::String&& value) { m_environmentIdHasBeenSet = true; m_environmentId = std::move(value); } + inline void SetEnvironmentId(const char* value) { m_environmentIdHasBeenSet = true; m_environmentId.assign(value); } + inline DeleteEnvironmentRequest& WithEnvironmentId(const Aws::String& value) { SetEnvironmentId(value); return *this;} + inline DeleteEnvironmentRequest& WithEnvironmentId(Aws::String&& value) { SetEnvironmentId(std::move(value)); return *this;} + inline DeleteEnvironmentRequest& WithEnvironmentId(const char* value) { SetEnvironmentId(value); return *this;} + ///@} ///@{ /** @@ -48,24 +65,39 @@ namespace Model ///@{ /** - *The ID of the environment that you want to delete.
+ *A parameter to configure deletion protection. If enabled, deletion protection + * prevents a user from deleting an environment if your application called either + * GetLatestConfiguration + * or in the environment during the specified interval.
This parameter + * supports the following values:
BYPASS
: Instructs
+ * AppConfig to bypass the deletion protection check and delete a configuration
+ * profile even if deletion protection would have otherwise prevented it.
APPLY
: Instructs the deletion protection check to
+ * run, even if deletion protection is disabled at the account level.
+ * APPLY
also forces the deletion protection check to run against
+ * resources created in the past hour, which are normally excluded from deletion
+ * protection checks.
ACCOUNT_DEFAULT
: The default
+ * setting, which instructs AppConfig to implement the deletion protection value
+ * specified in the UpdateAccountSettings
API.
A parameter to configure deletion protection. If enabled, deletion protection + * prevents a user from deleting a configuration profile or an environment if + * AppConfig has called either GetLatestConfiguration + * or for the configuration profile or from the environment during the specified + * interval.
This setting uses the following default values:
Deletion protection is disabled by default.
The default
+ * interval specified by ProtectionPeriodInMinutes
is 60.
DeletionProtectionCheck
skips configuration profiles and
+ * environments that were created in the past hour.
A parameter that indicates if deletion protection is enabled or not.
+ */ + inline bool GetEnabled() const{ return m_enabled; } + inline bool EnabledHasBeenSet() const { return m_enabledHasBeenSet; } + inline void SetEnabled(bool value) { m_enabledHasBeenSet = true; m_enabled = value; } + inline DeletionProtectionSettings& WithEnabled(bool value) { SetEnabled(value); return *this;} + ///@} + + ///@{ + /** + *The time interval during which AppConfig monitors for calls to GetLatestConfiguration
+ * or for a configuration profile or from an environment. AppConfig returns an
+ * error if a user calls or for the designated configuration profile or
+ * environment. To bypass the error and delete a configuration profile or an
+ * environment, specify BYPASS
for the
+ * DeletionProtectionCheck
parameter for either or .
A parameter to configure deletion protection. If enabled, deletion protection
+ * prevents a user from deleting a configuration profile or an environment if
+ * AppConfig has called either GetLatestConfiguration
+ * or for the configuration profile or from the environment during the specified
+ * interval. Deletion protection is disabled by default. The default interval for
+ * ProtectionPeriodInMinutes
is 60.
A parameter to configure deletion protection. If enabled, deletion protection
+ * prevents a user from deleting a configuration profile or an environment if
+ * AppConfig has called either GetLatestConfiguration
+ * or for the configuration profile or from the environment during the specified
+ * interval. Deletion protection is disabled by default. The default interval for
+ * ProtectionPeriodInMinutes
is 60.
A parameter to configure deletion protection. If enabled, deletion protection
+ * prevents a user from deleting a configuration profile or an environment if
+ * AppConfig has called either GetLatestConfiguration
+ * or for the configuration profile or from the environment during the specified
+ * interval. Deletion protection is disabled by default. The default interval for
+ * ProtectionPeriodInMinutes
is 60.
Deletes an data product in Amazon DataZone.
RESULT_LOG
SERVICE_LOG
WEBKIT_LOG
*INSTRUMENTATION_OUTPUT
EXERCISER_MONKEY_OUTPUT: * the artifact (log) generated by an Android fuzz test.
CALABASH_JSON_OUTPUT
CALABASH_PRETTY_OUTPUT
CALABASH_STANDARD_OUTPUT
CALABASH_JAVA_XML_OUTPUT
AUTOMATION_OUTPUT
APPIUM_SERVER_OUTPUT
APPIUM_JAVA_OUTPUT
APPIUM_JAVA_XML_OUTPUT
APPIUM_PYTHON_OUTPUT
APPIUM_PYTHON_XML_OUTPUT
EXPLORER_EVENT_LOG
EXPLORER_SUMMARY_LOG
APPLICATION_CRASH_REPORT
XCTEST_LOG
VIDEO
CUSTOMER_ARTIFACT
CUSTOMER_ARTIFACT_LOG
TESTSPEC_OUTPUT
APPIUM_SERVER_OUTPUT
APPIUM_JAVA_OUTPUT
APPIUM_JAVA_XML_OUTPUT
APPIUM_PYTHON_OUTPUT
APPIUM_PYTHON_XML_OUTPUT
APPLICATION_CRASH_REPORT
XCTEST_LOG
VIDEO
CUSTOMER_ARTIFACT
CUSTOMER_ARTIFACT_LOG
TESTSPEC_OUTPUT
APPIUM_WEB_JAVA_TESTNG_TEST_PACKAGE
APPIUM_WEB_PYTHON_TEST_PACKAGE
APPIUM_WEB_NODE_TEST_PACKAGE
APPIUM_WEB_RUBY_TEST_PACKAGE
CALABASH_TEST_PACKAGE
- *INSTRUMENTATION_TEST_PACKAGE
UIAUTOMATION_TEST_PACKAGE
UIAUTOMATOR_TEST_PACKAGE
- *XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
- *APPIUM_JAVA_JUNIT_TEST_SPEC
APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
- *APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
- *APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_RUBY_TEST_PACKAGE
INSTRUMENTATION_TEST_PACKAGE
XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
APPIUM_JAVA_JUNIT_TEST_SPEC
+ *APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_JAVA_TESTNG_TEST_SPEC
APPIUM_WEB_PYTHON_TEST_SPEC
APPIUM_WEB_NODE_TEST_SPEC
*APPIUM_WEB_RUBY_TEST_SPEC
The test type for the specified device pool.
Allowed values include * the following:
BUILTIN_FUZZ.
BUILTIN_EXPLORER. For Android, an app explorer that traverses an Android app, - * interacting with it and capturing screenshots at the same time.
APPIUM_JAVA_JUNIT.
APPIUM_JAVA_TESTNG.
APPIUM_PYTHON.
APPIUM_NODE.
APPIUM_RUBY.
APPIUM_WEB_JAVA_JUNIT.
APPIUM_WEB_JAVA_TESTNG.
APPIUM_WEB_PYTHON.
APPIUM_WEB_NODE.
APPIUM_WEB_RUBY.
CALABASH.
INSTRUMENTATION.
UIAUTOMATION.
UIAUTOMATOR.
XCTEST.
- *XCTEST_UI.
INSTRUMENTATION.
XCTEST.
XCTEST_UI.
+ *The job's type.
Allowed values include the following:
BUILTIN_FUZZ
BUILTIN_EXPLORER. For Android, an app explorer - * that traverses an Android app, interacting with it and capturing screenshots at - * the same time.
APPIUM_JAVA_JUNIT
BUILTIN_FUZZ
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
CALABASH
INSTRUMENTATION
UIAUTOMATION
UIAUTOMATOR
XCTEST
XCTEST_UI
APPIUM_WEB_RUBY
INSTRUMENTATION
XCTEST
XCTEST_UI
APPIUM_WEB_JAVA_TESTNG_TEST_PACKAGE
APPIUM_WEB_PYTHON_TEST_PACKAGE
APPIUM_WEB_NODE_TEST_PACKAGE
APPIUM_WEB_RUBY_TEST_PACKAGE
CALABASH_TEST_PACKAGE
- *INSTRUMENTATION_TEST_PACKAGE
UIAUTOMATION_TEST_PACKAGE
UIAUTOMATOR_TEST_PACKAGE
- *XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
- *APPIUM_JAVA_JUNIT_TEST_SPEC
APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
- *APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
- *APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_RUBY_TEST_PACKAGE
INSTRUMENTATION_TEST_PACKAGE
XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
APPIUM_JAVA_JUNIT_TEST_SPEC
+ *APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_JAVA_TESTNG_TEST_SPEC
APPIUM_WEB_PYTHON_TEST_SPEC
APPIUM_WEB_NODE_TEST_SPEC
*APPIUM_WEB_RUBY_TEST_SPEC
The run's type.
Must be one of the following values:
BUILTIN_FUZZ
BUILTIN_EXPLORER
For Android, an - * app explorer that traverses an Android app, interacting with it and capturing - * screenshots at the same time.
APPIUM_JAVA_JUNIT
- *APPIUM_JAVA_TESTNG
APPIUM_PYTHON
BUILTIN_FUZZ
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
CALABASH
INSTRUMENTATION
UIAUTOMATION
UIAUTOMATOR
XCTEST
XCTEST_UI
APPIUM_WEB_RUBY
INSTRUMENTATION
XCTEST
XCTEST_UI
The test's type.
Must be one of the following values:
BUILTIN_FUZZ
BUILTIN_EXPLORER. For Android, an app explorer - * that traverses an Android app, interacting with it and capturing screenshots at - * the same time.
APPIUM_JAVA_JUNIT
BUILTIN_FUZZ
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
CALABASH
INSTRUMENTATION
UIAUTOMATION
UIAUTOMATOR
XCTEST
XCTEST_UI
APPIUM_WEB_RUBY
INSTRUMENTATION
XCTEST
XCTEST_UI
For * all tests:
app_performance_monitoring
:
* Performance monitoring is enabled by default. Set this parameter to false to
- * disable it.
For Calabash tests:
profile: A
- * cucumber profile (for example, my_profile_name
).
tags: You can limit execution to features or scenarios that have (or don't - * have) certain tags (for example, @smoke or @smoke,~@wip).
For - * Appium tests (all types):
appium_version: The Appium version. - * Currently supported values are 1.6.5 (and later), latest, and default.
latest runs the latest Appium version supported by Device Farm - * (1.9.1).
For default, Device Farm selects a compatible version - * of Appium for the device. The current behavior is to run 1.7.2 on Android - * devices and iOS 9 and earlier and 1.7.2 for iOS 10 and later.
This behavior is subject to change.
For fuzz - * tests (Android only):
event_count: The number of events, - * between 1 and 10000, that the UI fuzz test should perform.
throttle: The time, in ms, between 0 and 1000, that the UI fuzz test should - * wait between events.
seed: A seed to use for randomizing the - * UI fuzz test. Using the same seed value between tests ensures identical event - * sequences.
For Explorer tests:
username: A - * user name to use if the Explorer encounters a login form. If not supplied, no - * user name is inserted.
password: A password to use if the - * Explorer encounters a login form. If not supplied, no password is inserted.
- *For Instrumentation:
filter: A test filter - * string. Examples:
Running a single test case:
- * com.android.abc.Test1
Running a single test:
- * com.android.abc.Test1#smoke
Running multiple
- * tests: com.android.abc.Test1,com.android.abc.Test2
For XCTest and XCTestUI:
filter: A test filter - * string. Examples:
Running a single test class: + * disable it.
For Appium tests (all types):
appium_version: The Appium version. Currently supported values are 1.6.5 (and + * later), latest, and default.
latest runs the latest Appium + * version supported by Device Farm (1.9.1).
For default, Device + * Farm selects a compatible version of Appium for the device. The current behavior + * is to run 1.7.2 on Android devices and iOS 9 and earlier and 1.7.2 for iOS 10 + * and later.
This behavior is subject to change.
For fuzz tests (Android only):
event_count: The + * number of events, between 1 and 10000, that the UI fuzz test should perform.
+ *throttle: The time, in ms, between 0 and 1000, that the UI fuzz + * test should wait between events.
seed: A seed to use for + * randomizing the UI fuzz test. Using the same seed value between tests ensures + * identical event sequences.
For Instrumentation:
filter: A test filter string. Examples:
Running a single
+ * test case: com.android.abc.Test1
Running a
+ * single test: com.android.abc.Test1#smoke
Running
+ * multiple tests: com.android.abc.Test1,com.android.abc.Test2
For XCTest and XCTestUI:
filter: A + * test filter string. Examples:
Running a single test class:
* LoginTests
Running a multiple test classes:
* LoginTests,SmokeTests
Running a single test:
* LoginTests/testValid
Running multiple tests:
* LoginTests/testValid,LoginTests/testInvalid
For UIAutomator:
filter: A test filter string. - * Examples:
Running a single test case:
- * com.android.abc.Test1
Running a single test:
- * com.android.abc.Test1#smoke
Running multiple
- * tests: com.android.abc.Test1,com.android.abc.Test2
The suite's type.
Must be one of the following values:
BUILTIN_FUZZ
BUILTIN_EXPLORER
Only available - * for Android; an app explorer that traverses an Android app, interacting with it - * and capturing screenshots at the same time.
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
- *APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
- *APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
CALABASH
INSTRUMENTATION
UIAUTOMATION
UIAUTOMATOR
XCTEST
XCTEST_UI
BUILTIN_FUZZ
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
INSTRUMENTATION
XCTEST
XCTEST_UI
The test's type.
Must be one of the following values:
BUILTIN_FUZZ
BUILTIN_EXPLORER
For Android, an - * app explorer that traverses an Android app, interacting with it and capturing - * screenshots at the same time.
APPIUM_JAVA_JUNIT
- *APPIUM_JAVA_TESTNG
APPIUM_PYTHON
BUILTIN_FUZZ
APPIUM_JAVA_JUNIT
APPIUM_JAVA_TESTNG
APPIUM_PYTHON
APPIUM_NODE
APPIUM_RUBY
APPIUM_WEB_JAVA_JUNIT
APPIUM_WEB_JAVA_TESTNG
APPIUM_WEB_PYTHON
APPIUM_WEB_NODE
APPIUM_WEB_RUBY
CALABASH
INSTRUMENTATION
UIAUTOMATION
UIAUTOMATOR
XCTEST
XCTEST_UI
APPIUM_WEB_RUBY
INSTRUMENTATION
XCTEST
XCTEST_UI
APPIUM_WEB_JAVA_TESTNG_TEST_PACKAGE
APPIUM_WEB_PYTHON_TEST_PACKAGE
APPIUM_WEB_NODE_TEST_PACKAGE
APPIUM_WEB_RUBY_TEST_PACKAGE
CALABASH_TEST_PACKAGE
- *INSTRUMENTATION_TEST_PACKAGE
UIAUTOMATION_TEST_PACKAGE
UIAUTOMATOR_TEST_PACKAGE
- *XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
- *APPIUM_JAVA_JUNIT_TEST_SPEC
APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
- *APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
- *APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_RUBY_TEST_PACKAGE
INSTRUMENTATION_TEST_PACKAGE
XCTEST_TEST_PACKAGE
XCTEST_UI_TEST_PACKAGE
APPIUM_JAVA_JUNIT_TEST_SPEC
+ *APPIUM_JAVA_TESTNG_TEST_SPEC
APPIUM_PYTHON_TEST_SPEC
APPIUM_NODE_TEST_SPEC
APPIUM_RUBY_TEST_SPEC
APPIUM_WEB_JAVA_JUNIT_TEST_SPEC
APPIUM_WEB_JAVA_TESTNG_TEST_SPEC
APPIUM_WEB_PYTHON_TEST_SPEC
APPIUM_WEB_NODE_TEST_SPEC
*APPIUM_WEB_RUBY_TEST_SPEC
Registers an AMI. When you're creating an instance-store backed AMI, * registering the AMI is the final step in the creation process. For more * information about creating AMIs, see Create - * your own AMI in the Amazon Elastic Compute Cloud User Guide.
- *For Amazon EBS-backed instances, CreateImage creates and - * registers the AMI in a single request, so you don't have to register the AMI - * yourself. We recommend that you always use CreateImage unless you have a - * specific reason to use RegisterImage.
If needed, you can - * deregister an AMI at any time. Any modifications you make to an AMI backed by an - * instance store volume invalidates its registration. If you make changes to an - * image, deregister the previous image and register the new image.
- * Register a snapshot of a root device volume
You can use
- * RegisterImage
to create an Amazon EBS-backed Linux AMI from a
- * snapshot of a root device volume. You specify the snapshot using a block device
- * mapping. You can't set the encryption state of the volume using the block device
- * mapping. If the snapshot is encrypted, or encryption by default is enabled, the
- * root volume of an instance launched from the AMI is encrypted.
For more - * information, see Create - * a Linux AMI from a snapshot and and Create + * an instance-store backed AMI in the Amazon EC2 User Guide.
+ *For Amazon EBS-backed instances, CreateImage creates and registers the + * AMI in a single request, so you don't have to register the AMI yourself. We + * recommend that you always use CreateImage unless you have a specific + * reason to use RegisterImage.
If needed, you can deregister an AMI + * at any time. Any modifications you make to an AMI backed by an instance store + * volume invalidates its registration. If you make changes to an image, deregister + * the previous image and register the new image.
Register a snapshot of + * a root device volume
You can use RegisterImage
to
+ * create an Amazon EBS-backed Linux AMI from a snapshot of a root device volume.
+ * You specify the snapshot using a block device mapping. You can't set the
+ * encryption state of the volume using the block device mapping. If the snapshot
+ * is encrypted, or encryption by default is enabled, the root volume of an
+ * instance launched from the AMI is encrypted.
For more information, see Create + * an AMI from a snapshot and Use - * encryption with Amazon EBS-backed AMIs in the Amazon Elastic Compute - * Cloud User Guide.
Amazon Web Services Marketplace product - * codes
If any snapshots have Amazon Web Services Marketplace product - * codes, they are copied to the new AMI.
Windows and some Linux - * distributions, such as Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise - * Server (SLES), use the Amazon EC2 billing product code associated with an AMI to - * verify the subscription status for package updates. To create a new AMI for - * operating systems that require a billing product code, instead of registering - * the AMI, do the following to preserve the billing product code association:
- *Launch an instance from an existing AMI with that billing product - * code.
Customize the instance.
Create an AMI - * from the instance using CreateImage.
If you purchase a - * Reserved Instance to apply to an On-Demand Instance that was launched from an - * AMI with a billing product code, make sure that the Reserved Instance has the - * matching billing product code. If you purchase a Reserved Instance without the - * matching billing product code, the Reserved Instance will not be applied to the - * On-Demand Instance. For information about how to obtain the platform details and - * billing information of an AMI, see in the Amazon EC2 User + * Guide.
Amazon Web Services Marketplace product codes
+ *If any snapshots have Amazon Web Services Marketplace product codes, they are + * copied to the new AMI.
In most cases, AMIs for Windows, RedHat, SUSE, and
+ * SQL Server require correct licensing information to be present on the AMI. For
+ * more information, see Understand
+ * AMI billing information in the Amazon EC2 User Guide. When creating
+ * an AMI from a snapshot, the RegisterImage
operation derives the
+ * correct billing information from the snapshot's metadata, but this requires the
+ * appropriate metadata to be present. To verify if the correct billing information
+ * was applied, check the PlatformDetails
field on the new AMI. If the
+ * field is empty or doesn't match the expected operating system code (for example,
+ * Windows, RedHat, SUSE, or SQL), the AMI creation was unsuccessful, and you
+ * should discard the AMI and instead create the AMI from an instance using
+ * CreateImage. For more information, see Create
+ * an AMI from an instance in the Amazon EC2 User Guide.
If you + * purchase a Reserved Instance to apply to an On-Demand Instance that was launched + * from an AMI with a billing product code, make sure that the Reserved Instance + * has the matching billing product code. If you purchase a Reserved Instance + * without the matching billing product code, the Reserved Instance will not be + * applied to the On-Demand Instance. For information about how to obtain the + * platform details and billing information of an AMI, see Understand * AMI billing information in the Amazon EC2 User Guide.
TOP_LOCATION_DETAILS
: Provides TTFB for Amazon CloudFront, your
* current configuration, and the best performing EC2 configuration, at 1 hour
- * intervals.
For lists of the fields returned with each query
- * type and more information about how each type of query is performed, see
+ * For lists of the fields returned with each query type and more information
+ * about how each type of query is performed, see
* Using the Amazon CloudWatch Internet Monitor query interface in the Amazon
* CloudWatch Internet Monitor User Guide. Amazon Web Services Parallel Computing Service (Amazon Web Services PCS) is a
+ * managed service that makes it easier for you to run and scale your high
+ * performance computing (HPC) workloads, and build scientific and engineering
+ * models on Amazon Web Services using Slurm. For more information, see the Amazon Web Services
+ * Parallel Computing Service User Guide. This reference describes the
+ * actions and data types of the service management API. You can use the Amazon Web
+ * Services SDKs to call the API actions in software, or use the Command Line
+ * Interface (CLI) to call the API actions manually. These API actions manage the
+ * service through an Amazon Web Services account. The API actions operate
+ * on Amazon Web Services PCS resources. A resource is an entity in Amazon
+ * Web Services that you can work with. Amazon Web Services services create
+ * resources when you use the features of the service. Examples of Amazon Web
+ * Services PCS resources include clusters, compute node groups, and queues. For
+ * more information about resources in Amazon Web Services, see Resource
+ * in the Resource Explorer User Guide. An Amazon Web Services PCS
+ * compute node is an Amazon EC2 instance. You don't launch compute nodes
+ * directly. Amazon Web Services PCS uses configuration information that you
+ * provide to launch compute nodes in your Amazon Web Services account. You receive
+ * billing charges for your running compute nodes. Amazon Web Services PCS
+ * automatically terminates your compute nodes when you delete the Amazon Web
+ * Services PCS resources related to those compute nodes. Creates a cluster in your account. Amazon Web Services PCS creates the
+ * cluster controller in a service-owned account. The cluster controller
+ * communicates with the cluster resources in your account. The subnets and
+ * security groups for the cluster must already exist before you use this API
+ * action. It takes time for Amazon Web Services PCS to create the
+ * cluster. The cluster is in a OVERALL_TRAFFIC_SUGGESTIONS
: Provides
+ * TTFB, using a 30-day weighted average, for all traffic in each Amazon Web
+ * Services location that is monitored.OVERALL_TRAFFIC_SUGGESTIONS_DETAILS
: Provides TTFB, using a 30-day
+ * weighted average, for each top location, for a proposed Amazon Web Services
+ * location. Must provide a Amazon Web Services location to search.Creating
state until it is ready to
+ * use. There can only be 1 cluster in a Creating
state per Amazon Web
+ * Services Region per Amazon Web Services account. CreateCluster
+ * fails with a ServiceQuotaExceededException
if there is already a
+ * cluster in a Creating
state.See Also:
AWS
+ * API Reference
Creates a managed set of compute nodes. You associate a compute node group + * with a cluster through 1 or more Amazon Web Services PCS queues or as part of + * the login fleet. A compute node group includes the definition of the compute + * properties and lifecycle management. Amazon Web Services PCS uses the + * information you provide to this API action to launch compute nodes in your + * account. You can only specify subnets in the same Amazon VPC as your cluster. + * You receive billing charges for the compute nodes that Amazon Web Services PCS + * launches in your account. You must already have a launch template before you + * call this API. For more information, see Launch + * an instance from a launch template in the Amazon Elastic Compute Cloud + * User Guide for Linux Instances.
Creates a job queue. You must associate 1 or more compute node groups with + * the queue. You can associate 1 compute node group with multiple + * queues.
Deletes a cluster and all its linked resources. You must delete all queues + * and compute node groups associated with the cluster before you can delete the + * cluster.
Deletes a compute node group. You must delete all queues associated with the + * compute node group first.
Deletes a job queue. If the compute node group associated with this queue + * isn't associated with any other queues, Amazon Web Services PCS terminates all + * the compute nodes for this queue.
Returns detailed information about a running cluster in your account. This + * API action provides networking information, endpoint information for + * communication with the scheduler, and provisioning status.
Returns detailed information about a compute node group. This API action + * provides networking information, EC2 instance type, compute node group status, + * and scheduler (such as Slurm) configuration.
Returns detailed information about a queue. The information includes the + * compute node groups that the queue uses to schedule jobs.
Returns a list of running clusters in your account.
Returns a list of all compute node groups associated with a + * cluster.
Returns a list of all queues associated with a cluster.
Returns a list of all tags on an Amazon Web Services PCS + * resource.
This API action isn't intended for you to use.
+ *Amazon Web Services PCS uses this API action to register the compute nodes it + * launches in your account.
Adds or edits tags on an Amazon Web Services PCS resource. Each tag consists + * of a tag key and a tag value. The tag key and tag value are case-sensitive + * strings. The tag value can be an empty (null) string. To add a tag, specify a + * new tag key and a tag value. To edit a tag, specify an existing tag key and a + * new tag value.
Deletes tags from an Amazon Web Services PCS resource. To delete a tag, + * specify the tag key and the Amazon Resource Name (ARN) of the Amazon Web + * Services PCS resource.
Updates a compute node group. You can update many of the fields related to + * your compute node group including the configurations for networking, compute + * nodes, and settings specific to your scheduler (such as Slurm).
Updates the compute node group configuration of a queue. Use this API to + * change the compute node groups that the queue can send jobs to.