Amazon Lightsail: Additional static IP address creation and can they be adjusted against AWS credits

Query raised to AWS Support:

Intend to create static IP. Five free already used. Need to know how to create additional static IP and their charges. Are these charges forfeited with my AWS credits?

Reply from AWS Support:

Thank you for reaching AWS Premium Support. I am Vishnu from Linux team and will be assisting you further with this case.

From the description, I understand that you would like to know how to create additional static IP addresses and their charges. Please feel free to correct me if I misunderstood your requirement in any way.

Kindly note that, there is no additional cost for increasing Static IP address limit. By default, all AWS accounts are limited to five Static IP addresses per Region, because public (IPv4) internet addresses are a scarce public resource. You can create a request directly from AWS console to increase the limit of Lightsail Static IP addresses in a region. Please use below link for the same.

https://console.aws.amazon.com/support/home?#/case/create?issueType=service-limit-increase&limitType=service-code-lightsail

Here you need to specify the “Region” and the new static IP address limit value with a clear Use case description. Once the request is submitted, our internal teams will review it and reach you with a confirmation on the same. If you require our assistance for creating the request, we can also create the request on behalf of you. In that case, kindly share the region, new static IP address limit value and a clear Use case description so that we can reach our internal teams with the request on your behalf.

Plesk Obsidian on Ubuntu (Web Admin Edition SE – FREE): Lightsail performance appears better than EC2

AWS, AWS LightSail, Blog, Brands, EC2, Plesk, Web Development & Internet Marketing

Initially, launched a couple of instances on AWS Lightsail of Plesk Obsidian on Ubuntu (Web Admin Edition SE – FREE). The results were satisfactory. If there is an issue with the scarcity of memory resources manifesting in the slow loading of websites, you can upgrade. This is unlike on EC2 wherein you suddenly lose access to Plesk admin dashboard as well as WordPress admin dashboard.

When the 3 sites were of small sizes with less than 10 blog posts, I lose access apparently because of lack of free space.

The same outcome followed despite the content of the websites remaining the same while upgrading instance types from t3.small to t3a.medium and finally m5a.large in the course of few days.

To be fair, it is clearly mentioned in the catalog:

Note: Plesk runs smoothly on a t3.micro instance for not more than 3 websites or domains with a small load. Note: In case you need the full Plesk functionality and/or larger instance types and/or more available AWS regions, please refer to the commercial Plesk AMIs on the AWS Marketplace (Web Host Editions).

If you have AWS credits and do not intend to pay a subscription fee to Plesk, going with this same Plesk Obsidian on Ubuntu (Web Admin Edition SE – FREE) on Lightsail instead of EC2 works better by my experience.

WP Engine now available in AWS Marketplace

AWS, Blog, Brand (WordPress), Brands, Cloud Computing/Startup Resource, Partner News, Web Development & Internet Marketing, WordPress, WP Engine

Source: WPEngine newsletter dated 31 March 2021

Access WP Engine’s enterprise-level digital experiences through AWS Marketplace, a digital catalog with thousands of software and services listings that run on Amazon Web Services.

WP Engine Premier: The WordPress Digital Experience Platform

WP Engine is the world’s leading WordPress Technology Company trusted by more than 150K customers including brands like AMD, Marriott, Thomson Reuters and Volvo. More of the top 200 thousand Alexa-ranked sites are powered by WP Engine than any other provider. WP Engine’s multi-product portfolio enables agencies and brands to run their WordPress sites and applications.

WP Engine’s Premier product line allows customers to build, power and optimize highly performant, redundant and secure digital experiences on WordPress. Premier customers benefit from advanced, SOC-2 compliant security, performance analytics and WP Engine’s dedicated account management.

WP Engine is a Digital Customer Experience (DCX) competency partner with AWS.

View the product listing on AWS Marketplace here.

This is an addition to WPEngine’s Startup, Growth, Scale, and Custom WordPress managed WordPress hosting available through wpengine.com.

AWS EC2: Restoring snapshot of an instance after upgrading instance size

AWS

Issue faced with Plesk Obsidian

