Steps:

Coments:

1. Consolidate all current versions in Nesh domain
2. Create a distribution, tar, file for each of the client current ams complete distribution
3. FTP to the AWS and unpack into the main server,
4. Perform fine cleanup and make an image for each distribution in the individual/working server,
5. Keep separate the Base/Generic Image
6. Support communication https://ams-support-wsdp.com/
7. One Image can be used for up to four instances, Dev, Test, UAT, and Prod
8. AWS and any cloud AMS instance must be standalone
9. Only on-prem servers could have multy AMS installed
10. Exclude $Tool/AuthCode.pl from all Distributions and Images.

• keep PHP version 7.4.3
• explore Ubuntu upgrade to the latest stable
• create mini server using the image containing all ams systems
• use the same all systems image to create individual system immages
• work on demand is to be conducted using individual images ( always latest I'd presume ), or in local if more complete environment is required, after which the aws image would be updated.
• Pricing based on number of Instances, like 1-5, 6-10, and so on, and the License duration (which can be extended on request and charged acordingly )
• Apart of the AMS package, application development could also be offered.
• All currently lincesed instances are elegible for updates, upgrades, if accepted bu customer.

54-66-222-10

13-211-159-20

AMS product page on AWS MP should have explanation regarding licensing:
The AMS image is free for 1 month and further arangements will be arranged via appropriate communication (email, omline meeting, and sim.)
All this should be made clear to the customer via product description:

Highlights 1 and 2

addition for aws S3 access -

sudo apt-get update ,

cpanm Net::Amazon::S3

sudo apt-get install libnet-amazon-s3-perl ,

env var in sysenv

export PERL5LIB=

$PERL5LIB:/home/ssm-user/perl5/lib/perl5

Change all .pl reading files to handle S# access

use Net::Amazon::S3;

use Net::Amazon::S3::Authorization::Basic;

use Net::Amazon::S3::Authorization::IAM;

    my $s3 = Net::Amazon::S3->new (

           authorization_context => Net::Amazon::S3::Authorization::Basic->new (

             aws_access_key_id     => $aws_access_key_id,

             aws_secret_access_key => $aws_secret_access_key,

           ),

           retry => 1,

         );

https://manpages.ubuntu.com/manpages/lunar/man3/Net::Amazon::S3.3pm.html

ams_dqm_2tb
ams_dqm_2tbR

ams_dqm_DP

ams_dqm_DVC

ams_dqm_DVC.Current

ams_dqm_DVC.DBG

ams_fl2tb

ams_get_coll_list

ams_get_coll_list_IO

ams_get_coll_list_IO-devel

Purchase:

• Customer using its AWS account makes a choice to purchase AMS from AMS-WSDP. 
• Trough the purchase process customer provides (using a form) all details required (TBD) including the the period for which the License will be purchased,.
• There will be 3 months cooling period which would allow customer to decide if the system is the right choice for the purpose. The price for the 3 months TBD.
• This step needs to be explored in details including Peter SF.
• The product purchased is precompiled aws AMS image.

Customatisation

• AMS team, apon receving comitment/payment and using customer details provided via the purchase form, creates Authorisation file, which will be sent to the customer along with Wellcomme Pack and intructions explaining initial steps.
• we need to discuss if anything else is needed

Deployment

• Customer uses the Image from the previous step to speenup a AWS server
• Customer makes various choices according to AWS requirementsand Wellcome Pack Instructions
• we need to provide recomendations ( memory, storage, elastick IP,  . . .  )
• AWS provides a FREE hhtps Cerificate fif certain features are included in to package, like elastic IP, ...

Post Deployment

• AMS team should verify the deployment is correctly performed and the sufficient aws features are included into the Customers package. 
• Also all important steps outlined in the Welcome Pack are performed.
• AMS team is available 24x7 the first 3 months after the deployment.
• Setup performed by Customer. See Prerequisites below.

Options

• pricing depending on number of instances
• pricing depending on the license duration
• level of support and pricing model

Support

• 24x7 the first week after deployment, email, skype, zoom, on-site (if possible), teams, phone, google-meet, ...
• ams-wsdp support portal :
• Casual                NA
• Basic                  0%           Default
• Standard            10%  LP
• Advanced           20%  LP
• Expert                 30%  LP
• Non Basic Support can be arranged for a certain period of time or times within the license period. LP is License Price

Prerequisites: below should be in the Welcome Pack

• replace initial admin with the Company Admin. 
• all sources and targets defined and pointed in the db table
• freetds.conf
• /etc/odbc.ini

Current Systems:

• ccamlr
• nemo
• dory
• npfc
• tropic bird

In ams-wsdp.com , projects TAB elaborate in some details on all applications.
This TAB should explain AMS Features applied.

BUILDING BUSINESS STRATEGY

Define customer base, first 10 (eg) , charge application development only.
To be used as a refference point(s).