This lab walks you through the steps to create an interface endpoint for Amazon SQS to access with EC2 Instance.
Duration: 90 minutes
AWS Region: US East (N. Virginia) us-east-1
VPC Endpoint allows us to securely connect your VPC and supported AWS services powered by AWS PrivateLink. AWS PrivateLink is a service that allows you to access AWS services by using private IP addresses. In this case, traffic does not leave Amazon’s network.
VPC endpoint does not require a NAT Gateway, NAT instance, Internet Gateway, or any VPN services to access AWS Services.
There are two types of VPC endpoints: Gateway and Interface.
VPC endpoint for SQS comes under Interface endpoint.
When you create a VPC endpoint for SQS, it asks for the VPC, Subnet, Security group, and the option of enabling the DNS Endpoint.
Launching Lab Environment
Create an SQS Queue and Copy the Queue URL
Create a VPC and Enable DNS Hostnames option
Create and attach an Internet Gateway with custom VPC
Create a Subnet
Configure the Subnet to enable auto-assign public IPv4 address
Add an entry to the Internet (0.0.0.0/0) in the Main Route table.
Create a Security Group for EC2 Instance
Launch an EC2 Instance
SSH into Endpoint instance
Create a VPC endpoint for SQS
Send the message to the SQS queue
Validation of the lab.
Deleting AWS Resources.