- Newest
- Most votes
- Most comments
Yes, the Visual editor and JSON options for AWS Backup policies in AWS Organizations are interchangeable. When you create a backup policy using the Visual editor, you can later view and edit the same policy in JSON format, and vice versa. This allows you flexibility in how you manage your backup policies.
Regarding granular control, the JSON editor typically provides more advanced capabilities, especially for complex resource selection criteria. For example, with JSON, you can implement more sophisticated backup strategies such as:
- Selecting specific resources by resource type
- Excluding resources based on resource type or tags
- Using combinations of multiple tags within the same resource selection
- Creating more complex conditional logic for resource selection
The JSON approach is particularly useful when you need to implement flexible backup strategies across your organization by combining multiple resource types and/or tags. It also allows you to exclude resources you don't want to back up using resource type or tag criteria, which can help optimize costs for non-critical resources.
To use these advanced selection features, you would create or modify a resource selection using the JSON editor in either the AWS Organizations or AWS Backup console. This gives you more precise control over which resources are included in your backup policies.
Sources
Enhance resource selection in AWS Backup Policies in AWS Organizations | AWS Storage Blog
AWS Backup now supports resource type and multiple tag selections in backup policies - AWS
Relevant content
- asked 4 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
