Skip to main content
print this page

Amorphic installation/upgrade imapacted in Custom Managed VPC Solution

· 2 min read
Fix Available
Fix Available
This bug has been fixed
Patch Available
Patch Available
This bug has a patch available for affected versions

Amorphic installation/upgrade to 2.3 fails in Custom Managed VPC Solution. Infrastructure failed to deploy due to error Unable to find SSM parameter.

Affected Versions: 2.3

Fix Version: 2.3*

2.3*

Customers installing or upgrading 2.3 after Oct 7, 2023 does not require explicit patching as the fix is part of the release artifacts.

Root cause(s)​

AWS Resource Cloudwatch Alarm for squid proxy with name rSquidProxyCPUCloudwatchAlarm failed to provision in Custom Managed VPC solution as it refers to SSM parameter AMORPHIC.PROXY.AUTOSCALINGGROUPNAME is unavailable in the case of Custom VPC as the Squid proxy does not get installed.

Impact​

No impact on existing customers. Customers going for Amorphic 2.3 fresh installation in custom Managed VPC. Customers having Amorphic running in Custom Managed VPC and upgrade to 2.3

Mitigation​

Timeline​

gantt
    title Timeline
    dateFormat YYYY-MM-DD
    tickInterval 1day
    axisFormat %b-%d
    todayMarker off
    section Tracker
        %% update the ticket number and date of bug report
        CLOUD-3985 : done, 2023-10-7, 0d
    section Identification
        Reported : crit, des1, 2023-10-7, 1d
    section Mitigation
        %% Update number of days took for each step below
        Bug fixed: milestone, 2023-10-7, 1d
    section Delivery
        %% update the date of each step below
        testing complete: milestone, 2023-10-7, 1d
  • 2023-10-07: Bug reported/identified (CLOUD-3985)
  • 2023-10-07: Bug triaged and fixed in development
  • 2023-10-07: Patch being pushed to release artifacts for version 2.3