/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include The discovery failure reason.See Also:
AWS
* API Reference
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure code.
* assume-role-failure
- IPAM could not assume the Amazon Web Services
* IAM service-linked role. This could be because of any of the following:
SLR has not been created yet and IPAM is still creating it.
You have opted-out of the IPAM home Region.
Account * you are using as your IPAM account has been suspended.
throttling-failure
- IPAM account is already using the
* allotted transactions per second and IPAM is receiving a throttling error when
* assuming the Amazon Web Services IAM SLR.
* unauthorized-failure
- Amazon Web Services account making the
* request is not authorized. For more information, see AuthFailure
* in the Amazon Elastic Compute Cloud API Reference.
The discovery failure message.
*/ inline const Aws::String& GetMessage() const{ return m_message; } /** *The discovery failure message.
*/ inline bool MessageHasBeenSet() const { return m_messageHasBeenSet; } /** *The discovery failure message.
*/ inline void SetMessage(const Aws::String& value) { m_messageHasBeenSet = true; m_message = value; } /** *The discovery failure message.
*/ inline void SetMessage(Aws::String&& value) { m_messageHasBeenSet = true; m_message = std::move(value); } /** *The discovery failure message.
*/ inline void SetMessage(const char* value) { m_messageHasBeenSet = true; m_message.assign(value); } /** *The discovery failure message.
*/ inline IpamDiscoveryFailureReason& WithMessage(const Aws::String& value) { SetMessage(value); return *this;} /** *The discovery failure message.
*/ inline IpamDiscoveryFailureReason& WithMessage(Aws::String&& value) { SetMessage(std::move(value)); return *this;} /** *The discovery failure message.
*/ inline IpamDiscoveryFailureReason& WithMessage(const char* value) { SetMessage(value); return *this;} private: IpamDiscoveryFailureCode m_code; bool m_codeHasBeenSet = false; Aws::String m_message; bool m_messageHasBeenSet = false; }; } // namespace Model } // namespace EC2 } // namespace Aws