Skip to main content

Guidance for Analyzing Credit Union Member Engagement Data on AWS

Overview

This Guidance helps credit unions build a modern member engagement data analytics pipeline. Credit unions have disparate sources of data, making it difficult for them to derive useful insights. This architecture helps credit unions bring data together in a single location and create visualizations to better understand member behavior and needs. Insights from these visualizations will help credit unions increase engagement through a quality digital experience, especially for those members who prefer to interact virtually rather than visiting in person. 

How it works

These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.

Well-Architected Pillars

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.

Use Amazon CloudWatch for application and infrastructure monitoring. This Guidance can be deployed using infrastructure as code within AWS CloudFormation, allowing for automation for fast iteration and consistent deployments.

Read the Operational Excellence whitepaper 

Lake Formation is used for unified governance to centrally manage access control at the table-, row-, and column-security level. API Gateway enforces policies that control security aspects such as authentication, authorization, or traffic management.

Read the Security whitepaper 

The serverless architecture enables this Guidance to be automatically scalable, highly available, and deployed across all Availability Zones. Services like Lambda, QuickSight, AWS Glue, Athena, and Amazon S3 are managed services that span multiple Availability Zones within a Region to allow for built-in resiliency. 

Read the Reliability whitepaper 

By using serverless technologies, you provision only the exact resources you need. To maximize the performance of this Guidance, test it with multiple instance types. For example, you can use Amazon API Gateway Edge endpoints for geographically dispersed customers. An edge-optimized API endpoint is best for geographically distributed clients. API requests are routed to the nearest Amazon CloudFront point of presence for regional customers (and when using other AWS services within the same Region).

Read the Performance Efficiency whitepaper 

By using serverless technologies that automatically scale, such as Amazon S3, Lambda, Athena, DataSync, and Amazon AppFlow, you pay only for the resources you use. Serverless services do not incur costs while they’re idle.

Read the Cost Optimization whitepaper 

The data lake automatically moves infrequently accessed data to cold storage with Amazon S3 Lifecycle configurations. By extensively using managed services and dynamic scaling, this architecture minimizes the environmental impact of the backend services.

Read the Sustainability whitepaper 

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.