💃 Level up your integration security 🕺

Good morning, Salesforce Nerds! 🌄 

With cloud adoption showing no signs of slowing down, companies are running more & more of their applications .

One of the most important we can do for our clients is design with security in mind from the beginning.

Today let’s check out an easy way to do just that. 💪 

If you’re in an environment that integrates Salesforce + AWS you should definitely be aware of this …

TABLE OF CONTENTS

Level up your integration security

• Private Connect

• Inbound Private Connections

• Outbound Private Connections

• Takeaways

What is it?

PRIVATE CONNECT

Private Connect is secure, fast, and easy way to connect your Salesforce org to your AWS instance. 💪 

This feature will reduce exposure to outside security threats around your AWS integrations by

✅ Setting up fully managed connection to AWS VPC

✅ Routes integration traffic through this connection instead of public internet

We’re talking about cross-cloud, bi-directional security here! 🔐 

You can set this up for both inbound and outbound traffic. This way you can keep all critical systems aligned!

Let’s check it out a little deeper. 👇️ 

Keep your I/B traffic secure

INBOUND PRIVATE CONNECTIONS

Inbound connections mean traffic coming INTO your Salesforce org.

So, if your company sends data from AWS into Salesforce then this is for you 🫵 

Inside your AWS instance:

✅ First, you’ll need a VPC inside AWS

✅ Next, create an AWS PrivateLink endpoint inside your VPC

This will help facilitate the AWS traffic into Salesforce’s managed VPC. 🔐 

To do this, you’re going to need something out of Salesforce …

Under Setup > Private Connect you’ll see a list of AWS Regions,

Find the one that matches the AWS region your VPC is in and grab the service name. 🗒️ 

You’ll need this for the PrivateLink creation in AWS.

Once it’s created, Salesforce see it automatically and you simply accept it.

Boom 💥 

Inbound private connection made.

Keep your O/B traffic secure

OUTBOUND PRIVATE CONNECTIONS

Outbound connections mean traffic going OUT from your Salesforce org.

Sending data from Salesforce to AWS? Read on 👇️ 

Under Setup > Private Connect, find that list of AWS Regions again.

Find the one that matches the region for your PrivateLink endpoint. Make note of the IAM Role.

In AWS, make sure that role is granted permissions to the PrivateLink endpoint.

Make a note of the endpoint service name in AWS. ✍️ 

Use it to create the outbound connection in Salesforce.

Lastly, set up a Named Credential.

Easy-peasy-🍋-squeezy.

Conclusion

TAKEAWAYS

In today’s cloud-driven technology landscape security is a must. 💯 

If you’re working with AWS + Salesforce then there’s no reason not to leverage these easy configuration to add that extra layer.

Soul Food

Today’s Principle

and now....Salesforce Memes