AppMod Toolkit

Deployment Guide

1. Application Modernization Toolkit.....................................................................................3

1.1. Introduction.....................................................................................................................3
1.2. Overview...........................................................................................................................3
1.3. Benefits.............................................................................................................................3
1.4. Use Case...........................................................................................................................3
1.5. Features............................................................................................................................4
2. Architecture..............................................................................................................................5
2.1 Solution Architecture....................................................................................................5
2.2 AWS services list............................................................................................................6
2.3 Open Source or 3rd Party software list....................................................................6
2.4 Deployment.....................................................................................................................7
2.4.1 SSL Certificate.................................................................................................................8
2.5 Time to deploy................................................................................................................8
2.6 Upgrade and Patching..................................................................................................8
2.7 Supported Regions........................................................................................................8
2.8 Technical Pre-requisites..............................................................................................8
2.9 Technical Skills...............................................................................................................9
2.10 Environment Configurations......................................................................................9
3. Security Integration................................................................................................................9
3.1 Deployment Privileges...............................................................................................10
3.2 Authentication & Authorization...............................................................................10
3.3 Encryption......................................................................................................................10
3.4 Secrets Management..................................................................................................10
3.5 Cloud Trail configuration...........................................................................................11
3.6 Regulatory compliance..............................................................................................11
4. Cost (Billable).........................................................................................................................11
4.1 Service Costing.............................................................................................................11
4.2 Solution Costing...........................................................................................................11
4.3 Solution Sizing..............................................................................................................12
5. Installation / Deployment...................................................................................................12
5.1 Deployment Steps.......................................................................................................12
5.2 Troubleshooting............................................................................................................16
5.2.1 Deployment Troubleshooting..............................................................................16

1
 AppMod Toolkit
Deployment Guide
5.3 Health Checks...............................................................................................................16
6. Scaling......................................................................................................................................17
7. Support.....................................................................................................................................17
7.1 Scope...............................................................................................................................17
7.2 Support duration..........................................................................................................17
7.3 Support Plan..................................................................................................................17
7.4 Contact............................................................................................................................17
7.5 Issue Management......................................................................................................17
8. Backup & Recovery..............................................................................................................18
8.1 Backup & Recovery.....................................................................................................18
9 Routine Maintenance...........................................................................................................18
9.1 Key & Credentials Change........................................................................................18
9.2 Software Patches and Updates...............................................................................19
9.3 License.............................................................................................................................19
9.4 Service Limits................................................................................................................19
9.5 Emergency Maintenance...........................................................................................19

2
 AppMod Toolkit
Deployment Guide

[Link] Modernization Toolkit

1.1. Introduction
Typical customer problems while migration and modernization of application
cloud includes:
1. Legacy Complexity: Legacy applications often become unwieldy, making it
challenging to understand the business logic embedded in code.
2. Cloud Native Adoption Lag: Organizations want to leverage cloud-native
services for scalability, cost-effectiveness, and flexibility. However,
refactoring monoliths to fit this paradigm can be time-consuming and error
prone.
3. Risk Avoidance: Organizations fear disrupting existing systems during the
transition. They seek tools that minimize risks and provide a clear path for
modernization.

1.2. Overview
AppMod Toolkit is designed to solve the problem of modernizing legacy
applications. It offers a revolutionary solution that leverages cutting-edge
technologies such as GenAI, LLM, and embeddings to seamlessly assess and
transform legacy monoliths into modern, cloud-native stacks. The toolkit aims to
make the process of modernizing legacy applications more efficient, cost-
effective, and secure, while reducing the dependency on functional and technical
SMEs.
Step 1: "Prizm" - Application Study & Assessment
Step 2: "CodeTX" - Application Modernization

1.3. Benefits
1. Reduced effort during assessment and during code translations/upgradation
2. Target architecture in compliance with the hyperscaler’s “Well Architected
Framework”
3. Secured & complaint application after migration.
4. Accelerated application modernization through scaled deliver.

1.4. Use Case

Use Case Description
AppMod Toolkit
Detailed 1. Customers can upload the application artifacts (Code base,
Assessment Database Schema, Documentation, etc.). The Toolkit
triggers chain of events to analyse the uploaded artifacts.
2. The detailed assessment Code, Document and DB Schema.
Application 1. Microservices recommendation with Service extraction
Modernization dashboard
2. Component Call Graph.
Project 1. Extract the application overview with list of User Stories.
3
 AppMod Toolkit
