Guidance for SWIFT Alliance Access on AWS
Overview
This Guidance enables financial institutions to integrate SWIFT Alliance Access with AWS infrastructure through a secure, cloud-optimized architecture. By leveraging deployment across two Availability Zones and aligning with SWIFT Customer Security Programme (CSP) requirements, it accelerates the transition to modern financial messaging while ensuring operational resilience, enhanced scalability, and robust compliance.
How it works
Alliance Connect Virtual Gold
This architecture diagram shows a standardized environment for connecting to the SWIFT network using Alliance Connect Virtual Gold connectivity.
Alliance Connect Virtual Silver
This architecture diagram shows a standardized environment for connecting to the SWIFT network using Alliance Connect Virtual Silver connectivity.
Alliance Connect Virtual Bronze
This architecture diagram shows a standardized environment for connecting to the SWIFT network using Alliance Connect Virtual Bronze connectivity.
Benefits
Streamline financial messaging operations
Deploy a highly available SWIFT connectivity solution across multiple Availability Zones. Focus on your core financial services while AWS manages the underlying infrastructure for your SWIFT Alliance Access environment.
Enhance security and compliance
Implement defense-in-depth strategies with private subnets, encrypted communications, and centralized key management. Meet SWIFT CSP requirements while simplifying security management across your financial messaging infrastructure.
Optimize costs with flexible deployment options
Scale your SWIFT Alliance Access environment based on transaction volumes with right-sized compute resources and optional database deployments. Reduce capital expenditure by paying only for the resources you use.
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.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages