> While account IDs, like any identifying information, should be used and shared carefully, they are not considered secret, sensitive, or confidential information.
https://docs.aws.amazon.com/accounts/latest/reference/manage...
https://docs.aws.amazon.com/accounts/latest/reference/manage...
For example, my home address is technically public, but I most certainly wouldn't want it lambasted across the interstate with a picture of my family next to it advertising where I live. It's handed out on a need-to-know basis, and I mostly trust / expect that it's kept mostly confidential, or use-limited.
I really wanted G+ to work, but they were just too stupid to understand that this was a deal-breaker.
If they're not secret, sensitive, or confidential, then why must they be shared carefully?
https://docs.aws.amazon.com/whitepapers/latest/data-classifi...
The other attack vector is from insiders. Many organizations "shield" identifiable information behind UUIDs or some other scheme. In the event of a breach, the UUID might mean nothing to most (it's not foolproof, though), but opens more doors for an insider.
It's sort of like giving someone your IP address. By itself it's not enough to hack someone. But if your host is insecure, it sure makes it easier knowing exactly where to attack.
... by us (it should say).
Users may consider it differently.