Deployment Guide
Documentation
Knowledge 1. Code analysis and functional documentation
Transfer
CodeTx
Code Upgrade 1. Application modernization from legacy to modern
and remediation. technologies
2. Upgrade application stack.
3. Remediated code verification before upgrade.

1.5. Features
Application Modernization Toolkit has below prominent features:
 User friendly interface
 Catalogue of typical patterns that can be reused across application
with minor adaptations.
 Tool can be tailored as per customer need.
 Single tool for assessment & migration of both Code and Database
schema
 Certified and Accredited Architect as core member of the tool product
team
 One Click deployment to enable accelerated deployment of tool in
customer environment.

[Link]
2.1 Solution Architecture

Figure 1 Solution Architecture

4
 AppMod Toolkit
Deployment Guide
1. User can access the front-end application and authenticate.
a. The UI is deployed in Amazon S3 and is accessed via AWS CloudFront.
b. User is authenticated by AWS Cognito Users.
c. Role based access is managed specified endpoints as per the application usage.
d. The backend API endpoints will be behind AWS ALB.

2. Upload the application artifacts to Amazon S3.

 The Amazon S3 buckets are encrypted by KMS
 Add the code files to Amazon SQS for further processing.
 The application artifacts are examined with the aid of AWS
Bedrock by using predefined Prompts.
3. At every file processing stage, the metadata and audit logs are saved to
AWS RDS for tracking and reporting.
4. The Embeddings are created for Documents and Database schema for
interactive questioning and querying. These embeddings are stored in
AWS S3.
 The Documents and Database schema are examined with the aid of
AWS Bedrock by using predefined Prompts.
5. CodeTx is hosted in EC2 for its higher memory capacity and long
processing needs.
 CodeTx utilizes Amazon Q for Version Upgrade.
6. ALB and CloudFront will be protected by AWS WAF with Rate limit and IP filtering along with
other rules.
7. The Bastion host will be deployed in public subnet to RDS administration
access.

The application monitoring is managed by AWS CloudWatch while the AWS

services accessed is managed by AWS IAM Roles and Policies.

2.2 AWS services list

The following tables shows what services are used to deploy AppMod Toolkit
and CodeTx on AWS. These services and permissions are required for the
Toolkit to perform its tasks.

2.2.1 AWS Services for AppMod Toolkit

AWS Service Usage

Amazon VPC Virtual Private Cloud

EIP Elastic IP addresses for AWS Application Gateway

ALB Distribute traffic to Lambda functions.

Amazon RDS Relational Database, PostgreSQL

Amazon S3 For storing the Files for processing

5
 AppMod Toolkit
Deployment Guide
AWS Lambda Serverless trigger to process file from ALB, AWS S3 bucket
and SQS
AWS IAM IAM User, Roles, and Policies for various AWS service access.
CloudFront The Frontend code, developed in Angular, is deployed in S3
backed and is accessed from CloudFront.
AWS Cognito The application access is managed with AWS Cognito users
and groups.
Amazon Monitoring the Application and infrastructure health and
CloudWatch events
AWS For Tracking User Activity and API access
CloudTrail

2.2.2 AWS Services for CodeTx

AWS Service Usage

Amazon VPC Virtual Private Cloud

EIP Elastic IP addresses for AWS Application Gateway

ALB Distribute traffic to Lambda functions.

Amazon RDS Relational Database, PostgreSQL

Amazon S3 For storing the Files for processing

Amazon EC2 CodeTx Deployment.

AWS IAM IAM User, Roles, and Policies for various AWS service access.
AWS Cognito The application access is managed with AWS Cognito users
and groups.
Amazon Monitoring the Application and infrastructure health and
CloudWatch events
AWS For Tracking User Activity and API access
CloudTrail
Amazon Q Code Tranhformation

2.3 Open Source or 3rd Party software list

Following software has been used with The AppMod Toolkit application.

Software Version
Angular 16.2.0
Python 3.11
Java 17
fastapi 0.95.2
pydantic 1.10.5
6
 AppMod Toolkit
Deployment Guide
uvicorn 0.26.0
psycopg2-binary 2.9.9
boto3 1.34.84
langchain 0.0.338
python-jose 3.3.0
diff2html 3.4.47
dom-to-image 2.6.0
file-saver 2.0.5
Highcharts 11.1.0
highcharts-angular 3.1.2
html2canvas 1.4.1
[Link] 0.10.1
Jspdf 2.5.1
jspdf-autotable 3.7.1
jwt-decode 4.0.0
OpenRewrite 8.24
AWS SDK 2.x

