Package com.pulumi.aws.ssmincidents

Class ReplicationSetArgs

  • public final class ReplicationSetArgs
extends com.pulumi.resources.ResourceArgs

    • Method Detail

      • region

        @Deprecated
public java.util.Optional<com.pulumi.core.Output<java.util.List<ReplicationSetRegionArgs>>> region()
        Deprecated.
        region is deprecated. Use regions instead.
        Returns:
        The replication set's Regions. Use `regions` instead.

      • regions

        public java.util.Optional<com.pulumi.core.Output<java.util.List<ReplicationSetRegionArgs>>> regions()
        Returns:
        The replication set's Regions.

      • tags

        public java.util.Optional<com.pulumi.core.Output<java.util.Map<java.lang.String,​java.lang.String>>> tags()
        Returns:
        Key-value map of resource tags. If configured with a provider `defaultTags` configuration block present, tags with matching keys will overwrite those defined at the provider-level. For information about the maximum allowed number of Regions and tag value constraints, see [CreateReplicationSet in the *AWS Systems Manager Incident Manager API Reference*](https://docs.aws.amazon.com/incident-manager/latest/APIReference/API_CreateReplicationSet.html). > **NOTE:** The Region specified by a provider must always be one of the Regions specified for the replication set. This is especially important when you perform complex update operations. > **NOTE:** After a replication set is created, you can add or delete only one Region at a time. > **NOTE:** Incident Manager does not support updating the customer managed key associated with a replication set. Instead, for a replication set with multiple Regions, you must first delete a Region from the replication set, then re-add it with a different customer managed key in separate deploy operations. For a replication set with only one Region, the entire replication set must be deleted and recreated. To do this, comment out the replication set and all response plans, and then run the deploy command to recreate the replication set with the new customer managed key. > **NOTE:** You must either use AWS-owned keys on all regions of a replication set, or customer managed keys. To change between an AWS owned key and a customer managed key, a replication set and it associated data must be deleted and recreated. > **NOTE:** If possible, create all the customer managed keys you need (using the deploy command) before you create the replication set, or create the keys and replication set in the same deploy command. Otherwise, to delete a replication set, you must run one deploy command to delete the replication set and another to delete the AWS KMS keys used by the replication set. Deleting the AWS KMS keys before deleting the replication set results in an error. In that case, you must manually reenable the deleted key using the AWS Management Console before you can delete the replication set.