Interface CreatePracticeRunConfigurationRequest.Builder

All Superinterfaces:
ArcZonalShiftRequest.Builder, AwsRequest.Builder, Buildable, CopyableBuilder<CreatePracticeRunConfigurationRequest.Builder,CreatePracticeRunConfigurationRequest>, SdkBuilder<CreatePracticeRunConfigurationRequest.Builder,CreatePracticeRunConfigurationRequest>, SdkPojo, SdkRequest.Builder
Enclosing class:
CreatePracticeRunConfigurationRequest
@Mutable @NotThreadSafe public static interface CreatePracticeRunConfigurationRequest.Builder extends ArcZonalShiftRequest.Builder, SdkPojo, CopyableBuilder<CreatePracticeRunConfigurationRequest.Builder,CreatePracticeRunConfigurationRequest>

  • Method Details

    • resourceIdentifier

      CreatePracticeRunConfigurationRequest.Builder resourceIdentifier(String resourceIdentifier)

      The identifier of the resource that Amazon Web Services shifts traffic for with a practice run zonal shift. The identifier is the Amazon Resource Name (ARN) for the resource.

      Amazon Application Recovery Controller currently supports enabling the following resources for zonal shift and zonal autoshift:

      Parameters:
      resourceIdentifier - The identifier of the resource that Amazon Web Services shifts traffic for with a practice run zonal shift. The identifier is the Amazon Resource Name (ARN) for the resource.

      Amazon Application Recovery Controller currently supports enabling the following resources for zonal shift and zonal autoshift:

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockedWindows

      CreatePracticeRunConfigurationRequest.Builder blockedWindows(Collection<String> blockedWindows)

      Optionally, you can block ARC from starting practice runs for specific windows of days and times.

      The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.

      For example, say you run business report summaries three days a week. For this scenario, you could set the following recurring days and times as blocked windows, for example: Mon:00:00-Mon:10:00 Wed-20:30-Wed:21:30 Fri-20:30-Fri:21:30.

      The blockedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Parameters:
      blockedWindows - Optionally, you can block ARC from starting practice runs for specific windows of days and times.

      The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.

      For example, say you run business report summaries three days a week. For this scenario, you could set the following recurring days and times as blocked windows, for example: Mon:00:00-Mon:10:00 Wed-20:30-Wed:21:30 Fri-20:30-Fri:21:30.

      The blockedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockedWindows

      CreatePracticeRunConfigurationRequest.Builder blockedWindows(String... blockedWindows)

      Optionally, you can block ARC from starting practice runs for specific windows of days and times.

      The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.

      For example, say you run business report summaries three days a week. For this scenario, you could set the following recurring days and times as blocked windows, for example: Mon:00:00-Mon:10:00 Wed-20:30-Wed:21:30 Fri-20:30-Fri:21:30.

      The blockedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Parameters:
      blockedWindows - Optionally, you can block ARC from starting practice runs for specific windows of days and times.

      The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.

      For example, say you run business report summaries three days a week. For this scenario, you could set the following recurring days and times as blocked windows, for example: Mon:00:00-Mon:10:00 Wed-20:30-Wed:21:30 Fri-20:30-Fri:21:30.

      The blockedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockedDates

      CreatePracticeRunConfigurationRequest.Builder blockedDates(Collection<String> blockedDates)

      Optionally, you can block ARC from starting practice runs for a resource on specific calendar dates.

      The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.

      For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.

      Parameters:
      blockedDates - Optionally, you can block ARC from starting practice runs for a resource on specific calendar dates.

      The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.

      For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockedDates

      CreatePracticeRunConfigurationRequest.Builder blockedDates(String... blockedDates)

      Optionally, you can block ARC from starting practice runs for a resource on specific calendar dates.

      The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.

      For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.

      Parameters:
      blockedDates - Optionally, you can block ARC from starting practice runs for a resource on specific calendar dates.

      The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.

      For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockingAlarms

      CreatePracticeRunConfigurationRequest.Builder blockingAlarms(Collection<ControlCondition> blockingAlarms)

      Blocking alarms for practice runs are optional alarms that you can specify that block practice runs when one or more of the alarms is in an ALARM state.

      Parameters:
      blockingAlarms - Blocking alarms for practice runs are optional alarms that you can specify that block practice runs when one or more of the alarms is in an ALARM state.
      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockingAlarms

      CreatePracticeRunConfigurationRequest.Builder blockingAlarms(ControlCondition... blockingAlarms)

      Blocking alarms for practice runs are optional alarms that you can specify that block practice runs when one or more of the alarms is in an ALARM state.

      Parameters:
      blockingAlarms - Blocking alarms for practice runs are optional alarms that you can specify that block practice runs when one or more of the alarms is in an ALARM state.
      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • blockingAlarms

      CreatePracticeRunConfigurationRequest.Builder blockingAlarms(Consumer<ControlCondition.Builder>... blockingAlarms)

      Blocking alarms for practice runs are optional alarms that you can specify that block practice runs when one or more of the alarms is in an ALARM state.

      This is a convenience method that creates an instance of the ControlCondition.Builder avoiding the need to create one manually via ControlCondition.builder().

      When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to blockingAlarms(List<ControlCondition>).

      Parameters:
      blockingAlarms - a consumer that will call methods on ControlCondition.Builder
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • allowedWindows

      CreatePracticeRunConfigurationRequest.Builder allowedWindows(Collection<String> allowedWindows)

      Optionally, you can allow ARC to start practice runs for specific windows of days and times.

      The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.

      For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.

      The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Parameters:
      allowedWindows - Optionally, you can allow ARC to start practice runs for specific windows of days and times.

      The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.

      For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.

      The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • allowedWindows

      CreatePracticeRunConfigurationRequest.Builder allowedWindows(String... allowedWindows)

      Optionally, you can allow ARC to start practice runs for specific windows of days and times.

      The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.

      For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.

      The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Parameters:
      allowedWindows - Optionally, you can allow ARC to start practice runs for specific windows of days and times.

      The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.

      For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.

      The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • outcomeAlarms

      CreatePracticeRunConfigurationRequest.Builder outcomeAlarms(Collection<ControlCondition> outcomeAlarms)

      Outcome alarms for practice runs are alarms that you specify that end a practice run when one or more of the alarms is in an ALARM state.

      Configure one or more of these alarms to monitor the health of your application when traffic is shifted away from an Availability Zone during each practice run. You should configure these alarms to go into an ALARM state if you want to stop a zonal shift, to let traffic for the resource return to the original Availability Zone.

      Parameters:
      outcomeAlarms - Outcome alarms for practice runs are alarms that you specify that end a practice run when one or more of the alarms is in an ALARM state.

      Configure one or more of these alarms to monitor the health of your application when traffic is shifted away from an Availability Zone during each practice run. You should configure these alarms to go into an ALARM state if you want to stop a zonal shift, to let traffic for the resource return to the original Availability Zone.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • outcomeAlarms

      CreatePracticeRunConfigurationRequest.Builder outcomeAlarms(ControlCondition... outcomeAlarms)

      Outcome alarms for practice runs are alarms that you specify that end a practice run when one or more of the alarms is in an ALARM state.

      Configure one or more of these alarms to monitor the health of your application when traffic is shifted away from an Availability Zone during each practice run. You should configure these alarms to go into an ALARM state if you want to stop a zonal shift, to let traffic for the resource return to the original Availability Zone.

      Parameters:
      outcomeAlarms - Outcome alarms for practice runs are alarms that you specify that end a practice run when one or more of the alarms is in an ALARM state.

      Configure one or more of these alarms to monitor the health of your application when traffic is shifted away from an Availability Zone during each practice run. You should configure these alarms to go into an ALARM state if you want to stop a zonal shift, to let traffic for the resource return to the original Availability Zone.

      Returns:
      Returns a reference to this object so that method calls can be chained together.

    • outcomeAlarms

      CreatePracticeRunConfigurationRequest.Builder outcomeAlarms(Consumer<ControlCondition.Builder>... outcomeAlarms)

      Outcome alarms for practice runs are alarms that you specify that end a practice run when one or more of the alarms is in an ALARM state.

      Configure one or more of these alarms to monitor the health of your application when traffic is shifted away from an Availability Zone during each practice run. You should configure these alarms to go into an ALARM state if you want to stop a zonal shift, to let traffic for the resource return to the original Availability Zone.

      This is a convenience method that creates an instance of the ControlCondition.Builder avoiding the need to create one manually via ControlCondition.builder().

      When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to outcomeAlarms(List<ControlCondition>).

      Parameters:
      outcomeAlarms - a consumer that will call methods on ControlCondition.Builder
      Returns:
      Returns a reference to this object so that method calls can be chained together.
      See Also:

    • overrideConfiguration

      CreatePracticeRunConfigurationRequest.Builder overrideConfiguration(AwsRequestOverrideConfiguration overrideConfiguration)
      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      overrideConfiguration - The override configuration.
      Returns:
      This object for method chaining.

    • overrideConfiguration

      CreatePracticeRunConfigurationRequest.Builder overrideConfiguration(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer)
      Description copied from interface: AwsRequest.Builder
      Add an optional request override configuration.
      Specified by:
      overrideConfiguration in interface AwsRequest.Builder
      Parameters:
      builderConsumer - A Consumer to which an empty AwsRequestOverrideConfiguration.Builder will be given.
      Returns:
      This object for method chaining.