List studios in your Amazon Web Services account in the requested Amazon Web Services Region.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
list-studios
is a paginated operation. Multiple API calls may be issued in order to retrieve the entire data set of results. You can disable pagination by providing the --no-paginate
argument.
When using --output text
and the --query
argument on a paginated response, the --query
argument must extract data from the results of the following query expressions: studios
list-studios
[--cli-input-json | --cli-input-yaml]
[--starting-token <value>]
[--max-items <value>]
[--generate-cli-skeleton <value>]
--cli-input-json
| --cli-input-yaml
(string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton
. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml
.
--starting-token
(string)
A token to specify where to start paginating. This is the
NextToken
from a previously truncated response.For usage examples, see Pagination in the AWS Command Line Interface User Guide .
--max-items
(integer)
The total number of items to return in the command’s output. If the total number of items available is more than the value specified, a
NextToken
is provided in the command’s output. To resume pagination, provide theNextToken
value in thestarting-token
argument of a subsequent command. Do not use theNextToken
response element directly outside of the AWS CLI.For usage examples, see Pagination in the AWS Command Line Interface User Guide .
--generate-cli-skeleton
(string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input
, prints a sample input JSON that can be used as an argument for --cli-input-json
. Similarly, if provided yaml-input
it will print a sample input YAML that can be used with --cli-input-yaml
. If provided with the value output
, it validates the command inputs and returns a sample output JSON for that command.
See ‘aws help’ for descriptions of global parameters.
To list your studios
The following list-studios
example lists the studios in your AWS account.
aws nimble list-studios
Output:
{
"studios": [
{
"adminRoleArn": "arn:aws:iam::123456789012:role/studio-admin-role",
"arn": "arn:aws:nimble:us-west-2:123456789012:studio/studio-id",
"createdAt": "2022-01-27T20:29:35+00:00",
"displayName": "studio-name",
"homeRegion": "us-west-2",
"ssoClientId": "a1b2c3d4-5678-90ab-cdef-EXAMPLE11111",
"state": "READY",
"statusCode": "STUDIO_CREATED",
"statusMessage": "The studio has been created successfully ",
"studioEncryptionConfiguration": {
"keyType": "AWS_OWNED_KEY"
},
"studioId": "us-west-2:studio-id",
"studioName": "studio-name",
"studioUrl": "https://studio-name.nimblestudio.us-west-2.amazonaws.com",
"tags": {},
"updatedAt": "2022-01-27T20:29:37+00:00",
"userRoleArn": "arn:aws:iam::123456789012:role/studio-user-role"
}
]
}
For more information, see What is Amazon Nimble Studio? in the Amazon Nimble Studio User Guide.
nextToken -> (string)
The token for the next set of results, or null if there are no more results.
studios -> (list)
A collection of studios.
(structure)
Represents a studio resource.
A studio is the core resource used with Nimble Studio. You must create a studio first, before any other resource type can be created. All other resources you create and manage in Nimble Studio are contained within a studio.
When creating a studio, you must provides two IAM roles for use with the Nimble Studio portal. These roles are assumed by your users when they log in to the Nimble Studio portal via Amazon Web Services SSO and your identity source.
The user role must have the AmazonNimbleStudio-StudioUser managed policy attached for the portal to function properly.
The admin role must have the AmazonNimbleStudio-StudioAdmin managed policy attached for the portal to function properly.
Your studio roles must trust the identity.nimble.amazonaws.com service principal to function properly.
adminRoleArn -> (string)
The IAM role that studio admins assume when logging in to the Nimble Studio portal.
arn -> (string)
The Amazon Resource Name (ARN) that is assigned to a studio resource and uniquely identifies it. ARNs are unique across all Regions.
createdAt -> (timestamp)
The Unix epoch timestamp in seconds for when the resource was created.
displayName -> (string)
A friendly name for the studio.
homeRegion -> (string)
The Amazon Web Services Region where the studio resource is located.
ssoClientId -> (string)
The Amazon Web Services SSO application client ID used to integrate with Amazon Web Services SSO to enable Amazon Web Services SSO users to log in to Nimble Studio portal.
state -> (string)
The current state of the studio resource.
statusCode -> (string)
Status codes that provide additional detail on the studio state.
statusMessage -> (string)
Additional detail on the studio state.
studioEncryptionConfiguration -> (structure)
Configuration of the encryption method that is used for the studio.
keyArn -> (string)
The ARN for a KMS key that is used to encrypt studio data.
keyType -> (string)
The type of KMS key that is used to encrypt studio data.
studioId -> (string)
The unique identifier for a studio resource. In Nimble Studio, all other resources are contained in a studio resource.
studioName -> (string)
The name of the studio, as included in the URL when accessing it in the Nimble Studio portal.
studioUrl -> (string)
The address of the web page for the studio.
tags -> (map)
A collection of labels, in the form of key:value pairs, that apply to this resource.
key -> (string)
value -> (string)
updatedAt -> (timestamp)
The Unix epoch timestamp in seconds for when the resource was updated.
userRoleArn -> (string)
The IAM role that studio users assume when logging in to the Nimble Studio portal.