# Connectivity Errors

### <mark style="color:blue;">CN01</mark>

#### Description:

* Please enter a unique endpoint name.

### <mark style="color:blue;">CN02</mark>

#### Description:

* Please detach the existing endpoint to the clusters: \<cluster name 1>, \<cluster name 2>&#x20;

### <mark style="color:blue;">CN03</mark>

#### Description:

* Please make sure the endpoint is ready to be assigned to a domain.

### <mark style="color:blue;">CN04</mark>

#### Description:

* Failed to delete the existing cluster connectivity. Please try to delete it manually.

### <mark style="color:blue;">CN05</mark>

#### Description:

* Please ensure the correct workspace is provided for the endpoint.

### <mark style="color:blue;">CN06</mark>

#### Description:

* Please provide the correct endpoint.

### <mark style="color:blue;">CN07</mark>

#### Description:

* Please ensure to attach the correct endpoint to the cluster

### <mark style="color:blue;">CN08</mark>

#### Description:

* Please contact e6data support for more information and assistance.

### <mark style="color:blue;">CN09</mark>

#### Description:

* Endpoint creation failed, all the changes have been rolledback.

### <mark style="color:blue;">CN10</mark>

#### Description:

* Please wait until the endpoint is completely deleted before proceeding with any further actions.

### <mark style="color:blue;">CN11</mark>

#### Description:

* Failed to delete the endpoint.

### <mark style="color:blue;">CN12</mark>

#### Description:

* Ensure you delete the cluster connectivity before attempting to detach the endpoint.

### <mark style="color:blue;">CN13</mark>

#### Description:

* The edit operation has failed. Changes may have been partially updated. Please try to edit the endpoint again.

### <mark style="color:blue;">CN14</mark>

#### Description:

* Please enter a unique IP set name.

### <mark style="color:blue;">CN15</mark>

#### Description:

* Please provide correct IP set.

### <mark style="color:blue;">CN16</mark>

#### Description:

* Ensure you delete the cluster connectivity before attempting to delete the attached IP Set

### <mark style="color:blue;">CN17</mark>

#### Description:

* Please disable existing connectivity before enabling new connectivity.

### <mark style="color:blue;">CN18</mark>

#### Description:

* Cluster connectivity is already enabled.

### <mark style="color:blue;">CN19</mark>

#### Description:

* Please ensure to attach the endpoint to the cluster.

### <mark style="color:blue;">CN20</mark>

#### Description:

* Endpoint is not available at the moment. Try again once it is ACTIVE.

### <mark style="color:blue;">CN21</mark>

#### Description:

* Please enable cluster connectivity

### <mark style="color:blue;">CN22</mark>

#### Description:

* Please ensure to enable the cluster connectivity before editing it.

### <mark style="color:blue;">CN23</mark>

#### Description:

* Please Add permission \<missing permission> to Cross Account IAM Role .

**Solution:**

* Please add the respective permission to your Cross Account IAM Role. There is no workspace updation required.&#x20;

### <mark style="color:blue;">CN24</mark>

#### Description:

* Please detach the existing endpoint to the clusters.

### <mark style="color:blue;">CN25</mark>

#### Description:

* Cluster connectivity failed to delete. Please Add permission to Cross Account IAM Role.

### <mark style="color:blue;">CN28</mark>

#### Error:

Endpoint creation failed: Name already exists in the cloud account

#### Description:

The endpoint creation failed because the user attempted to create an endpoint with a name that already exists as a resource in their cloud account. Duplicate names are not permitted, failing to create the endpoint.

#### Solution:

To resolve this issue, the user should create a new endpoint with a different name that does not conflict with existing resources in their cloud account. Choose a unique name for the endpoint to ensure successful creation without encountering name conflicts.

### <mark style="color:blue;">CN29</mark>

#### Error:

Invalid Certificate ARN

#### Description:

The endpoint creation failed because the certificate ARN provided by the user during the assign-to-domain operation is incorrect.

#### Solution:

To resolve this issue, the user needs to verify and correct the certificate ARN provided during the assign to Domain operation. Once the correct certificate ARN is obtained, it should be updated in the endpoint creation process. This will ensure that the endpoint creation proceeds successfully and allows the user to connect the cluster to the external tool using the updated certificate ARN.

### <mark style="color:blue;">CN30</mark>

#### Error:

The domain does not match the certificate.

#### Description:

During the creation of an endpoint, the provided domain by the user does not match the certificate associated with it. This mismatch prevents successful endpoint creation.

#### Solution:

Verify that the domain provided during endpoint creation matches the domain associated with the certificate. If they do not match, update the domain to match the certificate or obtain a new certificate with the correct domain. Once the domain and certificate are aligned, retry creating the endpoint.

### <mark style="color:blue;">CN31</mark>

#### Error:

Certificate not available for endpoint creation.

#### Description:

During the creation of an endpoint, the certificate required for authentication is not available at the moment. This could occur due to the certificate being in a pending state, revoked, or experiencing other issues.

#### Solution:

Check the status of the certificate in your cloud account to identify any errors or issues. Resolve any pending validation or revocation problems associated with the certificate. Once the certificate is available and any errors are resolved, retry creating the endpoint.

### <mark style="color:blue;">CN32</mark>

#### Error:

Invalid Certificate ARN format.

#### Description:

During the creation of an endpoint, the Certificate ARN provided by the user is not in the correct format. This error typically occurs when the ARN is copied or pasted incorrectly, leading to an invalid format.

#### Solution:

Recheck the Certificate ARN and ensure it is copied or entered correctly without any typos or missing characters. Verify that the ARN follows the correct format specified by AWS. Once the correct ARN is provided, retry creating the endpoint.

### <mark style="color:blue;">CN33</mark>

#### Error:

Endpoint creation failed due to delayed resource association.

#### Description:

During the creation of an endpoint, the association of resources in your cloud account experienced a delay, resulting in the failure of the endpoint creation process. This delay may have been caused by internal AWS error.

#### Solution:

To resolve this issue, the user should recreate the endpoint. Any changes made during the failed endpoint creation will be rolled back. Ensure that all necessary permissions and resources are available and retry the endpoint creation process. The failure might have occurred due to **WAFUnavailableEntityException**. For more information please refer to [AWS Documentation.](https://docs.aws.amazon.com/waf/latest/APIReference/API_CreateWebACL.html)