Updates an existing policy within the AgentCore Policy system¶

Description¶

Updates an existing policy within the AgentCore Policy system. This operation allows modification of the policy description and definition while maintaining the policy's identity. The updated policy is validated against the Cedar schema before being applied. This is an asynchronous operation. Use the get_policy operation to poll the status field to track completion.

If the updated policy is a temporal policy, the policy engine invalidates all active temporal sessions. If the update adds or removes temporal operators, the policy engine also invalidates active temporal sessions. For more information about temporal policy sessions, see session-based temporal policies. The policy engine returns an HTTP 409 ConflictException to in-flight sessions. To resume, you must start a new session with a new session ID.

Usage¶

bedrockagentcorecontrol_update_policy(policyEngineId, policyId,
  description, definition, validationMode, enforcementMode)

Arguments¶

• policyEngineId

  [required] The identifier of the policy engine that manages the policy to be updated. This ensures the policy is updated within the correct policy engine context.

• policyId

  [required] The unique identifier of the policy to be updated. This must be a valid policy ID that exists within the specified policy engine.

• description

  The new human-readable description for the policy. This optional field allows updating the policy's documentation while keeping the same policy logic.

• definition

  The new Cedar or Dogwood policy statement that defines the access control rules. This replaces the existing policy definition with new logic while maintaining the policy's identity.

• validationMode

  The validation mode for the policy update. Determines how Cedar analyzer validation results are handled during policy updates. FAIL_ON_ANY_FINDINGS runs the Cedar analyzer and fails the update if validation issues are detected, ensuring the policy conforms to the Cedar schema and tool context. IGNORE_ALL_FINDINGS runs the Cedar analyzer but allows updates despite validation warnings. Use FAIL_ON_ANY_FINDINGS to ensure policy correctness during updates, especially when modifying policy logic or conditions.

• enforcementMode

  The enforcement mode for the policy. Run this policy in LOG_ONLY mode to collect data on how it affects your application. Once you are satisfied with the data gathered, switch the policy to ACTIVE. If you omit this field, the policy's existing enforcement mode is unchanged.

Value¶

A list with the following syntax:

list(
  policyId = "string",
  name = "string",
  policyEngineId = "string",
  createdAt = as.POSIXct(
    "2015-01-01"
  ),
  updatedAt = as.POSIXct(
    "2015-01-01"
  ),
  policyArn = "string",
  status = "CREATING"|"ACTIVE"|"UPDATING"|"DELETING"|"CREATE_FAILED"|"UPDATE_FAILED"|"DELETE_FAILED",
  enforcementMode = "ACTIVE"|"LOG_ONLY",
  definition = list(
    cedar = list(
      statement = "string"
    ),
    policyGeneration = list(
      policyGenerationId = "string",
      policyGenerationAssetId = "string"
    ),
    policy = list(
      statement = "string"
    )
  ),
  description = "string",
  statusReasons = list(
    "string"
  )
)

Request syntax¶

svc$update_policy(
  policyEngineId = "string",
  policyId = "string",
  description = list(
    optionalValue = "string"
  ),
  definition = list(
    cedar = list(
      statement = "string"
    ),
    policyGeneration = list(
      policyGenerationId = "string",
      policyGenerationAssetId = "string"
    ),
    policy = list(
      statement = "string"
    )
  ),
  validationMode = "FAIL_ON_ANY_FINDINGS"|"IGNORE_ALL_FINDINGS",
  enforcementMode = "ACTIVE"|"LOG_ONLY"
)