Skip to content

Commit

Permalink
Merge pull request #382 from ant-media/refactor-cf-update-document
Browse files Browse the repository at this point in the history
Refactor cf update document
  • Loading branch information
Mohit-3196 authored Nov 7, 2024
2 parents 494a658 + a74f7c2 commit 29a3812
Show file tree
Hide file tree
Showing 9 changed files with 27 additions and 21 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -9,47 +9,53 @@ sidebar_position: 4

If you have installed Ant Media Server with Cloudformation and then want to update it, simply follow the steps below.

By following these instructions, you can upgrade your Ant Media Server AWS cluster and also retain all your existing settings without affecting the MongoDB configuration.

**NOTE: Please note that your old Instances will be terminated after this update.**

**1.** Log in to the AWS Dashboard and find CloudFormation in the search box. Then, click on the "stack" that you created earlier.
**1.** Login to your AWS console and Navigate to EC2 > Launch Templates.

**2.** Select the Launch templates for the **your-stack-AntMedia-LaunchTemplateOrigin** template and click on Actions > Modify template (Create a new version)

![](@site/static/img/aws-cf-update/aws-cf-update-1.png)

**3.** Go to Application and Operating System Images (Amazon Machine Image) and search for “Ant Media Server Enterprise” in the Search field.

![](@site/static/img/aws-cf-update/aws-cf-update-2.png)

And Subscribe to Ant Media Server Enterprise from here.

**2.** Please proceed by clicking “**Stack actions >` Create change set for current stack**” button
![](@site/static/img/image-1648408340505.png)
![](@site/static/img/aws-cf-update/aws-cf-update-3.png)

**3.** In this part, select the “**Replace current template**” and “**Amazon S3 URL**” options. Pass the URL below as Amazon S3 input and click “**Next**” button.

[https://ams-cloudformation.s3.eu-central-1.amazonaws.com/antmedia-aws-autoscale-update-template.yaml](https://ams-cloudformation.s3.eu-central-1.amazonaws.com/antmedia-aws-autoscale-update-template.yaml)
**4.** In the network settings section, select **Select existing security group** then Save it.

![](@site/static/img/image-1648408390850.png)
![](@site/static/img/aws-cf-update/aws-cf-update-4.png)

**4.** The values in this section are your previous settings, you can also change the parts you want to change here. Then please proceed by clicking “**Next**” button.

![](@site/static/img/image-1648408489675.png)
**Make all these settings for the Edge template as well.**

![](@site/static/img/image-1648408511839.png)
**5.** Now go to EC2 > Auto Scaling groups and select OriginGroup. In this section, set Desired and Minimum Capacity to 0 in Groups details.

**5.** Please proceed by clicking “**Next**” button
![](@site/static/img/aws-cf-update/aws-cf-update-5.png)

![](@site/static/img/image-1648408532875.png)
**6.** Then go to Launch template.

**6.** Please proceed by clicking “**Create change set**” button.
![](@site/static/img/aws-cf-update/aws-cf-update-6.png)

![](@site/static/img/image-1648408556782.png)
Here select Version **Latest** and Update.

**7.** Click "**Create change set**" in the window that comes up.
![](@site/static/img/aws-cf-update/aws-cf-update-7.png)

![](@site/static/img/image-1648408574196.png)

**8.** Please proceed by clicking “**Execute**” button.
**7.** Go to Groups details and update the Desired and Minimum Capacity as in previous settings.

![](@site/static/img/image-1648408591135.png)
![](@site/static/img/aws-cf-update/aws-cf-update-8.png)

**9.** Please proceed by clicking “**Execute change set**” button then Let's start the update process.

![](@site/static/img/image-1648408610018.png)
That's it. Your Instances will now run with the latest version of Ant Media Server.

**10.** When the update process is completed, you will see the "**UPDATE\_COMPLETE**" event as below.
**NOTE: Please make all these settings for the Edge template as well.**

![](@site/static/img/image-1648408625725.png)

If you have any questions, please just drop a line to [[email protected]](mailto:[email protected]).
Binary file added static/img/aws-cf-update/aws-cf-update-1.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-7.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/aws-cf-update/aws-cf-update-8.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 29a3812

Please sign in to comment.