FullStack AMI Changelog
Description
Patched: Security patches applied on 29-MAY-2023
DB
- MongoDB4.4 installed as service.
- MongoDB3.6 installed as docker.
- BaseDB
- root user password updated
Nginx
- v1.20.x installed
- modsec installed(disabled)
- headers-more module installed
- TLSv1.2 and TLSv1.3 | strong ciphers(updated)
Node
- added v14.20.x
- npm symlinked
Additional features
- lshell
- CodeDeploy, CloudWatch(disabled)
- Docker images: redis, rabbitMQ
- SSH strong ciphers(CTR,GCM)
- Added new User ori-devops.
- Security patched updated
- Installed clamAV
- Modified
- Changed the sshd config
- Added cron job for devops
- Created the
/syncAccessKeydirectory. - Modified the cron job duration for devops.sh to 10min.
| Sr. No | Mumbai | Ireland | N-Virginia |
|---|---|---|---|
| Current | ami-01b8b84e62f64da34 | ami-0d731008f309e3feb | ami-005778813ce017bab |
| Source | ami-0eb56a95c26fff4ba | ami-0e1b4c99fe36b17e3 | ami-0e1b4c99fe36b17e3 |
ID: ami-01b8b84e62f64da34
Latest | Stable
Name: FullStackImage_29-MAY-2023
Release Date: 29th MAY 2023
Type: Security patches updated
Reason for update/Issues in previous version
- Need to update the security patches.
- Need to update codedeploy max_revisions from 5 to 2 in codedeploy.yml file
Changes
- Updated Security patched to be applied.
- Updated codedeploy max_revisions from 5 to 2 in codedeploy.yml file
| Name | ID | |
|---|---|---|
| Current | FullStackImage_29-MAY-2023 | ami-01b8b84e62f64da34 |
| Source | FullStackImage_20-FEB-2023 | ami-0eb56a95c26fff4ba |
ID: ami-0eb56a95c26fff4ba
Stable
Name: FullStackImage_20-FEB-2023
Release Date: 20th FEB 2023
Type: Node version upgradation
Reason for update/Issues in previous version
- Need to remove ntp servers
- Need to upgrade the version of node from 14.17 to 14.20.
- Need to remove jenkins and node repo from yum.
Changes
- Removed ntp public servers
- Updated Security patched to be applied
- Updated node versions from 14.17 to 14.20
- Removed jenkins and node repo from yum
| Name | ID | |
|---|---|---|
| Current | FullStackImage_20-FEB-2023 | ami-0eb56a95c26fff4ba |
| Source | FullStackImage_06-APR-2022 | ami-0e1b4c99fe36b17e3 |
ID: ami-0e1b4c99fe36b17e3
danger
Name: FullStackImage_06-APR-2022
Release Date: 06th APRIL 2022
Type: clamAV installation
Reason for update/Issues in previous version
- Security patched to be applied
- Need to scan and remove the vulnerabilities on the server.
- Need to create the
synckeys_devops.shfile insyncAccessKeysdirectory & - Need to change the duration of cronjob for
synckeys_devops.shfrom 30m to 10m
Changes
- Created the
synckeys_devops.shfile insyncAccessKeysdirectory - Modified the cronjob duration for
synckeys_devops.shfrom 30min to 10min.
- Created the
| Name | ID | |
|---|---|---|
| Current | FullStackImage_06-APR-2022 | ami-0e1b4c99fe36b17e3 |
| Source | FullStackImage_17-Dec-2021 | ami-0996f77b55866f17e |
ID: ami-0996f77b55866f17e
danger
Name: FullStackImage_17-Dec-2021
Release Date: 17th December 2021
Type: Base update
Reason for update/Issues in previous version
- Requirement to clean the AMI.
Changes
- Cleared codedeploy deployment root directory
/opt/codedeploy-agent/deployment-root/with unwanted stuff. - Removed all existing history from server.
- Cleaned up all dbs with service based and container based.
- Updated security patches.
- Cleared codedeploy deployment root directory
| Name | ID | |
|---|---|---|
| Current | FullStackImage_17-Dec-2021 | ami-0996f77b55866f17e |
| Source | baseImageFullStackDeployment-nodev14_27-Aug-2021 | ami-08e49fda5afc02b20 |
ID: ami-08e49fda5afc02b20
danger
Name: baseImageFullStackDeployment-nodev14_27-Aug-2021
Release Date: 23th August 2021
Type: Base update
Reason for update/Issues in previous version
- Requirement for baseDB for bot development with no irrelevant data.
Changes
- Added a additional data directory to be used by both docker and mongoDB service with base DB created from
evoletbrand.- Docker can be started from
/home/ec2-user/new-mongo-datato use this baseDB, else can be started form the original/home/ec2-user/mongo-data - Similarly, mongoDB(4.4) service can use either
/var/lib/mongo-base-new/or the default/var/lib/mongo
- Docker can be started from
- Cleared directory
/etc/cfn/hooks.d/to avoid possible CF restarts.
- Added a additional data directory to be used by both docker and mongoDB service with base DB created from
| Name | ID | |
|---|---|---|
| Current | baseImageFullStackDeployment-nodev14_27-Aug-2021 | ami-08e49fda5afc02b20 |
| Source | baseImageFullStackDeployment-nodev14_23-Aug-2021 | ami-0d46abeace8e25ff3 |
ID: ami-0d46abeace8e25ff3
danger
Name: baseImageFullStackDeployment-nodev14_23-Aug-2021
Release Date: 23th August 2021
Type: Security fixes
Reason for update/Issues in previous version
- weak SSH ciphers and SSL ciphers are present in previous version. Now we have added strong ciphers.
Changes
- Added Strong SSH ciphers and SSL ciphers.
| Name | ID | |
|---|---|---|
| Current | baseImageFullStackDeployment-nodev14_23-Aug-2021 | ami-0d46abeace8e25ff3 |
| Source | baseImageFullStackDeployment-nodev14_17-Aug-2021 | ami-0a7380f300c7260ac |
ID: ami-0a7380f300c7260ac
danger
Name: baseImageFullStackDeployment-nodev14_17-Aug-2021
Release Date: 17th August 2021
Type: Fixes breaking issues
Reason for update/Issues in previous version
- npm version for root and ec2-user was different due to difference in location of installed binaries. This was incompatible with node v14 upgrade in previous release.
Changes
- A symlink was created to link updated binaries of with old ones to resolve this.
| Name | ID | |
|---|---|---|
| Current | baseImageFullStackDeployment-nodev14_17-Aug-2021 | ami-0a7380f300c7260ac |
| Source | baseImageFullStackDeployment-nodev14_14-Aug-2021 | ami-018fade404244a93b |
ID: ami-018fade404244a93b
danger
Name: baseImageFullStackDeployment-nodev14_14-Aug-2021
Release Date: 14th August 2021
Type: Fixes breaking issues
Reason for update/Issues in previous version
- Default
dashboard.confhad an incompatible setting. This caused nginx to crash on reload. Due to this all frontend deployments were failing during scale-up.- The setting was related to
modsecmodule which was added in previous release. After testing module was disabled fromnginx.confbut notdashboard.conf.
- The setting was related to
- Default
Changes
- Commented the
modsecsetting that was left indashboard.conf.
- Commented the
| Name | ID | |
|---|---|---|
| Current | baseImageFullStackDeployment-nodev14_14-Aug-2021 | ami-018fade404244a93b |
| Source | baseImageFullStackDeployment-nodev14_06-Aug-2021 | ami-0d28dca7de07cd2d3 |
ID: ami-0d28dca7de07cd2d3
danger
Name: baseImageFullStackDeployment-nodev14_06-Aug-2021
Release Date: 14th August 2021
Type: Major upgrade, Adding new feature
Reason for update/Issues in previous version
- Needed to add modsec module for nginx
- baseDB had to be updated
- Vodafone related stuff was to be deleted
- Corrupt data in intents collections to be deleted.
- root creds for DB had to be changed
Changes
- Checked and applied security patches.
- Updated node from v10.x to v14.7.x
- nginx updates
- Built nginx v1.20.x from source along with the below modules.
- Installed modsec module along with OWASP rule set.
- Default modsec config is added to
/etc/nginx/modsec - Keeping it disabled by default.
- Finalize the rules to be used from
/etc/nginx/modsec/main.confand update settings innginx.confas required to enable.
- Default modsec config is added to
- Installed headers-more module
- Installed modsec module along with OWASP rule set.
- Also, updated the install location structure. Now, it's more organized under
/opt/nginx - Added nginx logrotate.
- Built nginx v1.20.x from source along with the below modules.
- mongo updates
- Installed mongoDB v4.4 as service with same data/users as baseDB.
- Structured mongo installation in '/opt/mongo'
- Removed vodafone related data from the base DB.
- Removed additional workflows, intents etc.
| Name | ID | |
|---|---|---|
| Current | baseImageFullStackDeployment-nodev14_06-Aug-2021 | ami-0d28dca7de07cd2d3 |
| Source | baseImageFullStackDeployment-nodev10-13-July-2021 | ami-03d74daedad8c031d |