CloudFront is a Content Delivery Network service offered by AWS to serve up EVAN360 application content for very quick access. EVAN360 employs CloudFront to be that first line of defense for against malicious attacks by preventing traffic originating from various countries notorious for distributing US-based applications.

Amazon Web Services (AWS) is the service selected for the hosted deployment of the EVAN360 cloud application. AWS was selected for its robust security and reliability. 

Once internet traffic (HTTP and HTTPS) passes through CloudFront, it must get past the EVAN360 firewall. This web application firewall protects the EVAN360 Infrastructure from common application and database vulnerabilities and is configured to block any internet traffic deemed an attack.

No internet traffic can enter VPC unless it passes through the WAF. Each server and database within the VPC must also communicate through the AWS Identity and Access Management (IAM) service Once internet traffic is inside the VPC, it’s routed to the application servers through AWS’s Elastic Load Balancing service and authorized or blocked by the AWS Identity and Access Management (IAM) service.

Elastic Load Balancing serves two purposes.  First, to balance traffic so to prevent slowdowns from occurring when EVAN360 is busy.  Second, to make sure the EVAN360 application is always available in case of a hardware or software failure on any given application server.

The heart of the EVAN360 application lives here, in the EC2 servers. The EC2 servers are designed to scale both up and down as requirements change and usage increases and stay synchronized through the use of AWS ElastiCache.

The heart of the EVAN360 application lives here, in the EC2 servers. The EC2 servers are designed to scale both up and down as requirements change and usage increases and stay synchronized through the use of AWS ElastiCache.

ElastiCache acts as a broker between the EC2 servers by moving session data and information into memory for quick access. This is what makes EVAN360 extremely fast.

S3 serves as the primary place to store files, such as EVAN360 session recordings and transactional data.  S3 is also where our backups are stored ensuring quick restoration of information when or if needed. 

The API Gateway provides access to EVAN360 microservices layer. Microservice-based application architecture allows for applications that can scale by developing small, distinct components, managed separately from the core application hosted on EC2.

AWS Lambda automatically runs the identity management component of the EVAN360 application without requiring application servers (EC2).  As EVAN360 users access our application, traffic is routed through the API Gateway to the Lambda microservice for authentication and authorization.  For added security, the EVAN360 microservices hosted on Lambda sit within their own Virtual Private Cloud.

RDS is the database component of the EVAN360 Infrastructure and is where all EVAN360 configuration, user, provider, session and application data is stored.