#[non_exhaustive]
pub enum UpdatePublicSharingSettingsErrorKind {
AccessDeniedException(AccessDeniedException),
InternalFailureException(InternalFailureException),
InvalidParameterValueException(InvalidParameterValueException),
ResourceNotFoundException(ResourceNotFoundException),
ThrottlingException(ThrottlingException),
UnsupportedPricingPlanException(UnsupportedPricingPlanException),
Unhandled(Unhandled),
}
Expand description
Types of errors that can occur for the UpdatePublicSharingSettings
operation.
Variants (Non-exhaustive)§
This enum is marked as non-exhaustive
AccessDeniedException(AccessDeniedException)
You don't have access to this item. The provided credentials couldn't be validated. You might not be authorized to carry out the request. Make sure that your account is authorized to use the Amazon QuickSight service, that your policies have the correct permissions, and that you are using the correct access keys.
InternalFailureException(InternalFailureException)
An internal failure occurred.
InvalidParameterValueException(InvalidParameterValueException)
One or more parameters has a value that isn't valid.
ResourceNotFoundException(ResourceNotFoundException)
One or more resources can't be found.
ThrottlingException(ThrottlingException)
Access is throttled.
UnsupportedPricingPlanException(UnsupportedPricingPlanException)
This error indicates that you are calling an embedding operation in Amazon QuickSight without the required pricing plan on your Amazon Web Services account. Before you can use embedding for anonymous users, a QuickSight administrator needs to add capacity pricing to Amazon QuickSight. You can do this on the Manage Amazon QuickSight page.
After capacity pricing is added, you can use the GetDashboardEmbedUrl
API operation with the --identity-type ANONYMOUS
option.
Unhandled(Unhandled)
An unexpected error occurred (e.g., invalid JSON returned by the service or an unknown error code).
When logging an error from the SDK, it is recommended that you either wrap the error in
DisplayErrorContext
, use another
error reporter library that visits the error’s cause/source chain, or call
Error::source
for more details about the underlying cause.