Resource
The English user guide is currently in beta preview. Most of the documents have been automatically translated from the Japanese version. Should you find any inaccuracies, please reach out to Flatt Security.
Shisho Cloud inspects and audits a wide variety of targets. The entities of the data subject to audit are referred to as resources within Shisho Cloud. Each resource has a resource ID as a unique identifier. A human-readable resource name paired with a resource ID may be referred to as resource metadata.
Resource ID
The structure of a resource ID varies depending on the type of resource. However, it always has a prefix indicating the resource type. Here are some examples of resource IDs:
- AWS EC2 instance
- Format:
<RESOURCE_KIND>|<REGION>|<INSTANCE_ID>
- Example:
aws-ec2-instance|ap-northeast-1|i-0a1b2c3d4e5f6g7h8
- Format:
- Google Cloud Compute Engine instance
- Format:
<RESOURCE_KIND>|<PROJECT_NUMBER>|<ZONE>|<INSTANCE_ID>
- Example:
googlecloud-ce-instance|489621111111|asia-northeast1-b|5121584011111111111
- Format:
- GitHub repository
- Format:
<RESOURCE_KIND>|<ORGANIZATION_ID>-<REPOSITORY_ID>
- Example:
github-repository|663369379-560312901
- Format:
- Web application
- Format:
<RESOURCE_KIND>|<WEB_APPLICATION_ID>
- Example:
user-web-application|WA01J1C82HCBZWKN9M7R5TJ1GEDV
- Format:
Resource kind
In Shisho Cloud, the identifier that indicates the type of a resource is called the resource kind. The resource kind is composed of the provider, service, and resource name of the audit target. It is also used as a prefix for the resource ID. Here are some examples of resource kinds:
- AWS EC2 instance:
aws-ec2-instance
- Google Cloud Compute Engine instance:
googlecloud-ce-instance
- GitHub repository:
github-repository
- Web application:
user-web-application