Files
agent-call/docs/evidence/cloud-inventory-2026-09-11.md
T

17 lines
1.1 KiB
Markdown

# Aliyun Beijing read-only inventory — 2026-09-11
Commands executed without create/associate/delete actions:
```text
aliyun ecs DescribeInstances --RegionId cn-beijing --PageSize 100
aliyun vpc DescribeEipAddresses --RegionId cn-beijing --PageSize 100
```
Observed facts:
- Region `cn-beijing` has one existing ECS instance, `ecs.e-c1m1.large`, status `Running`, charge type `PrePaid`, with public IP `39.105.111.158`. It is not reused or modified because it is not an authorized target spot test cell.
- The registered SIP egress EIP `123.56.71.98` exists in Beijing, allocation `eip-2zeevfsaxzwuue2szy7xb`, status `Available`, and is currently unassociated.
- No instance/EIP was created, rebound, stopped, deleted, or released.
Creation remains gated on explicit test budget/spot price ceiling, disk/VSwitch/security-group selection, SSH key authorization, and the real SIP/AI/OSS acceptance window. The available EIP must be associated only through the approved cell plan; it must never be placed in a SIP trunk contact field or replaced with a newly allocated address.