- Newest
- Most votes
- Most comments
Set Up VPC Peering ==> IAM Role and Permissions (Create an IAM role that grants AppFlow permissions to access the necessary resources in both VPCs. ) ==> Set up an AppFlow flow (Define the source and destination connectors (such as SAP) ==> Network Configuration (Ensure that the security groups and network ACLs allow the necessary traffic between the peered VPCs.) ==> Test Connectivity.
For more details, I recommend checking the AWS documentation:
I believe AWS AppFlow connections can be configured with or without PrivateLink, depending on your network architecture and security requirements. If you are using VPC peering and want to leverage PrivateLink, make sure that PrivateLink is enabled for AppFlow in both the source and destination VPCs.
- Please see this : https://docs.aws.amazon.com/appflow/latest/userguide/private-flows.html
Also, if you're connecting to a private SAP instance in another VPC, you generally use the private IP address or DNS hostname of the SAP instance. The URL would typically be something like sap://<private-ip-or-hostname>:<port>.
No, it doesn't accept URL of this format sap://.... I also tried with https://privateIp but this also doesn't work. Application host URL - https://privateIp Port number - 8001 PrivateLink - disabled ( since it needs endpoint service, nlb, tg .. )
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- asked 5 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 23 days ago
- AWS OFFICIALUpdated a year ago
Your answer is not complete . In APPFLow connections , what URL should I fill in case of VPC peering ? should I enable privatelink enabled or not