# [Web 2][AWS] VPC endpoints **Published by:** [2qov3b](https://paragraph.com/@2qov3b/) **Published on:** 2022-01-04 **URL:** https://paragraph.com/@2qov3b/web-2-aws-vpc-endpoints ## Content An automobile company uses a hybrid environment to run its technology infrastructure using a mix of on-premises instances and AWS Cloud. The company has a few managed instances in Amazon VPC. The company wants to avoid using the internet for accessing AWS Systems Manager APIs from this VPC. As a Systems Administrator, which of the following would you recommend to address this requirement?Ref: https://docs.aws.amazon.com/vpc/latest/userguide/how-it-works.html#what-is-privatelink https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-create-vpc.html Ans: You can privately access AWS Systems Manager APIs from Amazon VPC by creating VPC Endpoint - A managed instance is any machine configured for AWS Systems Manager. You can configure EC2 instances or on-premises machines in a hybrid environment as managed instances. You can improve the security posture of your managed instances (including managed instances in your hybrid environment) by configuring AWS Systems Manager to use an interface VPC endpoint in Amazon Virtual Private Cloud (Amazon VPC). An interface VPC endpoint (interface endpoint) enables you to connect to services powered by AWS PrivateLink, a technology that enables you to privately access Amazon EC2 and Systems Manager APIs by using private IP addresses. PrivateLink restricts all network traffic between your managed instances, Systems Manager, and Amazon EC2 to the Amazon network. This means that your managed instances don't have access to the Internet. If you use PrivateLink, you don't need an Internet gateway, a NAT device, or a virtual private gateway. ## Publication Information - [2qov3b](https://paragraph.com/@2qov3b/): Publication homepage - [All Posts](https://paragraph.com/@2qov3b/): More posts from this publication - [RSS Feed](https://api.paragraph.com/blogs/rss/@2qov3b): Subscribe to updates