Module aws_sdk_backup::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Backup can respond with.

Structs

• AdvancedBackupSetting

  A list of backup options for each resource type.

• BackupJob

  Contains detailed information about a backup job.

• BackupJobSummary

  This is a summary of jobs created or running within the most recent 30 days.

• BackupPlan

  Contains an optional backup plan display name and an array of BackupRule objects, each of which specifies a backup rule. Each rule in a backup plan is a separate scheduled task and can back up a different selection of Amazon Web Services resources.

• BackupPlanInput

  Contains an optional backup plan display name and an array of BackupRule objects, each of which specifies a backup rule. Each rule in a backup plan is a separate scheduled task.

• BackupPlanTemplatesListMember

  An object specifying metadata associated with a backup plan template.

• BackupPlansListMember

  Contains metadata about a backup plan.

• BackupRule

  Specifies a scheduled task used to back up a selection of resources.

• BackupRuleInput

  Specifies a scheduled task used to back up a selection of resources.

• BackupSelection

  Used to specify a set of resources to a backup plan.

• BackupSelectionsListMember

  Contains metadata about a BackupSelection object.

• BackupVaultListMember

  Contains metadata about a backup vault.

• CalculatedLifecycle

  Contains DeleteAt and MoveToColdStorageAt timestamps, which are used to specify a lifecycle for a recovery point.

• Condition

  Contains an array of triplets made up of a condition type (such as StringEquals), a key, and a value. Used to filter resources using their tags and assign them to a backup plan. Case sensitive.

• ConditionParameter

  Includes information about tags you define to assign tagged resources to a backup plan.

• Conditions

  Contains information about which resources to include or exclude from a backup plan using their tags. Conditions are case sensitive.

• ControlInputParameter

  A list of parameters for a control. A control can have zero, one, or more than one parameter. An example of a control with two parameters is: "backup plan frequency is at least daily and the retention period is at least 1 year". The first parameter is daily. The second parameter is 1 year.

• ControlScope

  A framework consists of one or more controls. Each control has its own control scope. The control scope can include one or more resource types, a combination of a tag key and value, or a combination of one resource type and one resource ID. If no scope is specified, evaluations for the rule are triggered when any resource in your recording group changes in configuration.

• CopyAction

  The details of the copy operation.

• CopyJob

  Contains detailed information about a copy job.

• CopyJobSummary

  This is a summary of copy jobs created or running within the most recent 30 days.

• DateRange

  This is a resource filter containing FromDate: DateTime and ToDate: DateTime. Both values are required. Future DateTime values are not permitted.

• Framework

  Contains detailed information about a framework. Frameworks contain controls, which evaluate and report on your backup events and resources. Frameworks generate daily compliance results.

• FrameworkControl

  Contains detailed information about all of the controls of a framework. Each framework must contain at least one control.

• LegalHold

  A legal hold is an administrative tool that helps prevent backups from being deleted while under a hold. While the hold is in place, backups under a hold cannot be deleted and lifecycle policies that would alter the backup status (such as transition to cold storage) are delayed until the legal hold is removed. A backup can have more than one legal hold. Legal holds are applied to one or more backups (also known as recovery points). These backups can be filtered by resource types and by resource IDs.

• Lifecycle

  Contains an array of Transition objects specifying how long in days before a recovery point transitions to cold storage or is deleted.

• ProtectedResource

  A structure that contains information about a backed-up resource.

• RecoveryPointByBackupVault

  Contains detailed information about the recovery points stored in a backup vault.

• RecoveryPointByResource

  Contains detailed information about a saved recovery point.

• RecoveryPointCreator

  Contains information about the backup plan and rule that Backup used to initiate the recovery point backup.

• RecoveryPointMember

  This is a recovery point which is a child (nested) recovery point of a parent (composite) recovery point. These recovery points can be disassociated from their parent (composite) recovery point, in which case they will no longer be a member.

• RecoveryPointSelection

  This specifies criteria to assign a set of resources, such as resource types or backup vaults.

• ReportDeliveryChannel

  Contains information from your report plan about where to deliver your reports, specifically your Amazon S3 bucket name, S3 key prefix, and the formats of your reports.

• ReportDestination

  Contains information from your report job about your report destination.

• ReportJob

  Contains detailed information about a report job. A report job compiles a report based on a report plan and publishes it to Amazon S3.

• ReportPlan

  Contains detailed information about a report plan.

• ReportSetting

  Contains detailed information about a report setting.

• RestoreJobSummary

  This is a summary of restore jobs created or running within the most recent 30 days.

• RestoreJobsListMember

  Contains metadata about a restore job.

Enums

• AggregationPeriod
  When writing a match expression against AggregationPeriod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BackupJobState
  When writing a match expression against BackupJobState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BackupJobStatus
  When writing a match expression against BackupJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BackupVaultEvent
  When writing a match expression against BackupVaultEvent, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConditionType
  When writing a match expression against ConditionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• CopyJobState
  When writing a match expression against CopyJobState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• CopyJobStatus
  When writing a match expression against CopyJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LegalHoldStatus
  When writing a match expression against LegalHoldStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RecoveryPointStatus
  When writing a match expression against RecoveryPointStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RestoreJobState
  When writing a match expression against RestoreJobState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• RestoreJobStatus
  When writing a match expression against RestoreJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StorageClass
  When writing a match expression against StorageClass, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VaultState
  When writing a match expression against VaultState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VaultType
  When writing a match expression against VaultType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.