Files
go-sip/docs/evidence/20260920-real-cloud-inventory.md
T

32 lines
1.3 KiB
Markdown

# 2026-09-20 Alibaba Cloud read-only inventory
## Scope
This is a read-only recheck before any real SIP deployment. It does not
authorize rebinding an EIP, adopting an existing instance, creating an ECS, or
placing a call.
- Region: `cn-beijing`
- Required fixed EIP: `123.56.71.98`
- Required project tag: `project=agent-call`
## Observed inventory
- The fixed EIP allocation `eip-2zeevfsaxzwuue2szy7xb` exists and is
`Available` with no attached instance.
- The account currently returns one running instance, `ali.bj.01`, in
`cn-beijing-g`: Rocky Linux 9.3, `ecs.e-c1m1.large`, VPC
`vpc-2zeln7cr1x6biyr9o8l4v`, security group `sg-2ze8kw8l5egptn3vqml9`, and
public IP `39.105.111.158`. It is not Debian 13, does not use the required
fixed EIP, and has no ECS tags (`DescribeTags` returned `TotalCount: 0`).
- The instance was not adopted, modified, stopped, deleted, or used for SIP
validation. Its ownership and authorization are not established.
## Gate result
The fixed EIP remains unbound and the only running instance is an unrelated or
otherwise unauthorized candidate. Per the deployment rules, no rebinding,
replacement public IP, new ECS, SSH attempt, or real call was performed. A
project-tagged Debian 13 test host and an explicitly authorized EIP association
are still required before deploying the candidate package.