update_resiliency_policy
async
¶
update_resiliency_policy(
policy_arn: Arn,
*,
config_overrides: Optional[AsyncresiliencehubClientConfig] = None,
policy_name: Optional[EntityName] = None,
policy_description: Optional[EntityDescription] = None,
data_location_constraint: Optional[DataLocationConstraint] = None,
tier: Optional[ResiliencyPolicyTier] = None,
policy: Optional[DisruptionPolicy] = None,
) -> UpdateResiliencyPolicyResponse
Updates a resiliency policy.
Resilience Hub allows you to provide a value of zero for rtoInSecs and rpoInSecs of your resiliency policy. But, while assessing your application, the lowest possible assessment result is near zero. Hence, if you provide value zero for rtoInSecs and rpoInSecs, the estimated workload RTO and estimated workload RPO result will be near zero and the Compliance status for your application will be set to Policy breached.
Parameters:
-
policy_arn(Arn) –Amazon Resource Name (ARN) of the resiliency policy. The format for this ARN is: arn:
partition:resiliencehub:region:account:resiliency-policy/policy-id. For more information about ARNs, see Amazon Resource Names (ARNs) in the Amazon Web Services General Reference guide. -
policy_name(Optional[EntityName], default:None) –Name of the resiliency policy.
-
policy_description(Optional[EntityDescription], default:None) –Description of the resiliency policy.
-
data_location_constraint(Optional[DataLocationConstraint], default:None) –Specifies a high-level geographical location constraint for where your resilience policy data can be stored.
-
tier(Optional[ResiliencyPolicyTier], default:None) –The tier for this resiliency policy, ranging from the highest severity (
MissionCritical) to lowest (NonCritical). -
policy(Optional[DisruptionPolicy], default:None) –Resiliency policy to be created, including the recovery time objective (RTO) and recovery point objective (RPO) in seconds.
Raises:
-
AccessDeniedException–You don't have permissions to perform the requested operation. The user or role that is making the request must have at least one IAM permissions policy attached that grants the required permissions.
-
ConflictException–This exception occurs when a conflict with a previous successful write is detected. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.
-
InternalServerException–This exception occurs when there is an internal failure in the Resilience Hub service.
-
ResourceNotFoundException–This exception occurs when the specified resource could not be found.
-
ThrottlingException–This exception occurs when you have exceeded the limit on the number of requests per second.
-
ValidationException–This exception occurs when a request is not valid.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_resiliencehub/_services/async_resiliencehub.py
4978 4979 4980 4981 4982 4983 4984 4985 4986 4987 4988 4989 4990 4991 4992 4993 4994 4995 4996 4997 4998 4999 5000 5001 5002 5003 5004 5005 5006 5007 5008 5009 5010 5011 5012 5013 5014 5015 5016 5017 5018 5019 5020 5021 5022 5023 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034 5035 5036 5037 5038 5039 5040 5041 5042 5043 5044 5045 5046 5047 5048 5049 5050 5051 5052 5053 5054 5055 5056 5057 5058 5059 5060 5061 5062 5063 5064 5065 | |