This Guidance demonstrates how to move from on-premises payment hardware security modules (HSMs) to the cloud by connecting to Futurex’s Payment HSM through AWS Marketplace. The architecture applies to various payment functionalities, such as personal identification number (PIN) translation and card verification value (CVV) verification, and complies with regulatory standards for processing sensitive cardholder data.
Architecture Diagram
Step 1
Sign up for a Futurex Payment HSM service on AWS Marketplace. Create a VirtuCrypt Intelligence Portal account.
Step 2
Once the service has been successfully connected to the VirtuCrypt account, create a CryptoTunnel using AWS Virtual Private Network (AWS VPN) over AWS Direct Connect.
Step 3
Provision cloud payment HSMs and assign them to load balancing clusters.
Step 4
Create CryptoTunnels and download Cryptoverse public key infrastructure (PKI) certificates for application authentication.
Step 5
Create an endpoint connection from the Amazon Virtual Private Cloud (Amazon VPC) to the VirtuCrypt Access Point (VAP).
Step 6
Test the connection with an ECHO command to confirm connectivity to the internet.
Step 1
Sign up for a Futurex Payment HSM service on AWS Marketplace. Create a VirtuCrypt Intelligence Portal account.
Step 2
Once the service has been successfully connected to the VirtuCrypt account, create a CryptoTunnel using AWS Virtual Private Network (AWS VPN) over AWS Direct Connect.
Step 3
Provision cloud payment HSMs and assign them to load balancing clusters.
Step 4
Create CryptoTunnels and download Cryptoverse public key infrastructure (PKI) certificates for application authentication.
Step 5
Create an endpoint connection from the Amazon Virtual Private Cloud (Amazon VPC) to the VirtuCrypt Access Point (VAP).
Step 6
Test the connection with an ECHO command to confirm connectivity to the internet.
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational ExcellenceRead the Operational Excellence whitepaper
AWS PrivateLink connects your on-premises networks to private subnets, making it easier to manage your global network through a simplified network architecture.
-
SecurityRead the Security whitepaper
Payment customers connect to the payment HSM from a private subnet and sends commands over private endpoints. Network traffic using PrivateLink doesn’t traverse the public internet, reducing exposure to threats such as brute force and distributed denial-of-service (DDoS) attacks.
-
ReliabilityRead the Reliability whitepaper
This architecture uses a modular approach so that different workloads can scale based on increased demand of transactions.
-
Performance EfficiencyRead the Performance Efficiency whitepaper
PrivateLink connects AWS services across different accounts and VPCs without requiring an internet gateway, network address translation (NAT) device, or public IP address. By controlling access to your VPC, you can manage traffic and data access patterns.
-
Cost OptimizationRead the Cost Optimization whitepaper
PrivateLink optimizes the network path, helping you reduce costs associated with NAT gateways, NAT instances, and firewall maintenance.
-
SustainabilityRead the Sustainability whitepaper
This architecture uses services that can dynamically scale to meet demand. This reduces the amount of compute power required by backend services that would otherwise need to keep running, even when workloads decrease.
Implementation Resources
A detailed guide is provided to experiment and use within your AWS account. Each stage of building the Guidance, including deployment, usage, and cleanup, is examined to prepare it for deployment.
The sample code is a starting point. It is industry validated, prescriptive but not definitive, and a peek under the hood to help you begin.
Related Content
Protect payment workloads through AWS Marketplace with Futurex’s cloud payment HSMs
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.