2.4 Deployment
The AppMod Toolkit solution utilizes Bedrock Lambda, SQS and S3 as the core
native services.
SAM Templates are used to automate the deployment of the AppMod Toolkit
solution.
Below table summarizes the resources created for the Application Modernization
Toolkit

Amazon  VPC A VPC with 1 public & 1 private

VPC  Subnet subnets for each zone.
 Internet Gateway An internet-gateway.
 NAT Gateway A NAT gateway so resources in
 Route Tables private subnets can access the
internet.
EIP  Elastic IP address For ALB
ALB  Application Load Triggering AWS Lambdas
Balancer
Amazon  DBSubnetGroup The relational database with Multi-
RDS  DBInstance AZ enabled for high availability.
 SecurityGroup
Amazon  Bucket The AWS lambda function that
S3-  Lambda triggers when a file is uploaded to
Lambda  Roles S3 Bucket with event message.
Granular Roles are created for
Lambda functions
AWS IAM  IAM User The user created for the pod
7
 AppMod Toolkit
Deployment Guide
 IAM Access Key deployments
Amazon  FIFO Queues To process code files sequentially
SQS  Queues
Amazon  Us-east-1 Bedrock Consume LLMs for Generative AI
Bedrock service tasks

 Network configuration.
o VPC is configured with [Link] /16 CIDR range.
o 2 Private subnets for Lambda functions and RDS with CIDR
[Link]/24 and [Link]/24
o 2 Public subnets for ALB with CIDR [Link]/24, [Link]/24.
o Standard Route Table configuration – Private subnets have only
connectivity within the VPC, and public subnets have connectivity via
internet gateway.
Security Groups
o DBSecurityGroup allowing PostgreSQL inbound traffic on port 5432
from ALB ALBSecurityGroup.
o ALB allowing access on port 443 from Internet.

2.4.1 SSL Certificate

The toolkit connects to the RDS with IAM role. The python code requires SSL certificate to
connect to RDS. This SSL certificate is managed by AWS. This is downloaded from AWS provided
certificate bundle for specific AWS Region. It is available at
[Link]
[Link] .
The certificate is part of code bundle where database connection is necessary.
AppMod toolkit doesn’t create or utilize any KMS keys.

2.5 Time to deploy.

The average time for deployment is approximately 3 hours for the end-to-end
deployment including time for the SAM Templates to run along with
provisioning of all the resources and deployment of the Lambda.

2.6 Upgrade and Patching

Any upgrade to the application code will be managed by build and deploy
process of App Mod Toolkit. The application uses AWS managed services;
hence it will follow default patching schedule.

2.7 Supported Regions

The Toolkit has dependency on AWS Bedrock and toolkit will be supported in
the regions where AWS Bedrock is available.
The AWS Bedrock is available in US East (N. Virginia), US West (Oregon), Asia
Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe
(Frankfurt), Europe (Paris) regions.

2.8 Technical Pre-requisites

AppMod Toolkit solution will be deployed in Customer’s environment.

8
 AppMod Toolkit
Deployment Guide
 Customer needs to have an AWS Account and a user configured with
Administrator privileges. We recommend that root user should not be used for
solution deployment as prescribed by AWS best practices and is secured by
MFA.
 For build ad deployment of the toolkit, internet access is required to
download the dependent components.
 The registration of DNS is required before start of the Toolkit deployment.
This is used in ALB configuration of the Toolkit.
 For deployment of Toolkit, the AWS CloudShell must be updated with Python
3.11, and poetry.
 Customer must procure Amazon Q for Developer license and be configured
with SSO integration in place.
 Customer must manage the necessary steps to ship the Code and
Infrastructure zip file to Customer environment (VDI, etc.) and AWS
CloudShell.

2.9 Technical Skills

 Linux CLI experience is helpful to run (Copy Paste) some command line
scripts. Basic AWS understanding would be desirable.
 Good understanding of CloudFormation/ SAM Templates and SAM CLI.

2.10 Environment Configurations

SAM template deploys all the required resources, application services, IAM roles,
CloudFront configurations. SAM Templates also includes configuration for OS and
environment variables.
There are few input parameters which needs to be passed while executing SAM
template. Those are:
1. ApplicationName: app-mod
1. AppRegion: us-east-1
2. BackupRetentionPeriod: 7 (days)
3. BedrockEmbeddingId: [Link]-embed-text-v1
4. BedrockModelId: [Link]-v2:1
5. DatabaseName: app-mod-db
6. DatabasePort: 5432
7. DatabaseUser: migrationapp
8. DBInstanceClass: [Link]
9. DbStorage: 20 (Gb )
[Link]: ai-developer-assist-storage
[Link]: dev|qa|prod
[Link]: 0 (disabled)

