Struct aws_sdk_qldb::operation::update_ledger_permissions_mode::UpdateLedgerPermissionsModeInput
source · #[non_exhaustive]pub struct UpdateLedgerPermissionsModeInput {
pub name: Option<String>,
pub permissions_mode: Option<PermissionsMode>,
}Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.name: Option<String>The name of the ledger.
permissions_mode: Option<PermissionsMode>The permissions mode to assign to the ledger. This parameter can have one of the following values:
-
ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for ledgers.This mode allows users who have the
SendCommandAPI permission for this ledger to run all PartiQL commands (hence,ALLOW_ALL) on any tables in the specified ledger. This mode disregards any table-level or command-level IAM permissions policies that you create for the ledger. -
STANDARD: (Recommended) A permissions mode that enables access control with finer granularity for ledgers, tables, and PartiQL commands.By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and PartiQL actions, in addition to the
SendCommandAPI permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.
We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.
Implementations§
source§impl UpdateLedgerPermissionsModeInput
impl UpdateLedgerPermissionsModeInput
sourcepub fn permissions_mode(&self) -> Option<&PermissionsMode>
pub fn permissions_mode(&self) -> Option<&PermissionsMode>
The permissions mode to assign to the ledger. This parameter can have one of the following values:
-
ALLOW_ALL: A legacy permissions mode that enables access control with API-level granularity for ledgers.This mode allows users who have the
SendCommandAPI permission for this ledger to run all PartiQL commands (hence,ALLOW_ALL) on any tables in the specified ledger. This mode disregards any table-level or command-level IAM permissions policies that you create for the ledger. -
STANDARD: (Recommended) A permissions mode that enables access control with finer granularity for ledgers, tables, and PartiQL commands.By default, this mode denies all user requests to run any PartiQL commands on any tables in this ledger. To allow PartiQL commands to run, you must create IAM permissions policies for specific table resources and PartiQL actions, in addition to the
SendCommandAPI permission for the ledger. For information, see Getting started with the standard permissions mode in the Amazon QLDB Developer Guide.
We strongly recommend using the STANDARD permissions mode to maximize the security of your ledger data.
source§impl UpdateLedgerPermissionsModeInput
impl UpdateLedgerPermissionsModeInput
sourcepub fn builder() -> UpdateLedgerPermissionsModeInputBuilder
pub fn builder() -> UpdateLedgerPermissionsModeInputBuilder
Creates a new builder-style object to manufacture UpdateLedgerPermissionsModeInput.
Trait Implementations§
source§impl Clone for UpdateLedgerPermissionsModeInput
impl Clone for UpdateLedgerPermissionsModeInput
source§fn clone(&self) -> UpdateLedgerPermissionsModeInput
fn clone(&self) -> UpdateLedgerPermissionsModeInput
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moresource§impl PartialEq for UpdateLedgerPermissionsModeInput
impl PartialEq for UpdateLedgerPermissionsModeInput
source§fn eq(&self, other: &UpdateLedgerPermissionsModeInput) -> bool
fn eq(&self, other: &UpdateLedgerPermissionsModeInput) -> bool
self and other values to be equal, and is used
by ==.