Hosted an EC2 instance on AWS EC2. Plan t3.micro. Unable to access Plesk dashboard since yesterday. Getting the message:

Reply received:

What happens with Plesk Obsidian is apparently if there is a memory/resource deficiency, you might be unable to access Plesk admin dashboard. Also, all live websites might no more live. In such cases, it is pertinent to have a snapshot in place so that after changing the instance sizing from Instance Type, a snapshot can be restored.

Ideally, even without a snapshot, one should be able to accomplish by first stopping the instance, then upgrading (like I tried to do from t3.micro to t3a.medium), and finally starting the instance. In my case, even after raising from t3.micro to t3a.medium, I could not access Plesk admin dashboard and associated websites were still not live. Since, I had a snapshot (taken few days back), I decided to replace EC2 instance with the snapshot, which was successful.

Query raised to AWS Support:

intend to restart the above instance after migrating one of its snapshot. Earlier, I was unable to access Plesk admin dashboard as there was a shortage of memory space. So, decided to relaunch with a snapshot. Could not figure out which one of the two is the snapshot of i-0cf7dc9918291c1b1. 1. snap-094c6b4b5c37228e8 2. snap-0ddc9e7371852d2fd So, help regarding figuring out the snapshot needed. After that, could not succeed in knowing how to proceed. Do I need to create Volume for the snapshot. A guidance such that I am able to restore the snapsot of instance will be highly appreciated. I have been able to change the instance size but struck since then. Instance ID(s): i-0cf7dc9918291c1b1.

Reply from AWS Support:

Hello, Greetings for the day!

Thank you for contacting AWS Premium Support. I’m Pranitha from the EC2 Linux team and I will be assisting you with the case today.

I understand that you are unable to figure out the correct snapshot for the instance i-0cf7dc9918291c1b1 and require guidance on restoring the instance from the snapshot. Please correct me if I have misunderstood your concern.

Firstly, I looked up your account and as you mentioned I could see the below two snapshots in us-east-1 region:

snap-094c6b4b5c37228e8
snap-0ddc9e7371852d2fd

Furthermore, both the above snapshots were created from the same volume vol-069e47f515eeaea13. However, currently I see that the volume vol-069e47f515eeaea13 is unattached and is in available state. Upon checking the cloudtrail history, I was able to confirm that this volume was previously attached to the concerned instance i-0cf7dc9918291c1b1.

Hence, I can confirm that both the above snapshots belong to the instance i-0cf7dc9918291c1b1. Both the above snapshots were created around the same time with the most recent one being “snap-0ddc9e7371852d2fd” created on Mon Mar 15 2021 11:21:21 GMT+0530 (IST).

Therefore, you may launch a new EC2 instance from snapshot “snap-0ddc9e7371852d2fd” of the volume. For this you would need to first create an AMI from the snapshot and launch an instance from this AMI. Please refer to the below AWS documentation for steps to achieve the same: [+]https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html#creating-launching-ami-from-snapshot

Alternatively, as the volume “vol-069e47f515eeaea13” is in available state, you may also opt to create a new EC2 instance and attach the volume to it as a secondary volume. [+]https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-attaching-volume.html

Either of these approaches would help you restore the data of the original instance on the newly launched instance.

I hope the above information helps. Incase you feel I have missed out on addressing your concern right, or if I can otherwise provide any additional assistance with regard to this matter, please do not hesitate to let me know, I’ll be happy to work ahead with you until everything is successfully addressed. Hope you have an amazing day ahead!

EC2 Instances: Stop Instance may not be equivalent to pausing in case Auto Scaling feature opted for, can delete all associated websites/apps

AWS, Blog, Brand (WordPress), Brands, Cloud Computing/Startup Resource, EC2, Web Development & Internet Marketing

With Stop and Terminate option under one menu, one might form an opinion that Stop will work like a pause, something meant to unpublish associated websites/apps with the instance, and later publish after pressing Start button. This can actually work like so if Auto Scaling option not opted for. In case Auto Scaling option opted, stopping might immediately delete apps/websites associated with the instance if marked unhealthy. To prevent Amazon EC2 Auto Scaling from terminating unhealthy instances, suspend the ReplaceUnhealthy process. ‘While the instance is not present in an Autoscaling group, after performing a stop operation on the instance there won’t be any data loss (unless instance store volume is attached). Therefore on starting the instance back all the data would be already present in the instance’s EBS volumes.’