[Link] Integration
The AppMod Toolkit application has used best practice approach to secure
and protect client’s data. The security standards recommended by AWS were
also taken into consideration for AppMod Toolkit deployment on AWS
platform.

9
 AppMod Toolkit
Deployment Guide
Customers need to create/provide IAM user with permission to execute the
SAM template and create roles/policies. We recommend customer not to use
root user for any AWS deployment activities, however root user will be used
for monitoring budgets and bills on AWS console.
The core logic is deployed as AWS Lambda which implements Fast API, giving
api like behaviour by the Lambda. The Lambda functions will be exposed via
ALB.
S3 buckets are encrypted with SSE-S3 keys.
The RDS connection will be managed with IAM Authentication.
Access to the application is managed with Amazon Cognito. The Users are
assigned to group to manage access to application functionality.
The users from Admin group can upload the code for processing and can also
go through other functionalities e.g. QnA. The user who are not member of
Admin group will be restricted to access Admin functions like upload the code
or Code conversion.

3.1 Deployment Privileges

The AppMod Toolkit does not need AWS root privileges for deployment. We
recommend customer to create an Administrator role to deploy the
application.
When you set permissions with IAM policies, grant only the permissions
required to perform a task. We are following least-privilege permissions
principle while defining IAM Policies by applying narrowly scoped
privileges/permissions for the AWS services that need to be integrated.

3.2 Authentication & Authorization

Currently the system has AWS IAM roles created for Service interactions. The
Toolkit has granular roles for each Lambda access. Here is high level
permission for the Roles.

Roles/User Service Access Provided (R/W)

Name
LambdaExecutionRole S3 PutObject
GetObject
ListObject
Lambda AssumeRole
Cloudwatch CreateLogGroup
CreateLogStream
PutLogEvents
SQS SendMessage
ReceiveMessage
DeleteMessage
GetQueueAttributes
Bedrock InvokeModel
InvokeModelWithResponseStrea
m
RDS rds-db:connect

10
 AppMod Toolkit
Deployment Guide
App mod Toolkit deployed in the same security group thus restricting invocation
from any services outside infrastructure. Public access to RDS is restricted.

Role/User Name Description

LambdaExecutionRole Role assumed by the lambda to call
AWS services. The policies are defined
with required Actions and Resources
according to the principle of least privilege
principle.
3.3Encryption
No confidential data is stored by the application on S3. However, S3 bucket is
encrypted with SSE-S3 keys. Additional security needs based on the content of
the file will be assessed and applied based on customer requirement.
CodeTx utilizes EFS for processing data storage. EFS data at rest is encrypted
using default AWS KMS key for Amazon EFS (aws/elasticfilesystem). Data in
transit is encrypted by mounting the file system through TLS 1.2.

3.4Secrets Management
There is no confidential information required for AWS services. The master
credentials for RDS will be stored in Secrets Manager and will be managed by
RDS Service. Every service-to-service communication is IAM based. Only human
intervention with RDS is done with username/password.

3.5 Cloud Trail configuration

We are utilizing CloudTrail tracking user activity and API usage.

3.6 Regulatory compliance

Regulatory compliance will be incorporated based on customer requirements by
extending the automation scripts and Toolkit code.
The Toolkit does not log any Code or any other artifact contents in AWS
CloudWatch.

[Link] (Billable)
4.1 Service Costing
The table below lists the minimum billable and non-billable AWS
services to deploy AppMod Toolkit on AWS.

NOTE: AWS subscription is owned by the customer and billed to the

customer.

AWS Service Billable Mandatory

Amazon VPC Billable Yes

EIP Non-Billable Yes

ALB Billable Yes

11
 AppMod Toolkit
Deployment Guide
Amazon Bedrock Billable Yes

Amazon RDS Billable Yes

Amazon S3 Billable Yes

AWS Lambda Billable Yes

Amazon EC2 Billable Yes

AWS IAM Non-Billable Yes

Amazon SQS Billable Yes
Amazon CloudWatch Billable Yes

AWS CloudTrail Billable No

Amazon Q Billable Yes

4.2 Solution Costing

It will be finalized per customer basis depending on the customization
required. Onetime fee is charged to the customer and will be baked in the
overall pricing.

