Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Assertion
Attributes A structure that defines which attributes in the IdP assertion are to be used to define information about the users authenticated by the IdP to use the workspace.
- Authentication
Description A structure containing information about the user authentication methods used by the workspace.
- Authentication
Summary A structure that describes whether the workspace uses SAML, IAM Identity Center, or both methods for user authentication, and whether that authentication is fully configured.
- AwsSso
Authentication A structure containing information about how this workspace works with IAM Identity Center.
- Network
Access Configuration The configuration settings for in-bound network access to your workspace.
When this is configured, only listed IP addresses and VPC endpoints will be able to access your workspace. Standard Grafana authentication and authorization are still required.
Access is granted to a caller that is in either the IP address list or the VPC endpoint list - they do not need to be in both.
If this is not configured, or is removed, then all IP addresses and VPC endpoints are allowed. Standard Grafana authentication and authorization are still required.
While both
prefixListIds
andvpceIds
are required, you can pass in an empty array of strings for either parameter if you do not want to allow any of that type.If both are passed as empty arrays, no traffic is allowed to the workspace, because only explicitly allowed connections are accepted.
- Permission
Entry A structure containing the identity of one user or group and the
Admin
,Editor
, orViewer
role that they have.- Role
Values This structure defines which groups defined in the SAML assertion attribute are to be mapped to the Grafana
Admin
andEditor
roles in the workspace. SAML authenticated users not part ofAdmin
orEditor
role groups haveViewer
permission over the workspace.- Saml
Authentication A structure containing information about how this workspace works with SAML.
- Saml
Configuration A structure containing information about how this workspace works with SAML.
- Service
Account Summary A structure that contains the information about one service account.
- Service
Account Token Summary A structure that contains the information about a service account token.
- Service
Account Token Summary With Key A structure that contains the information about a service account token.
This structure is returned when creating the token. It is important to store the
key
that is returned, as it is not retrievable at a later time.If you lose the key, you can delete and recreate the token, which will create a new key.
- Update
Error A structure containing information about one error encountered while performing an UpdatePermissions operation.
- Update
Instruction Contains the instructions for one Grafana role permission update in a UpdatePermissions operation.
- User
A structure that specifies one user or group in the workspace.
- Validation
Exception Field A structure that contains information about a request parameter that caused an error.
- VpcConfiguration
The configuration settings for an Amazon VPC that contains data sources for your Grafana workspace to connect to.
Provided
securityGroupIds
andsubnetIds
must be part of the same VPC.Connecting to a private VPC is not yet available in the Asia Pacific (Seoul) Region (ap-northeast-2).
- Workspace
Description A structure containing information about an Amazon Managed Grafana workspace in your account.
- Workspace
Summary A structure that contains some information about one workspace in the account.
Enums§
- Account
Access Type - When writing a match expression against
AccountAccessType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Authentication
Provider Types - When writing a match expression against
AuthenticationProviderTypes
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Data
Source Type - When writing a match expression against
DataSourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - IdpMetadata
A structure containing the identity provider (IdP) metadata used to integrate the identity provider with this workspace. You can specify the metadata either by providing a URL to its location in the
url
parameter, or by specifying the full metadata in XML format in thexml
parameter. Specifying both will cause an error.- License
Type - When writing a match expression against
LicenseType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Notification
Destination Type - When writing a match expression against
NotificationDestinationType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Permission
Type - When writing a match expression against
PermissionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Role
- When writing a match expression against
Role
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Saml
Configuration Status - When writing a match expression against
SamlConfigurationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Update
Action - When writing a match expression against
UpdateAction
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - User
Type - When writing a match expression against
UserType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Validation
Exception Reason - When writing a match expression against
ValidationExceptionReason
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Workspace
Status - When writing a match expression against
WorkspaceStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.