AWS Support Case:

Subject

Stopping of an EC2 instance led to termination

I intended to upgrade one of my EC2 instances. Came to know that an EC2 instance can be increased only by stopping it. So I stopped the instance i-0b4edxxx on expectation that after upgrading, I would restart the instance. However, things did not go that way. After stopping the instance, it appears that the instance terminated. I could see a fresh instance i-0d4axxx being activated. On trying to access the files from the activated one, which is under Plesk hosting, I found that WordPress websites were all gone. Help appreciated. Instance ID(s): i-0b4exxx

Reply:

Hello Greetings for the day! Thank you for contacting AWS Premium Support. I’m Manav from the EC2 linux team and I will be assisting you with the case today.

From the case description, I understand that in order to upgrade one of your instances, you stopped the instance i-0b4edd040cd31256c, but it got terminated and a new instance was launched i-0d4a0e7ebb8fc67d1. Now the new instance does not have WordPress website data on it. Therefore, you need my assistance in understanding why the instance got deleted. Please correct me if I have misunderstood your concern.

Starting with my investigation, I checked the CloudTrail logs to identify the instance and reason behind its termination. Upon reviewing the logs, I could notice that the instance i-0b4edd040cd31256c was terminated on 2021-03-10 at around 07:53 UTC, as part of the scaling action performed by your autoscaling group “AutoScalingEC2”.

I reviewed the activity history of “AutoScalingEC2” using my internal tools and could confirm that the instance was terminated as it was marked unhealthy when you stopped it.


At 2021-03-10T07:53:34Z an instance was taken out of service in response to an EC2 health check indicating it has been terminated or stopped.

The same phenomenon is mentioned in this AWS documentation : https://docs.amazonaws.cn/en_us/AWSEC2/latest/UserGuide/Stop_Start.html#instance_stop

“If your instance is in an Auto Scaling group, the Amazon EC2 Auto Scaling service marks the stopped instance as unhealthy, and may terminate it and launch a replacement instance.”

Having said this, the new instance i-0d4a0e7ebb8fc67d1 was launched on 2021-03-10 at 07:53 UTC as its replacement to meet the specified desired capacity of 1.

As you might already be aware, Amazon EC2 Auto Scaling checks that all instances within the Auto Scaling group are running and in good shape by periodically checking the health state of the instances. When it determines that an instance is unhealthy, it terminates that instance and launches a new one. This helps in maintaining the number of running instances at the minimum number (or desired number, if specified) that you defined. For more information on Health checks for Auto Scaling instances, you may refer[1].

Having said the above, I would also like to inform you that the newly launched instance will not hold any data of the previous instance. Only the settings specified in the Autoscaling Launch Configuration will be applied to all instances that are launched as part of the Autoscaling group. The custom modifications or the data stored on individual instances will be independent of the other instances and will not be copied when its replacement is launched.

Unless you have created a snapshot/AMI of the previous instance, It would not be possible to recover the data of the terminated instance. I understand that this might have caused severe inconvenience to you. Kindly note that due to strict Data Privacy and Shared Responsibility Model [+], we at AWS do not store any backup for the customer resources.

I further checked your account for any available backups (snapshots or AMI) but I was unable to find any. Unfortunately, kindly understand that, in such cases, it is not possible to recover the data.

However, I can guide you on how to prevent this from happening in future. To prevent Amazon EC2 Auto Scaling from terminating unhealthy instances, suspend the ReplaceUnhealthy process. For more information, see >>> https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html

Additionally, you may find the AWS documentation[2] helpful to prevent termination of Amazon EC2 instances under different scenarios.

Lastly, I strongly recommend you to take regular backups of your instances by creating a snapshot/AMI [3][4] so that you will be in a position to recover the data under situations like these.

