In AWS there are a number of gateways within a VPC. The following types exist: AWS VPC Gateway Types Gateway Type Purpose Internet Gateway (IGW) Enables public internet access for VPC resources (in public subnets). NAT Gateway (NGW) Allows private subnet instances to access the internet outbound only . Virtual Private Gateway (VGW) Enables VPN connectivity to on-premises networks. Transit Gateway (TGW) Connects multiple VPCs and on-premises networks at scale. Egress-only Internet Gateway IPv6-specific gateway for outbound-only internet access from private subnets. PrivateLink / Interface Endpoints Secure, private access to AWS services over AWS network. Gateway Endpoints (S3/DynamoDB) Private access to AWS services without an IGW or NAT. So let's dive in a little deeper. De...
So – another summer camp is over. What was the outcome of this? Was there more to it than meeting some old friends, dive into some slides, get your hands dirty on new versions and finally talk about it over a glass of Portuguese wine or beer? So let’s start at the beginning – where are we right now? In the Process Cloud Service track the global PM Nathan Angstadt kicked of the session by asking how many projects we are on that use PCS and how we get along selling the product. The outcome was somewhat predictable: about one or two participants were on PCS projects, and selling is still a big issue. We discussed the various reasons for that. The main essence was that the PCS is often positioned at previous BPM customers who still have to deal with large BPM implementations and are somewhat afraid of the new PCS-style. BPM and PCS are two different things. They target different customer issues. BPM is still useful when it comes to large scale implementation...