@pulumi/aws 6.6.0-alpha.1697624191 → 6.6.1

package/neptune/globalCluster.d.ts

@@ -81,7 +81,7 @@ import * as outputs from "../types/output";
  * ```sh
  *  $ pulumi import aws:neptune/globalCluster:GlobalCluster example example
  * ```
- *  Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 export declare class GlobalCluster extends pulumi.CustomResource {
     /**

package/neptune/globalCluster.js

@@ -85,7 +85,7 @@ const utilities = require("../utilities");
  * ```sh
  *  $ pulumi import aws:neptune/globalCluster:GlobalCluster example example
  * ```
- *  Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 class GlobalCluster extends pulumi.CustomResource {
     /**

package/organizations/account.d.ts

@@ -22,7 +22,7 @@ import * as pulumi from "@pulumi/pulumi";
  * ```sh
  *  $ pulumi import aws:organizations/account:Account my_account 111111111111
  * ```
- *  Certain resource arguments, like `role_name`, do not have an Organizations API method for reading the information after account creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `role_name`, do not have an Organizations API method for reading the information after account creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 export declare class Account extends pulumi.CustomResource {
     /**

package/organizations/account.js

@@ -28,7 +28,7 @@ const utilities = require("../utilities");
  * ```sh
  *  $ pulumi import aws:organizations/account:Account my_account 111111111111
  * ```
- *  Certain resource arguments, like `role_name`, do not have an Organizations API method for reading the information after account creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `role_name`, do not have an Organizations API method for reading the information after account creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 class Account extends pulumi.CustomResource {
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@pulumi/aws",
-    "version": "v6.6.0-alpha.1697624191+ac5e1355",
+    "version": "v6.6.1",
     "description": "A Pulumi package for creating and managing Amazon Web Services (AWS) cloud resources.",
     "keywords": [
         "pulumi",

package/pinpoint/app.d.ts

@@ -62,7 +62,7 @@ export declare class App extends pulumi.CustomResource {
      */
     readonly limits: pulumi.Output<outputs.pinpoint.AppLimits | undefined>;
     /**
-     * The application name. By default generated by TODO
+     * The application name. By default generated by Pulumi
      */
     readonly name: pulumi.Output<string>;
     /**
@@ -117,7 +117,7 @@ export interface AppState {
      */
     limits?: pulumi.Input<inputs.pinpoint.AppLimits>;
     /**
-     * The application name. By default generated by TODO
+     * The application name. By default generated by Pulumi
      */
     name?: pulumi.Input<string>;
     /**
@@ -156,7 +156,7 @@ export interface AppArgs {
      */
     limits?: pulumi.Input<inputs.pinpoint.AppLimits>;
     /**
-     * The application name. By default generated by TODO
+     * The application name. By default generated by Pulumi
      */
     name?: pulumi.Input<string>;
     /**

package/ram/resourceShareAccepter.d.ts

@@ -6,7 +6,7 @@ import * as pulumi from "@pulumi/pulumi";
  *
  * ## Example Usage
  *
- * This configuration provides an example of using multiple TODO AWS providers to configure two different AWS accounts. In the _sender_ account, the configuration creates a `aws.ram.ResourceShare` and uses a data source in the _receiver_ account to create a `aws.ram.PrincipalAssociation` resource with the _receiver's_ account ID. In the _receiver_ account, the configuration accepts the invitation to share resources with the `aws.ram.ResourceShareAccepter`.
+ * This configuration provides an example of using multiple AWS providers to configure two different AWS accounts. In the _sender_ account, the configuration creates a `aws.ram.ResourceShare` and uses a data source in the _receiver_ account to create a `aws.ram.PrincipalAssociation` resource with the _receiver's_ account ID. In the _receiver_ account, the configuration accepts the invitation to share resources with the `aws.ram.ResourceShareAccepter`.
  *
  * ```typescript
  * import * as pulumi from "@pulumi/pulumi";

package/ram/resourceShareAccepter.js

@@ -12,7 +12,7 @@ const utilities = require("../utilities");
  *
  * ## Example Usage
  *
- * This configuration provides an example of using multiple TODO AWS providers to configure two different AWS accounts. In the _sender_ account, the configuration creates a `aws.ram.ResourceShare` and uses a data source in the _receiver_ account to create a `aws.ram.PrincipalAssociation` resource with the _receiver's_ account ID. In the _receiver_ account, the configuration accepts the invitation to share resources with the `aws.ram.ResourceShareAccepter`.
+ * This configuration provides an example of using multiple AWS providers to configure two different AWS accounts. In the _sender_ account, the configuration creates a `aws.ram.ResourceShare` and uses a data source in the _receiver_ account to create a `aws.ram.PrincipalAssociation` resource with the _receiver's_ account ID. In the _receiver_ account, the configuration accepts the invitation to share resources with the `aws.ram.ResourceShareAccepter`.
  *
  * ```typescript
  * import * as pulumi from "@pulumi/pulumi";

package/rds/clusterParameterGroup.d.ts

@@ -58,7 +58,7 @@ export declare class ClusterParameterGroup extends pulumi.CustomResource {
      */
     readonly arn: pulumi.Output<string>;
     /**
-     * The description of the DB cluster parameter group. Defaults to "Managed by TODO".
+     * The description of the DB cluster parameter group. Defaults to "Managed by Pulumi".
      */
     readonly description: pulumi.Output<string>;
     /**
@@ -109,7 +109,7 @@ export interface ClusterParameterGroupState {
      */
     arn?: pulumi.Input<string>;
     /**
-     * The description of the DB cluster parameter group. Defaults to "Managed by TODO".
+     * The description of the DB cluster parameter group. Defaults to "Managed by Pulumi".
      */
     description?: pulumi.Input<string>;
     /**
@@ -148,7 +148,7 @@ export interface ClusterParameterGroupState {
  */
 export interface ClusterParameterGroupArgs {
     /**
-     * The description of the DB cluster parameter group. Defaults to "Managed by TODO".
+     * The description of the DB cluster parameter group. Defaults to "Managed by Pulumi".
      */
     description?: pulumi.Input<string>;
     /**

package/rds/globalCluster.d.ts

@@ -178,7 +178,7 @@ import * as outputs from "../types/output";
  * ```
  *  Certain resource arguments, like `force_destroy`, only exist within this provider. If the argument is set in the the provider configuration on an imported resource, This provider will show a difference on the first plan after import to update the state value. This change is safe to apply immediately so the state matches the desired configuration.
  *
- * Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ * Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 export declare class GlobalCluster extends pulumi.CustomResource {
     /**

package/rds/globalCluster.js

@@ -182,7 +182,7 @@ const utilities = require("../utilities");
  * ```
  *  Certain resource arguments, like `force_destroy`, only exist within this provider. If the argument is set in the the provider configuration on an imported resource, This provider will show a difference on the first plan after import to update the state value. This change is safe to apply immediately so the state matches the desired configuration.
  *
- * Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ * Certain resource arguments, like `source_db_cluster_identifier`, do not have an API method for reading the information after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 class GlobalCluster extends pulumi.CustomResource {
     /**

package/route53/zoneAssociation.d.ts

@@ -33,16 +33,16 @@ import * as pulumi from "@pulumi/pulumi";
  *
  * ## Import
  *
- * The VPC is _not_ in the same region where you have configured the TODO AWS Provider:
+ * The VPC is _not_ in the same region where you have configured the AWS Provider:
  *
  * __Using `pulumi import` to import__ Route 53 Hosted Zone Associations using the Hosted Zone ID and VPC ID, separated by a colon (`:`). For example:
  *
- * The VPC is in the same region where you have configured the TODO AWS Provider:
+ * The VPC is in the same region where you have configured the AWS Provider:
  *
  * ```sh
  *  $ pulumi import aws:route53/zoneAssociation:ZoneAssociation example Z123456ABCDEFG:vpc-12345678
  * ```
- *  The VPC is _not_ in the same region where you have configured the TODO AWS Provider:
+ *  The VPC is _not_ in the same region where you have configured the AWS Provider:
  *
  * ```sh
  *  $ pulumi import aws:route53/zoneAssociation:ZoneAssociation example Z123456ABCDEFG:vpc-12345678:us-east-2

package/route53/zoneAssociation.js

@@ -39,16 +39,16 @@ const utilities = require("../utilities");
  *
  * ## Import
  *
- * The VPC is _not_ in the same region where you have configured the TODO AWS Provider:
+ * The VPC is _not_ in the same region where you have configured the AWS Provider:
  *
  * __Using `pulumi import` to import__ Route 53 Hosted Zone Associations using the Hosted Zone ID and VPC ID, separated by a colon (`:`). For example:
  *
- * The VPC is in the same region where you have configured the TODO AWS Provider:
+ * The VPC is in the same region where you have configured the AWS Provider:
  *
  * ```sh
  *  $ pulumi import aws:route53/zoneAssociation:ZoneAssociation example Z123456ABCDEFG:vpc-12345678
  * ```
- *  The VPC is _not_ in the same region where you have configured the TODO AWS Provider:
+ *  The VPC is _not_ in the same region where you have configured the AWS Provider:
  *
  * ```sh
  *  $ pulumi import aws:route53/zoneAssociation:ZoneAssociation example Z123456ABCDEFG:vpc-12345678:us-east-2

package/s3/bucketLifecycleConfigurationV2.d.ts

@@ -15,7 +15,7 @@ import * as outputs from "../types/output";
  * > **NOTE:** S3 Buckets only support a single lifecycle configuration. Declaring multiple `aws.s3.BucketLifecycleConfigurationV2` resources to the same S3 Bucket will cause a perpetual difference in configuration.
  *
  * > **NOTE:** Lifecycle configurations may take some time to fully propagate to all AWS S3 systems.
- * Running TODO operations shortly after creating a lifecycle configuration may result in changes that affect configuration idempotence.
+ * Running Pulumi operations shortly after creating a lifecycle configuration may result in changes that affect configuration idempotence.
  * See the Amazon S3 User Guide on [setting lifecycle configuration on a bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-set-lifecycle-configuration-intro.html).
  *
  * ## Example Usage

package/s3/bucketLifecycleConfigurationV2.js

@@ -19,7 +19,7 @@ const utilities = require("../utilities");
  * > **NOTE:** S3 Buckets only support a single lifecycle configuration. Declaring multiple `aws.s3.BucketLifecycleConfigurationV2` resources to the same S3 Bucket will cause a perpetual difference in configuration.
  *
  * > **NOTE:** Lifecycle configurations may take some time to fully propagate to all AWS S3 systems.
- * Running TODO operations shortly after creating a lifecycle configuration may result in changes that affect configuration idempotence.
+ * Running Pulumi operations shortly after creating a lifecycle configuration may result in changes that affect configuration idempotence.
  * See the Amazon S3 User Guide on [setting lifecycle configuration on a bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-set-lifecycle-configuration-intro.html).
  *
  * ## Example Usage

package/scheduler/schedule.d.ts

@@ -75,7 +75,7 @@ export declare class Schedule extends pulumi.CustomResource {
      */
     static isInstance(obj: any): obj is Schedule;
     /**
-     * ARN of the target of this schedule, such as a SQS queue or ECS cluster. For universal targets, this is a [Service ARN specific to the target service](https://docs.aws.amazon.com/scheduler/latest/UserGuide/managing-targets-universal.html#supported-universal-targets).
+     * ARN of the SQS queue specified as the destination for the dead-letter queue.
      */
     readonly arn: pulumi.Output<string>;
     /**
@@ -142,7 +142,7 @@ export declare class Schedule extends pulumi.CustomResource {
  */
 export interface ScheduleState {
     /**
-     * ARN of the target of this schedule, such as a SQS queue or ECS cluster. For universal targets, this is a [Service ARN specific to the target service](https://docs.aws.amazon.com/scheduler/latest/UserGuide/managing-targets-universal.html#supported-universal-targets).
+     * ARN of the SQS queue specified as the destination for the dead-letter queue.
      */
     arn?: pulumi.Input<string>;
     /**

package/securityhub/organizationConfiguration.d.ts

@@ -2,9 +2,9 @@ import * as pulumi from "@pulumi/pulumi";
 /**
  * Manages the Security Hub Organization Configuration.
  *
- * > **NOTE:** This resource requires an `aws.securityhub.OrganizationAdminAccount` to be configured (not necessarily with TODO). More information about managing Security Hub in an organization can be found in the [Managing administrator and member accounts](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-accounts.html) documentation
+ * > **NOTE:** This resource requires an `aws.securityhub.OrganizationAdminAccount` to be configured (not necessarily with Pulumi). More information about managing Security Hub in an organization can be found in the [Managing administrator and member accounts](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-accounts.html) documentation
  *
- * > **NOTE:** This is an advanced TODO resource. TODO will automatically assume management of the Security Hub Organization Configuration without import and perform no actions on removal from the TODO configuration.
+ * > **NOTE:** This is an advanced AWS resource. Pulumi will automatically assume management of the Security Hub Organization Configuration without import and perform no actions on removal from the Pulumi program.
  *
  * ## Example Usage
  *

package/securityhub/organizationConfiguration.js

@@ -8,9 +8,9 @@ const utilities = require("../utilities");
 /**
  * Manages the Security Hub Organization Configuration.
  *
- * > **NOTE:** This resource requires an `aws.securityhub.OrganizationAdminAccount` to be configured (not necessarily with TODO). More information about managing Security Hub in an organization can be found in the [Managing administrator and member accounts](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-accounts.html) documentation
+ * > **NOTE:** This resource requires an `aws.securityhub.OrganizationAdminAccount` to be configured (not necessarily with Pulumi). More information about managing Security Hub in an organization can be found in the [Managing administrator and member accounts](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-accounts.html) documentation
  *
- * > **NOTE:** This is an advanced TODO resource. TODO will automatically assume management of the Security Hub Organization Configuration without import and perform no actions on removal from the TODO configuration.
+ * > **NOTE:** This is an advanced AWS resource. Pulumi will automatically assume management of the Security Hub Organization Configuration without import and perform no actions on removal from the Pulumi program.
  *
  * ## Example Usage
  *

package/securityhub/standardsControl.d.ts

@@ -3,8 +3,8 @@ import * as pulumi from "@pulumi/pulumi";
  * Disable/enable Security Hub standards control in the current region.
  *
  * The `aws.securityhub.StandardsControl` behaves differently from normal resources, in that
- * TODO does not _create_ this resource, but instead "adopts" it
- * into management. When you _delete_ this resource configuration, TODO "abandons" resource as is and just removes it from the state.
+ * Pulumi does not _create_ this resource, but instead "adopts" it
+ * into management. When you _delete_ this resource configuration, Pulumi "abandons" resource as is and just removes it from the state.
  *
  * ## Example Usage
  *

package/securityhub/standardsControl.js

@@ -9,8 +9,8 @@ const utilities = require("../utilities");
  * Disable/enable Security Hub standards control in the current region.
  *
  * The `aws.securityhub.StandardsControl` behaves differently from normal resources, in that
- * TODO does not _create_ this resource, but instead "adopts" it
- * into management. When you _delete_ this resource configuration, TODO "abandons" resource as is and just removes it from the state.
+ * Pulumi does not _create_ this resource, but instead "adopts" it
+ * into management. When you _delete_ this resource configuration, Pulumi "abandons" resource as is and just removes it from the state.
  *
  * ## Example Usage
  *

package/ssm/document.d.ts

@@ -77,7 +77,7 @@ import * as outputs from "../types/output";
  * ```sh
  *  $ pulumi import aws:ssm/document:Document example example
  * ```
- *  The `attachments_source` argument does not have an SSM API method for reading the attachment information detail after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  The `attachments_source` argument does not have an SSM API method for reading the attachment information detail after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 export declare class Document extends pulumi.CustomResource {
     /**

package/ssm/document.js

@@ -81,7 +81,7 @@ const utilities = require("../utilities");
  * ```sh
  *  $ pulumi import aws:ssm/document:Document example example
  * ```
- *  The `attachments_source` argument does not have an SSM API method for reading the attachment information detail after creation. If the argument is set in the TODO configuration on an imported resource, TODO will always show a difference. To workaround this behavior, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  The `attachments_source` argument does not have an SSM API method for reading the attachment information detail after creation. If the argument is set in the Pulumi program on an imported resource, Pulumi will always show a difference. To workaround this behavior, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 class Document extends pulumi.CustomResource {
     /**

package/storagegateway/gateway.d.ts

@@ -107,7 +107,7 @@ import * as outputs from "../types/output";
  * ```sh
  *  $ pulumi import aws:storagegateway/gateway:Gateway example arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12345678
  * ```
- *  Certain resource arguments, like `gateway_ip_address` do not have a Storage Gateway API method for reading the information after creation, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `gateway_ip_address` do not have a Storage Gateway API method for reading the information after creation, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 export declare class Gateway extends pulumi.CustomResource {
     /**

package/storagegateway/gateway.js

@@ -111,7 +111,7 @@ const utilities = require("../utilities");
  * ```sh
  *  $ pulumi import aws:storagegateway/gateway:Gateway example arn:aws:storagegateway:us-east-1:123456789012:gateway/sgw-12345678
  * ```
- *  Certain resource arguments, like `gateway_ip_address` do not have a Storage Gateway API method for reading the information after creation, either omit the argument from the TODO configuration or use `ignore_changes` to hide the difference. For example:
+ *  Certain resource arguments, like `gateway_ip_address` do not have a Storage Gateway API method for reading the information after creation, either omit the argument from the Pulumi program or use `ignore_changes` to hide the difference. For example:
  */
 class Gateway extends pulumi.CustomResource {
     /**