4.3 Solution Sizing

The region must support at least 2 different zone for subnets (1 public and 1
private subnet in each zone).
For RDS, a [Link] will be used with Multi-AZ deployment.
CodeTX will be deployed in EC2 of instance type [Link]. This is deployed
with Autoscaling defined with desired capacity as 1.

[Link] / Deployment
5.1 Deployment Steps
The [Link] file provides the detailed steps for the deployment.
 Provision an AWS CloudShell environment.
To provision an AWS Cloudshell environment, click on the CloudShell
environment icon on the top right.

12
 AppMod Toolkit
Deployment Guide
This will provision a new cli

 App Mod Toolkit will be deployed using SAM templates and source code.
These deployment artifacts will be shared bundled in a zip file “app-mod-
[Link]”. Unzip the file in CloudShell.
o In AWS CloudShell:
 Open your terminal.
 Upload the [Link] to CloudShell.
 Create a new directory app-mod-toolkit in
 Unzip the file into the folder.
 Run command:
unzip [Link] -d app-mod-toolkit

 This will extract the contents into your current folder as can be
seen

 Go to app-mod-toolkit folder
13
 AppMod Toolkit
Deployment Guide
 Run sam cli command : sam build

 After successful build run the next sam cli command , sam deploy –guided

14
 AppMod Toolkit
Deployment Guide

 Following Microservices (to be deployed on AWS Lambda) and AWS Lambda

code bases will be deployed in the customer AWS account, which can be
modified based on the business requirement.
1. lmbd-app-mod-prod-monolithanalyser
2. lmbd-app-mod-prod-monolithanalyser-appinfo
3. lmbd-app-mod-prod-monolithanalyser-s3trigger
4. lmbd-app-mod-prod-monolythanalyser-extractbre
5. lmbd-app-mod-prod-monolithanalyser-functional-inference
6. lmbd-app-mod-prod-assesment-extract-embedding

15
 AppMod Toolkit
Deployment Guide
7. lmbd-app-mod-prod-monolythanalyser-codeassesmentapi
8. lmbd-app-mod-prod-monolithdecomposer-report
9. lmbd-app-mod-prod-assessment-api
[Link]-app-mod-prod-assessment-extractzipfile
[Link]-app-mod-prod-assesment-extract-embedding
[Link]-app-mod-prod-plsql-analyser-api
[Link]-app-mod-prod-plsqlanalyser-extractzip
[Link]-app-mod-prod-plsqlanalyser-fileinfo
[Link]-app-mod-prod-languageconversion
[Link]-app-mod-prod-db-assessment-api
[Link]-app-mod-prod-monolythanalyser-codeassesmentapi
[Link]-app-mod-prod-monolythanalyser-extarctembedding
[Link]-app-mod-prod-monolythanalyser-codereview
 For deploying the Toolkit the SAM template along with source code will be
executed on customer AWS Account.

5.2 Troubleshooting
5.2.1 Deployment Troubleshooting.
The AWS infrastructure provisioning is managed by SAM template. However,
any AWS infrastructure related error can be seen in AWS CLI Console. The
possible errors are listed below.
 There could be an error creating AWS S3 buckets because of Account
Limits. The S3 Bucket limit can be increased by raising AWS Support
ticket.
 The SAM templates are designed to provision the necessary resources
including Roles. However, for any permissions issue, account level
restrictions can be checked with AWS Account owner.
 For any CloudFormation deployment error go to specific CloudFormation it
failed on and check its event logs. Make sure valid parameters is being
passed. After that's done, delete the specific stack where it failed on, and
rerun the deployment script.
 During deployment, SAM template uploads the Lambda code into S3
buckets. Before deleting those S3 buckets, the contents needs to be
cleared.

16
 AppMod Toolkit
Deployment Guide
5.3 Health Checks
The AppMod Toolkit health can be monitored utilising the custom CloudWatch
dashboard. Following are the list all the components required in Toolkit for which
dashboards are available.
1. Lambda
2. Bedrock
Example screenshot is provided below.
The main dashboard will show the holistic view of all the AWS services used for
the application.

Figure 2 AppMod Toolkit Dashboard

[Link]
AWS Lambda functions are scalable to handle the Toolkit load.

[Link]
7.1 Scope
Run Support for the solution will be provided to customers based on SoW and the
cost would be calculated for the same based on the duration.
 Bug fix support
 Modification and feature request
 Support staff will be available as per the SLA defined by customer
