lvtujingji
lvtujingji
That is normaly when I add policy and changed yaml file . The policy json { "Version": "2012-10-17", "Statement": [ { "Action": [ "ecr:UploadLayerPart", "ecr:PutImage", "ecr:InitiateLayerUpload", "ecr:GetDownloadUrlForLayer", "ecr:CompleteLayerUpload", "ecr:BatchGetImage", "ecr:BatchCheckLayerAvailability"...
> Normal users can also log in through `https://your-endpoint/manager/` by entering the host and API key. Normal users can only view their own information. 1 and 4 currently are supported,...
This is my configuration root@ip-172-31-45-23:/etc/bee# bee version 2.1.0-de7eccc1 root@ip-172-31-45-23:/etc/bee# cat bee.yaml api-addr: 127.0.0.1:1633 full-node: true swap-enable: true blockchain-rpc-endpoint: https://rpc.gnosis.gateway.fm nat-addr: "18.223.119.122:1634" payment-threshold: "9000000" swap-initial-deposit: "0" # target-neighborhood: "10010011011" password-file: /var/lib/bee/password...
aga delete error us-west-2 - GlobalAccelerator - arn:aws:globalaccelerator::784954671920:accelerator/17f66cbd-d355-4998-97f6-5ee97e5dd2b3 - [ARN: "arn:aws:globalaccelerator::784954671920:accelerator/17f66cbd-d355-4998-97f6-5ee97e5dd2b3"] - would remove us-west-2 - GlobalAcceleratorListener - arn:aws:globalaccelerator::784954671920:accelerator/17f66cbd-d355-4998-97f6-5ee97e5dd2b3/listener/04fd050c - [ARN: "arn:aws:globalaccelerator::784954671920:accelerator/17f66cbd-d355-4998-97f6-5ee97e5dd2b3/listener/04fd050c"] - would remove us-west-2 - GlobalAcceleratorListener - arn:aws:globalaccelerator::784954671920:accelerator/17f66cbd-d355-4998-97f6-5ee97e5dd2b3/listener/b82fb97a...
configuration regions: - all blocklist: - "999999999999" # Account Id whose resources will not be deleted accounts: "000000000000": {} # Account Id for which all resources will be deleted bypass-alias-check-accounts:...
ap-southeast-1 - PinpointPhoneNumber - phone-df7f3e31605644249d0ea0ececacf806 - [CreatedDate: "2024-10-26T08:43:44Z", ID: "phone-df7f3e31605644249d0ea0ececacf806", Status: "ACTIVE"] - failed ConflictException: Conflict Occurred - Reason="PHONE_NUMBER_ASSOCIATED_TO_POOL" ResourceType="phone-number" ResourceId="phone-df7f3e31605644249d0ea0ececacf806"
Some update in here?
Will there be plans to support removing this?