1 comment
note: this is the pilot doc that is now outdated. please refer to the official private connect developer guide for up to date info https://help.salesforce.com/articleView?id=sf.private_connect_overview.htm&type=5
WarningSalesforce Private Connect for AWS was archived. To reactivate, contact the group owner A.A. Ron.
Group
Salesforce Private Connect for AWS
Hi, I am still exploring AWS and want to know whether we can develop a Salesforce type application there or not? It seems AWS supports python, java, C#, and ruby rails and many other languages But not Apex. Also, AWS is more for hosting applications, setting up servers and databases but NOT for declarative. Any inputs would be appreciated
1 comment
@Vishal Pandey - you may want to check out Salesforce Evergreen: https://developer.salesforce.com/blogs/2019/11/introducing-salesforce-evergreen.html
Hi, please may I ask. I would like to try out AWS AppFlow and would like to know if PriveLink can be used together to secure the data transfer or not.
Thank you,
JK
2 comments
Hi @Courtney Dascenzo. My AWS infrastructure folks pointed me to the below article that was published a few months back. Can you help me connect the dots and understand how this pilot relates to the functionality/setup that is described in the article? Is it essentially describing the same thing or are there material differences?
2 comments
We are setting up the Salesforce Private Connect for AWS by following the developer guide but require some assistance with the initial instructions for Inbound Connections -- Amazon-to-Salesforce.
There is a step that requires creating a PrivateConnection using the Salesforce Metadata API but this is unclear. We have created an XML file in the format specified and used both Workbench and SFDX to upload the settings to our pilot Salesforce instance.
When using SFDX we create the XML file, zip it and upload the zip sfdx force:mdapi:deploy -u <sf-instance> -f <file.zip> -w 2, is this the intended way for uploading the metadata? Without a package.xml file? How can we tell if the metadata has been uploaded successfully? Whatever we try the VPC endpoint status remains as "pending acceptance".
Lastly, for this section, should the externalConnectionProperties.propertyValue be the VPC id only or the entire service name?
1 comment
@Christopher Sullivan - It does requires a package.xml . I'm attaching some screenshots that may help. The status of the endpoint will not change in salesforce. It will remain as "pending acceptance". This is a limitation in pilot but will reflect the appropriate status once GA. To see the actual status of the endpoint, login to the aws console and look there. If it is "available" in aws, then the connection is ready to use. For inbound connections you register the endpoint id, for outbound connections you register the endpoint service through the salesforce metadata api.