7.3. AWS PrivateLink 연결 활성화

프로세스

1. 고객 지원으로 이동합니다. 그러나 자동 입력 필드는 다음을 확인합니다.

   1. 계정 필드에 고객 계정이 표시됩니다.
   2. 소유자 필드에 로그인이 표시됩니다.
   3. Product 필드에는 Red Hat Ansible Automation Platform On Clouds가 표시됩니다.
   4. Version 필드에 AWS - Managed Service가 표시됩니다.
2. What can we help you with? 섹션에 대해 구성 을 선택합니다.
3. Continue 를 클릭합니다.

4. 다음 템플릿의 값을 사용하여 제목에 값을 복사하고 지원 요청의 문제 섹션을 설명합니다.

   Title:
   Ansible Automation Platform Service on AWS PrivateLink Template
   
   Describe your problem:
   Enable AWS PrivateLink connectivity from control plane to customer's network
   
   Endpoint Service references are for the Endpoint Service created in the customer's VPC.
   
   Endpoint Service name: <enter here>
   Endpoint Service AWS region: <enter here>
   Endpoint Service ports or port ranges: <enter here>
   
   If you have multiple endpoint services in multiple regions, you must provide the following values for each endpoint service you have:
   
   Endpoint Service name: <enter here>
   Endpoint Service AWS region: <enter here>
   Endpoint Service ports or port ranges: <enter here>
   URL of your AAP deployment: <enter here>

   Title:
   Ansible Automation Platform Service on AWS PrivateLink Template
   
   Describe your problem:
   Enable AWS PrivateLink connectivity from customer's network to control plane
   
   Customer AWS account ID: <enter here>
   Endpoint AWS region(s): <enter here>
   URL of your AAP deployment: <enter here>
   The existing endpoint provided for the initial region (if a PrivateLink has already been configured): <enter here>
   
   If you want to setup PrivateLink for additional regions, you must send the above values for those regions.
   
   
   After Red Hat has configured the control plane Endpoint Service allowed principal and supported regions, a response will be added to your support ticket to create your Endpoint and share the Endpoint Service name, which you can find at https://console.redhat.com/ansible/service.

5. Continue 를 클릭합니다.