Backing up each and every resources in AWS account
By : Hemoto
Date : August 01 2020, 07:00 PM
I think the issue was by ths following , The "correct" way is not to 'backup' resources. Rather, it is to initially create those resources in a reproducible manner. For example, creating resources via an AWS CloudFormation template allows the same resources to be deployed in a different region or account. Only the data itself, such as the information stored in a database, would need a 'backup'. Everything else could simply be redeployed.
Backing up data on your Google mail account in Android
this one helps. All AWS API calls are related to specific services. For example, you can request a list of Amazon VPCs, a list of Amazon DynamoDB tables, a list of Amazon EBS volumes -- but each would require a different API call. Another option would be to use AWS Config:
Azure Migration of Resources To New Account Before Deletion of User Account
By : doskoi
Date : March 29 2020, 07:55 AM
will help you The account used to create a resource is no longer relevant after the resource is created. Other than the activity log entry, Azure doesn't track who created a resource, and if that original user account is deleted it will have no effect on the resource or any other user's access to it.