Study guide
7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access
AWS Certified Security – Specialty SCS-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Getting Started with the SCS-C03 Exam
0.1 SCS-C03 Exam Format, Domains & Study Strategy
2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services
1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification
3 Chapter 2: Enterprise Logging Architecture & Analysis
2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs
4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks
3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks
5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis
4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective
6 Chapter 5: Edge Protection, WAF & DDoS Mitigation
5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS
7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security
6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect
8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit
7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI
9 Chapter 8: Enterprise Authentication, Federation & Directory Services
8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures
10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation
9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags
11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing
10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation
12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance
11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores
13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI
12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture
14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection
13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults
15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance
14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog
16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing
15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews
7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access
Key Takeaways Explain This Topic AI
Gateway endpoints (S3 and DynamoDB only) work only for traffic inside the VPC; interface endpoints are reachable from on-premises networks over Direct Connect or VPN.
Endpoint policies restrict what can pass through an endpoint but never grant permissions; aws:ResourceOrgID and aws:PrincipalOrgID keep traffic within the organization.
Requests through VPC endpoints don't carry public source IPs, so use aws:SourceVpce, aws:SourceVpc, or aws:VpcSourceIp instead of aws:SourceIp.
A PrivateLink endpoint service behind an NLB lets consumers with overlapping CIDRs connect one way, with allowed principals and manual acceptance.
AWS Client VPN authenticates users with certificates, Active Directory, or SAML and authorizes CIDR access; Verified Access authorizes each request to a specific application.
Last updated: September 2026
7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access
Skill 5.1.2 covers mechanisms for secure and private access to resources : AWS PrivateLink, VPC endpoints, AWS Client VPN, and AWS Verified Access. The exam typically describes a workload or user that must reach a service without crossing the public internet, or a data set that must be reachable only from approved networks, and asks which combination of endpoint, policy, and condition key achieves it.
VPC Endpoints
Feature Gateway Endpoint Interface Endpoint (PrivateLink)
Services Amazon S3 and Amazon DynamoDB only Most AWS services, AWS Marketplace partners, and your own endpoint services
How it works Route table entries that point the service's prefix list at the endpoint Elastic network interfaces with private IP addresses in your subnets
Security groups Not applicable Yes, on the endpoint network interfaces
DNS Uses the public service name; routing changes the path Private DNS makes the standard service hostname resolve to private IPs inside the VPC
Reachable from on-premises or peered VPCs No Yes, over Direct Connect, Site-to-Site VPN, peering, or a transit gateway
Cost No charge Hourly per endpoint per AZ, plus data processing
S3 supports both types: a gateway endpoint is the low-cost default for traffic from the VPC, and an S3 interface endpoint serves on-premises clients that reach AWS over Direct Connect or VPN.
Endpoint Policies
Gateway endpoints and most interface endpoints accept an endpoint policy , a resource-based policy that limits what can be done through that endpoint . The default policy allows full access. Endpoint policies never grant permissions; the caller's IAM policy and any resource policy must also allow the request. A typical policy lets traffic through the endpoint reach only resources owned by your organization, by principals in your organization: {
- "Statement": [
- {
- "Sid": "OrgPrincipalsToOrgResourcesOnly",
- "Effect": "Allow",
- "Principal": "*",
- "Action": "s3:*",
- "Resource": "*",
- "Condition": {
- "StringEquals": {
- "aws:PrincipalOrgID": "o-exampleorgid",
- "aws:ResourceOrgID": "o-exampleorgid"
- }
- }
- }
- ]
- }
This blocks a compromised instance from copying data to an attacker-owned bucket through the endpoint.
Restricting Resources to the Endpoint
On the resource side, a bucket policy can deny requests that don't arrive through an approved endpoint or VPC by using aws:SourceVpce or aws:SourceVpc . Requests through a VPC endpoint carry private addresses, so aws:SourceIp (which evaluates public IP addresses) doesn't match them; use aws:VpcSourceIp for the private address. Add exceptions for AWS services acting on your behalf ( aws:ViaAWSService or aws:PrincipalIsAWSService ), or the deny can break integrations.
Data Perimeters
AWS describes a data perimeter as three sets of guardrails that together ensure only trusted identities access trusted resources from expected networks:
Perimeter Question Answered Typical Condition Keys Where Enforced
Identity Is the caller one of my identities? aws:PrincipalOrgID , aws:PrincipalIsAWSService Resource policies, RCPs, endpoint policies
Resource Is the target one of my resources? aws:ResourceOrgID , aws:ResourceAccount SCPs, endpoint policies
Network Is the request coming from my networks? aws:SourceVpc , aws:SourceVpce , aws:SourceIp , aws:ViaAWSService Resource policies, RCPs, SCPs
RCPs apply identity and network conditions to resources across the organization, and SCPs apply resource and network conditions to your principals.
Publishing Your Own Services with PrivateLink
A service provider puts an endpoint service in front of a Network Load Balancer (or Gateway Load Balancer). Consumers in other VPCs or accounts create interface endpoints to it.
The provider controls allowed principals and can require manual acceptance of each connection request.
Connections are initiated only from consumer to provider; the provider can't reach into the consumer VPC.
Overlapping CIDR ranges don't matter, because no routing between the VPCs is created.
A private DNS name for the service requires domain ownership verification with a TXT record.
This is the standard way to expose a service to many customer or business-unit VPCs without VPC peering or transit gateway routes.
AWS Client VPN
AWS Client VPN is a managed OpenVPN-based service for remote users.
Authentication : mutual certificate authentication (server and client certificates in ACM), Active Directory through AWS Directory Service, or SAML 2.0 federation (for example, with IAM Identity Center). Directory or SAML authentication can be combined with certificates.
Authorization rules grant access to destination CIDR ranges, optionally only for specific Active Directory or SAML groups.
Security groups on the target network associations control what VPN clients can reach.
Split tunnel sends only routes for the VPC through the VPN; full tunnel sends all client traffic through AWS.
A client connect handler (a Lambda function) can run custom checks, such as device posture or time-of-day rules, before a connection is allowed.
Connection logging to CloudWatch Logs records connection attempts and results.
AWS Verified Access
Where Client VPN gives network-level access to CIDR ranges, Verified Access evaluates every request to a specific application against Cedar policies that use identity and device trust data (Section 7.3). It supports HTTP(S) applications and non-HTTP TCP endpoints such as SSH, RDP, and database connections, so it can replace VPN access for many administrative and internal use cases without giving users a route into the VPC.
- Need Choose
- Private access from a VPC to an AWS service Gateway or interface VPC endpoint with an endpoint policy
- Expose an internal service to other VPCs or accounts PrivateLink endpoint service behind an NLB
- Remote users need broad network access AWS Client VPN with authorization rules
- Per-application, identity- and device-aware access without network access AWS Verified Access
- Specialty Exam Pitfalls
Expecting gateway endpoints to work from on-premises : Gateway endpoints are route-table constructs inside the VPC. Use S3 interface endpoints for on-premises access.
Using aws:SourceIp for endpoint traffic : Requests through VPC endpoints don't carry public source IPs; use aws:SourceVpce , aws:SourceVpc , or aws:VpcSourceIp .
Thinking endpoint policies grant access : They only restrict; IAM and resource policies must still allow the request.
Deny-all bucket policies without service exceptions : A strict aws:SourceVpce deny can block AWS services, such as replication or CloudTrail delivery, that call on your behalf.