Skip to main content

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 comentario
  1. 27 nov 2019, 3:45 p.m.
    @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.