I hope this helps. Please reach out to me if you have any additional questions or need further assistance and I will be happy to help you. Stay safe and have a great day ahead!

References:- =========

[1]Health checks for Auto Scaling instances – https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html#replace-unhealthy-instance

[2]Instance termination – https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/terminating-instances.html#Using_ChangingDisableAPITermination

[3]Creating a snapshot – https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html

[4]Creating a Linux AMI from an instance – https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html [+] Data Privacy FAQ https://aws.amazon.com/compliance/data-privacy-faq/

Shared Responsibility Model https://aws.amazon.com/compliance/shared-responsibility-model/

Best regards, Manav G.

Amazon Web Services

Here is the explanation by one more AWS customer support specialists:

Hello Rajeev

Thank you for your time over call today

I reached out to you over call as I saw that you had some doubts regarding Autoscaling Group and Instances in terminate and stop state.

While on call we discussed that about the nature of instance when in the Autoscaling group as well as when not in Autoscaling group.

=> While the instance is not present in an Autoscaling group, after performing a stop operation on the instance there won’t be any data loss (unless instance store volume is attached). Therefore on starting the instance back all the data would be already present in the instance’s EBS volumes.

=> While the instance is associated with an Autoscaling group, stopping an instance makes the Autoscaling group mark it as ‘unhealthy’, and in order to maintain desired number of instances, the Autoscaling group terminates the ‘unhealthy’ instance and launches a new ‘healthy’ instance as per the launch configuration.
This newly launched instance will not hold any data of the previous instance. Only the settings specified in the AutoScaling Launch Configuration will be applied to all instances that are launched as part of the Autoscaling group.

Thanks again for your time.
I hope this helps. In case you still have any queries, please feel free to revert back and we will be happy to help.

Have a nice day ahead!

References:-

[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html

How to terminate an instance in Autoscaling Group

Query

Since I need to terminate the instance, I am trying with the option Terminate. However, each time, a new replacement comes up. It might be since it appears that Auto Scaling option still enabled. I tried to opt out of Auto Scaling but could not. Kindly, help me with termination of the instance i-0fba5e5db22fd8bb6 (Key Name: FinVestOpKey).

Reply

I understand that you need to terminate the instance i-0fba5e5db22fd8bb6, but not able to. Hence you need assistance regarding the same.

Before we start, I would like to inform that I checked the instance with the help of my internal tools and can confirm that your assumption of instance not being terminated due to Autoscaling Group is correct. Every time an instance in an Autoscaling group is terminated, a new instance is launched to replace it.

Now, in order to disassociate instance from the Autoscaling Group and terminate it, you can simply delete the Autoscaling Group and with it, all the instances associated will also get terminated. In your case only the instance “i-0fba5e5db22fd8bb6” is associated, hence it will get terminated.

You can follow the steps mentioned below for the same :-

*) Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/

*) On the navigation pane, under AUTO SCALING, choose Auto Scaling Groups.

*) On the Auto Scaling Groups page, select the check box next to your Auto Scaling group ‘AutoScalingEC2’ and choose Delete.

*) When prompted for confirmation, choose Delete.

A loading icon in the Name column indicates that the Auto Scaling group is being deleted. The Desired, Min, and Max columns show 0 instances for the Auto Scaling group. It takes a few minutes to terminate the instance and delete the group. Refresh the list to see the current state.

Detailed information on the same –

https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-process-shutdown.html#as-shutdown-lbs-delete-asg-cli

However in case you wish to keep your Autoscaling group but still want to terminate the instance, you can modify the Autoscaling’s desired capacity to be 0. Doing this would automatically terminate your associated instance ( i-0fba5e5db22fd8bb6 ). You can refer to the steps below :-

*) Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/

*) On the navigation pane, under AUTO SCALING, choose Auto Scaling Groups.

*) Select the Autoscaling group ‘AutoScalingEC2’.

*) Select Edit option.

*) Modify the ‘Desired Capacity’ to be 0 > Update.

For more information on setting capacity limits for your Auto Scaling group – https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-capacity-limits.html

Best regards,

Manav G.

Amazon Web Services