17
 AppMod Toolkit
Deployment Guide
7.2 Support duration.
Support duration for the platform will be based on the SOW signed between
Eviden and the customer for whom the AppMod Toolkit solution will be deployed.

7.3 Support Plan

Typical support hours will be a working business day and will be signed based on
the customer business needs and contract. Since the product is always sold with
services, engineering team contact will be shared Atos Project teams only.

7.4 Contact
Contact details will be provided when SoW is signed for the platform.

7.5 Issue Management

Customer will have options e.g., low, medium, high whilst creating a ticket.
Based on the priority the tickets will be picked up and resolved.
Standard Response Time: This is the typical initial response time in business
days to acknowledge the receipt of support requests.
 Severity 1 - Within four (4) working hours
 Severity 2 - Within one (1) business day
 Severity 3 - Within one (1) business day
 Severity 4 - Within one (1) business day
Standard Resolution Time: This is the typical time in business days to resolve
support requests excluding the intervals between Eviden requesting
information / data from the Client and receiving the same.
 Severity 1 - Within one (1) business day
 Severity 2 - Within two (2) business days
 Severity 3 - Within four (4) business days
 Severity 4 - Within ten (10) business days
Training on the usage of AppMod Toolkit Training provided to
Authorized users:
 Recorded videos on how deploy the AppMod Toolkit AWS Platform
 Recorded Videos on AppMod Toolkit AWS features (template creation,
updating etc.)

[Link] & Recovery

8.1 Backup & Recovery
Customer can recover the software by running the SAM templates again. Then
he needs to Then he must import the backed data into RDS by following the
steps in backup and recovery as provided below

To restore a DB instance from a DB snapshot

1. Sign into the AWS Management Console and open the Amazon RDS
console at [Link]
2. In the navigation pane, choose Snapshots.

18
 AppMod Toolkit
Deployment Guide

3. Choose the DB snapshot that you want to restore from.

4. For Actions, choose Restore snapshot.
5. On the Restore snapshot page, for DB instance identifier, enter the
name for your restored DB instance. Give the instance identifier as the old
database name. (e.g., rds-ces-cn-dev-masterdb-cwtcjtpcitrl0)
6. Specify other settings, such as allocated storage size.
7. Choose Restore DB instance.
Point the application to new restored database.
For CodeTx restart the EC2 instance in case it is in Stopped state. In case of any
failure in the EC2 instance, same can be provisioned again using CloudFormation
template.

9 Routine Maintenance
9.1 Key & Credentials Change
AppMod Toolkit uses AWS managed services, and the keys are AWS managed.
There are no Eviden Managed keys. The database master password will be
rotated automatically by RDS service. To connect to the database, this password
can be retrieved from Secrets Manager.
The master database password is used only for interacting with database from
server management tools. The application uses IAM based database calls.

9.2 Software Patches and Updates

Eviden will provide detailed documentation, support and sample code for any
emergency patches which are critical in nature with respect to the platform or
the application services.

The documentation will detail the reference of impacted AWS resources along
with related code artifacts. The SAM templates, build code, database scripts will
be shared along with deployment steps.
Lambda automatically applies patches and security updates to all managed
runtimes and their corresponding container base images.
AWS EC2 instances will be patched using AWS Systems Manager Patch Manager.
The patch policy feature will be used to automate for scanning and installing
patches to EC2 instances

9.3 License
AppMod Toolkit will be provided as an Accelerator to the customer. It does not
involve any subscription or Licences fees. Eviden will be providing AppMod
Toolkit solutions Architect, Platform expert and Developers to get the solution up
and running on customer environment as part of the SOW/contract.

9.4 Service Limits

Customer must manage the AWS service limits. We recommend customers to
use new account rather than existing account. This will avoid limit clash with
existing AWS services.

19
 AppMod Toolkit
Deployment Guide
They can use the AWS Trusted Advisor service to monitor the usage against
limits.

9.5 Emergency Maintenance

 Raising the vCPU limit for the RDS can be done if health check indicates that
RDS starving for resources.
 If the EC2 is showing high utilization and needs to be scaled, then
Autoscaling definition can be edited to increment the resources capacity.
 In case of Lambda throttling because of unreserved capacity, bring the
reserved capacity for the specific Lambda. The Lambda functions e.g.
Language conversion is configured to have the Reserved Concurrency to
one. The Toolkit lambda functions however execute with default limit of
unreserved account concurrency. The maximum concurrency observed is 15
for a medium size application.

20