Access Amazon SQS using Amazon VPC Interface Endpoint

Lab Details

  1. This lab walks you through the steps to create an interface endpoint for Amazon SQS to access with EC2 Instance.

  2. Duration: 90 minutes

  3. AWS Region: US East (N. Virginia) us-east-1

Introduction

VPC endpoint for SQS

  • 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.

Architecture Diagram

Task Details

  1. Launching Lab Environment

  2. Create an SQS Queue and Copy the Queue URL

  3. Create a VPC and Enable DNS Hostnames option

  4. Create and attach an Internet Gateway with custom VPC

  5. Create a Subnet

  6. Configure the Subnet to enable auto-assign public IPv4 address

  7. Add an entry to the Internet (0.0.0.0/0) in the Main Route table.

  8. Create a Security Group for EC2 Instance

  9. Launch an EC2 Instance

  10. SSH into Endpoint instance

  11. Create a VPC endpoint for SQS

  12. Send the message to the SQS queue

  13. Validation of the lab.

  14. Deleting AWS Resources.