where keep resource name for stopping snapshot service ? i'm root
hello, i use this command line aws lightsail disable-add-on --region eu-north-1 --resource-name redubuntu --add-on-type AutoSnapshot but resource name is incorrect see the reponse An error occurred (InvalidInputException) when calling the DisableAddOn operation: Requested resource not found: {redubuntu} (Service: Lightsail; Status Code: 400; Error Code: InvalidInputException; Request ID: 33a5e2c7-1db2-4b1b-bb9e-d3a0f0e61618; Proxy: null) [cloudshell-user@ip-10-6-9-251 ~]$
where i keep the correct name resource ? i tried in arn and iam but nothing done . thanks
- 最新
- 最多得票
- 最多評論
nothing done , i changed in provate but forbidden delete . what to do ?
succes, i have deleted what you tell me, and the last snapshot i arrive to delete, but the other old snapshot is forbidden delete also if i set pubblic. see screen shot i'm root
i find that my snapshot , forbidden to delete , are been created by ami. what to do ? thanks
First, please unregister the AMI. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/deregister-ami.html#clean-up-ebs-ami
Hello.
I also answered the URL below, but are you trying to stop automatic snapshots in EC2 rather than Lightsail?
https://repost.aws/ja/questions/QUBlrWrFyNTuqiV50P1IhHGg/i-want-stop-snapshot-service-console-ask-me-resource-name-lightseal-as-not-a-registered-service-i-m-root
This command is for stopping automatic snapshots of Lightsail instances; it cannot stop snapshots of EC2 instances or other resources.
For EC2, you need to check your AWS Backup settings and Data Lifecycle Manager settings.
Please check these settings and delete any settings that are creating snapshots of the target EC2.
https://docs.aws.amazon.com/aws-backup/latest/devguide/deleting-a-backup-plan.html
https://docs.aws.amazon.com/ebs/latest/userguide/view-modify-delete.html#delete
相關內容
AWS 官方已更新 3 年前- AWS 官方已更新 3 個月前
Select the snapshot you want to delete on that screen. You can delete it after selecting it. Looking at the snapshot description, it looks like an AMI has probably been created as well, so you may need to delete the AMI first. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/deregister-ami.html#clean-up-ebs-ami