AWS re:Invent 2016: Disaster Recovery and Business Continuity for Systemically Important Financial Institutions (FIN302 )
•
5 likes•6,815 views
Modern financial services organizations rely heavily on technology and automated systems to run business-as-usual. However, if this technology were interrupted by natural disasters or other events, there could be a devastating impact on investors and market participants, and in turn your reputational brand. In this session, we provide a step-by-step disaster recovery solution employed by a major exchange. This solution leverages Amazon EC2 Container Service to provide Docker containers, Weave Net to support a multicast overlay network that enables high volume multicast feeds in a cloud environment, and AWS CloudFormation for the ability to easily create and manage AWS assets. The session also covers the importance of redundancy (not just operationally, but for SEC compliance reasons as well) and how financial services organizations can increase geographical diversification of their primary and disaster recovery data centers. We dive deep into each major component of the solution.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to AWS re:Invent 2016: Disaster Recovery and Business Continuity for Systemically Important Financial Institutions (FIN302 )
Similar to AWS re:Invent 2016: Disaster Recovery and Business Continuity for Systemically Important Financial Institutions (FIN302 ) (20)
More from Amazon Web Services
More from Amazon Web Services (20)
Recently uploaded
Recently uploaded (20)
AWS re:Invent 2016: Disaster Recovery and Business Continuity for Systemically Important Financial Institutions (FIN302 )
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. November 28, 2016 Disaster Recovery and Business Continuity for Systemically Important Financial Institutions Felix Candelario, Solutions Architect Benjamin Feldon, Solutions Architect FIN302
- 2. The takeaway Systemically important workloads for Financial Services are running on AWS Disaster Recovery can be automated, auditable, & elastic You can leverage AWS for Disaster Recovery while meeting your regulatory requirements
- 3. Agenda • Modernizing Disaster Recovery • Trading refresher • Customer Implementation • Disaster Recovery demo
- 5. Current Disaster Recovery methods Manual Capital intensive Infrequently tested
- 7. Securities Exchange Commission “having due regard for the public interest, the protection of investors, and the maintenance of fair and orderly markets, to use its authority under the Exchange Act to facilitate the establishment of a national market system for securities in accordance with the Congressional findings and objectives set forth in Section 11A(a)(1) of the Exchange Act.” [Release No. 34-73639; File No. S7-01-13]
- 8. Regulation Systems Compliance and Integrity • RegSCI requires • “comprehensive policies and procedures in place to help ensure the robustness and resiliency of their technological systems” • “geographical diversity” • “a two hour recovery goal would be required for recovery facilities”
- 11. Trading at Exchanges Customers Broker/Dealers Exchange Bid Ask QTY Price QTY Price 300 25.10 500 25.12 400 25.09 600 25.13 150 25.08 300 25.14 900 25.06 250 25.15 B|50@$25.11 Bid Ask QTY Price QTY Price 300 25.10 500 25.12 400 25.09 600 25.13 150 25.08 300 25.14 900 25.06 250 25.15 Bid Ask QTY Price QTY Price 500 25.12 300 25.10 600 25.13 400 25.09 300 25.14 150 25.08 250 25.15 900 25.06 Bid Ask QTY Price QTY Price 50 25.11 500 25.12 300 25.10 600 25.13 400 25.09 300 25.14 150 25.08 250 25.15 900 25.06 ACK S|75@$25.11 Bid Ask QTY Price QTY Price 50 25.11 75 25.11 300 25.10 500 25.12 400 25.09 600 25.13 150 25.08 300 25.14 900 25.06 250 25.15 Bid Ask QTY Price QTY Price 50 25.11 75 25.11 300 25.10 500 25.12 400 25.09 600 25.13 150 25.08 300 25.14 900 25.06 250 25.15 Bid Ask QTY Price QTY Price 50 25.11 25 25.11 300 25.10 500 25.12 400 25.09 600 25.13 150 25.08 300 25.14 900 25.06 250 25.15 F|50@$25.11 F|50@$25.11
- 12. General exchange architecture Customer Gateways Matching Engines Market Data Engines
- 14. AEX Properties • 100 symbols listed • Simulated 100 Broker/Dealers • Each Broker/Dealer supports 100 customers • Every customer sends a Buy or Sell order for a random symbol for a random quantity every second Our fictitious exchange – Amazon EXchange DR Strategy
- 15. AEX Tech Stack AWS CloudFormation Troposphere Amazon EC2 Container Service Weaveworks Weave Net Amazon Route 53 Amazon Simple Storage Service (S3) Infrastructure as code Generates CloudFormation templates Container management service Provides container overlay network Highly available and scalable cloud DNS service Captures streaming data to S3Amazon Kinesis Firehose Secure, durable, highly-scalable cloud storage
- 18. Recovery time objective & recovery point objective Disaster Recovery point Recovery time Data loss Down time
- 20. CloudFormation template S3 us-west-2 Firehose RTO ~ 7 minutes RPO = 0
- 33. AEX Architecture AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster Weave Net S3Firehose ECS Cluster ECS Cluster ECS Cluster Route 53
- 34. Weave Net AEX Architecture AWS cloud virtual private cloud Matching Engine Cluster Market Data Cluster S3Firehose ECS Cluster ECS Cluster Route 53 Customer Gateway Cluster ECS Cluster
- 36. AEX Architecture AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster Weave Net ECS Cluster ECS Cluster ECS Cluster Route 53 S3Firehose
- 38. AEX Architecture AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster Weave Net S3Firehose ECS Cluster ECS Cluster ECS Cluster Route 53
- 40. AEX Architecture AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster S3Firehose ECS Cluster ECS Cluster ECS Cluster Route 53 Weave Net
- 44. Conclusion
- 45. CloudFormation template S3 us-west-2 Firehose RTO ~ 7 minutes RPO = 0
- 46. AWS CloudFormation CloudFormation template Source code AWS CodePipeline Modernizing Disaster Recovery Assets Automated testing results Scheduled
- 47. Benefits of modernized Disaster Recovery • Elastic • Auditable • Reusable • Easy geolocation • Reduced attack surface Modernizing Disaster Recovery AWS CloudFormation CloudFormation template Source code AWS CodePipeline AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster Weave Net Assets Automated testing results Scheduled
- 48. Process of modernizing Disaster Recovery • Understand your workload • Evaluate statefulness • Select and monitor replication techniques • Architect • Infrastructure as code • Refactor where necessary • Rehydrate state • Test • Automate Modernizing Disaster Recovery AWS CloudFormation CloudFormation template Source code AWS CodePipeline AWS cloud virtual private cloud Customer Gateway Cluster Matching Engine Cluster Market Data Cluster Weave Net Assets Automated testing results Scheduled
- 49. Thank you!
- 50. Remember to complete your evaluations!
- 51. Related Sessions