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

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

How to launch your WordPress website on EC2 with Plesk

AWS, EC2, Plesk

It is assumed that you have already activated your AWS account.

Need to move on to AWS Marketplaces (since Plesk is a third party providing the software).

For this demo, will opt for Plesk Obsidian on Ubuntu (Web Admin Edition SE – FREE).

This Web Admit Edition provided free by Plesk. You can launch three instances of WordPress (or any other supported instance such as Joomla, Drupal) with this. Only usage costs will be charged by AWS. No licensing cost by Plesk.

For those looking for a free way (no charge by AWS as well for the first 12 months) to launch a WordPress website on AWS, unfortunately, this Plesk plan will not support.

As mentioned, Plesk runs smoothly on a t3.micro instance for not more than 3 websites or domains with a small load. We opt t3.micro for this demo.

Opt for t3.micro for this demo. You can either click Review and Launch or Next: Configure Instance Details (in case willing to go with default settings).

After configuring, click Review and Launch.

Download and keep this .pem file in safe custody for future needs. Next, click Launch Instances.

For this demo, I click Launch. You might want to configure as per your needs after going through Instance Details, Storage, Tags.

Need to access Plesk admin dashboard. For that press Connect.

Type sudo plesk login. For the first time, you get two URLs. Second one is to set Plesk admin credentials. Copy the second URL and paste on the address bar of your browser.

Going forward, you can access Plesk login page by either typing https://”ip address”:8443 or through URL shown after typing sudo plesk login on the console bar after pressing Connect.

Allocating static IP address

Make sure to reboot the instance after associating static IP.

Now, you can access Plesk admin dashboard, which is covered in an earlier article post written for Lightsail instance here: Plesk Hosting Stack on Ubuntu: 3 websites under one instance with plans starting 5$ per month on Amazon Lightsail and a demo of migration with free Migrate Guru plugin. The Plesk admin dashboard remains the same irrespective of being launched either on Lightsail or EC2 as for this demo.

Plesk Hosting Stack on Ubuntu: 3 websites under one instance with plans starting 5$ per month on Amazon Lightsail and a demo of migration with free Migrate Guru plugin

AWS, AWS LightSail, Blog, Brands, Cloud Computing/Startup Resource, Plesk, Web Development & Internet Marketing, WordPress

Launch three websites after creating a Plesk Ubuntu instance on AWS Lightsail with plans starting at 5$ per month. This post will also include a demo of migration of an existing WordPress here using Migrate Guru plugin.

Login to Lightsail dashboard — https://aws.amazon.com/lightsail/

Plans starting with 5$ per month. Three domains can be used for launching websites per instance.

In case you intend to connect with FTP for files access, make sure to open ports 20-22, 49152-65535 under Networking. They are blocked by default. I have opened them as intend to migrate another WordPress instance/website to this using Migrate Guru plugin that needs FTP details as part of migration process.

Make sure to reboot after making changes under networking.

It is important to add a static ip right at this stage.

Type sudo plesk login to access login url to set first time username and password for Plesk dashboard from where the proposed three websites will be managed.

Update A records of the domain name under DNS. For this demo, NameCheap.

From WordPress menu, install a fresh WordPress instance.

Migrating to the above WordPress instance using free Migrate Guru plugin

Install Migrate Guru plugin on WordPress website which to be migrated.

Will be using FTP option.

In the Directory Path field, first check in which directory wpconfig.php file located. If within httpdocs, then under Directory Path enter httpdocs (Directory path for WordPress site migration to Plesk using Migrator Guru plugin).

For destination URL, entering https://digitalsplendid.work as SSL activated earlier from the Plesk dashboard.

One of the hurdles I faced while migrating from a Bitnami application (under AWS Lightsail) is inability to add new plugins with this error message:

Installation failed: Download failed. Destination directory for file streaming does not exist or is not writable.

Here is the solution:

So, I address this issue for digitalsplendid.xyz.

Made a search with “Bitnami” on wp-config.php file and removed the line that has a code starting with define. After that, I could upload new plugins (as well update existing plugins).

You can upgrade Lightsail instances seamlessly, downgrade possible but not a one click process

We started with 5$ per month plan (cheapest plan for Plesk Ubuntu). Not surprisingly, once three WordPress websites live and contents posted, there will be resource issues. Refer this on how to upgrade: https://aws.amazon.com/premiumsupport/knowledge-center/change-lightsail-plan/

Cloud computing technologies for startups: Tips based on our experience as a startup from India

AWS, Blog, Brands, Cloud Computing/Startup Resource, Google Cloud, IBM Cloud, Microsoft, News, Offers, Oracle Cloud, Partner News, Web Development & Internet Marketing, WordPress, WordPress.org, WP Engine

Given the promising outlook of cloud computing, start building expertise around cloud computing technologies by choosing one or more of the leading brands: Amazon Web Service (AWS), Google Cloud, Microsoft Azure, Digital Ocean, Alibaba Cloud. All of them have special packages for startups with liberal credits to learn, try new ideas. Even if you do not join or not approved for their startup or partner programs, you can register as a customer and chances are you still get free perks/credits.

AWS
WP Engine
Microsoft
IBM Cloud
Oracle Cloud
Google Cloud
Hitachi Vantara
OVH Cloud

1. Amazon Web Services (AWS)

If AWS, follow the course roadmap prescribed as part of AWS certifications while joining as AWS Partner. As a Registered AWS Partner (free tier), you will learn about cloud technologies while nurturing your skills as a consultant/developer. We are a Registered Consulting Partner. As AWS Partner, you can align to Software (ISV), Hardware, Services (Consulting), Training, or Distribution path.

For India, a great way to avail of free credit from AWS (5000$) and DigitalOcean (1000$) is to signup for the StartupIndia program and get DPIIT (also called DIPP) recognition.

Point taken that DIPP recognition has its own criterion of being incorporated as a private limited company or registered as a partnership firm or a limited liability partnership. This might not be suitable for newbies or those who prefer to be freelancers in true spirit. Now, any startup (not just registered with StartupIndia or DIPP recognized) can apply for the AWS Activate Founders program and subject to meeting their conditions be granted 1350$ AWS credit (1,000 USD in AWS credits, valid for two years, and $350 USD in AWS Developer Support credits valid for one year). One can apply for both, (possibility to avail $100,000 in AWS Activate credits).

Still an easier way to avail your first 5k AWS credit can be through Intercom: Read here:

Maximizing AWS Activate: How to Unlock $5,000 in Credits for Your Startup

Review us on AWS

2. WP Engine

Simultaneously, consider partnering with technology companies like WPEngine for developing state-of-the-art websites powered by WordPress (WP Engine is an AWS Partner Network (APN) Advanced Technology Partner with the AWS Digital Customer Experience Competency). We are a WPEngine Agency Partner. For agencies and end-users, it perhaps makes more sense to opt for such hosting solutions that take care of most back end technology stuff. Agencies stay focused on creating content as part of generating a great client experience; clients stay focused on their core work which is not maintaining servers like AWS. WP Engine’s technology improves site speed, while providing the intelligence to make it even faster. Tools like Local + WP Engine Connect make WP Engine relevant for hard-core developers too.

Headless WordPress with Atlas is the latest innovative feature by WP Engine and all agency partners are provided extensive free support to leverage this opportunity to make WordPress sites load absurdly fast.

Contact us for your WP Engine needs here

3. Microsoft

Now, coming to Microsoft, it appears that they are not as liberal as AWS when it comes to providing credit to startups. Nevertheless, Microsoft has a unique set of features, and there are ways by which startups can associate with Microsoft for free.

The best way perhaps should be by registering under Microsoft for Startups, but this has its own criteria which might not be fulfilled by all. Till recently, Microsoft for Startups program was open to only those startups who were registered with a list of accelerators/incubators.

Now, the program in limited preview is open to all founders. They are reviewing applications on a rolling basis and will notify you if you are granted access.

So if your company is not approved for Microsoft for Startup Founders Hub, there are other resources for startups and small businesses to explore:



	Bring your startup’s ideas to life with an Azure free account. Join the Microsoft Partner Network a to expand your business, engage customers, earn more, and get discounts on Microsoft products. Discover the most popular Microsoft products for startups, including Visual Studio, Microsoft 365 Business, Power BI, and Dynamics 365, plus the GitHub development platform.

With Microsoft Partner Networks, one can start for free albeit paid subscriptions (Microsoft Action Pack) will help leverage the program to its full.

4. IBM Cloud

In addition to free forever lite plan by IBM, there is Startup with IBM program.

We applied for the Builder Plan and initially got approved.

Hi Rajeev, welcome to Startup with IBM!

Congratulations, you have been accepted into the Startup with IBM program.
Your account number is confirmed and as follow:

To complete your registration and to begin your partnership journey with IBM, follow these simple steps:

1. Access your $1,000 monthly credit on IBM Cloud

Step 1: Check your inbox for a separate email titled “Action Required! Complete your IBMid – SoftLayer identity link.” (you might need to check your spam folders) Step 2: Click the “Complete Registration” link within that email to complete your account registration.

2. Get started building with the platform

Log in with your IBMid credentials to browse the IBM Cloud Services Catalog. From core concepts to beginners tutorials, visit IBM docs and find the information you need to start using IBM Cloud.

3. Sell with IBM

Once you’ve built your solution, expand your audience! Get in front of 25 million customers, partners, and developers, and access leading buyers and sellers around the globe through IBM Marketplace. Refer to IBM Partners for more information.

Reference your resources

Build your skills and develop competencies on IBM technologies with learning paths. Access 100 code patterns across Data, AI, and Cloud to accelerate your integration of IBM technology! Login to check your account credit on your IBM Cloud Account (account > billing > invoices). For support, visit IBM Cloud support. “Talk to an Expert” is the easiest way of getting any issue resolved!
Need access to our 24/7 support? Contact our Technical and Sales Engineering teams by simply opening a ticket via the portal under “Support.” View the IBM Cloud Catalog. Learn more about IBM Cloud (Infrastructure).

Regards,
The Startup with IBM Team

Refer to our Cloud Service Agreement and the Startup with IBM Addendum for additional offer details.

The bad news is that within few days, this credit was reversed on the ground of not meeting the criteria. Although the exact reason was not given, still I understand it was because we were not aligned with their list of accelerators/incubators.

IBM continues to provide various opportunities for startups and their founders to expand within their respective IT domains, which may involve participating in programs such as the IBM Partner Plus, IBM TechXchange Community, and IBM Champions.

5. Oracle cloud

Oracle is providing a free trial and credit (expire after 730 days) to all new signups.

Oracle Cloud too has a free, forever tier. Oracle has inherent expertise in database technology that is part and parcel of any hosting experience.

Right now, they are also selectively offering free migration, something not available with AWS, Microsoft Azure or IBM.

For startups and developers, a better way to initiate a relationship with Oracle Cloud is to signup for Oracle for Startups program.

(For easy access to links, pasting the content of the email below)

Welcome to Oracle for Startups! I’ll be acting as your primary point of contact during this part of the program – I’m here to help, so please reach out to me directly if you have any questions. As a starting point, please create a profile for your company in our Startup Portal here:

https://oraclestartupbeat.com/StartupPortal/?root=register

Through the Startup Portal, you can do the following:

Request for migration support
Request additional cloud credits
Level up for access to marketing and customers
Request a meeting with an Oracle mentor
Access videos, success stories and technical documentation

Additionally, here are a few resources you might find helpful as you start to build on Oracle Cloud:

It is a privilege to have you in the Oracle for Startups family. Please consider joining us for an upcoming event or ask-me-anything session and let me know how I can help you with any questions.

Best,

Kenan Kitchen

Oracle for Startups – North America

Email: [email protected]

www.oracle.com/startup/

Although we did not use Oracle Cloud till now, our experience with Oracle for Startups somewhat resonates with this somewhat negative review. Despite tall claims of mentorship under the program, we could not spot any mentor.

6. Google cloud

Earlier Google Cloud had a startup program ‘designed for early-stage companies backed by a select group of Google Cloud for Startups investors (VC, incubator, or accelerator) and minimum viable product.’

As mentioned on the above email, “We unfortunately are not able to accept your application at this time, since our program is less applicable for small businesses, consultancies, and agencies solely providing services. We also cannot accept blogs, devshops, educational institutions, government entities, nonprofits, or cryptomining companies.” This actually is true for many other startup programs by technology companies.

The possibility remains, “If your product is in stealth mode, we recommend reapplying at cloud.google.com/startup when you have more materials for our team to review.”

Like with other cloud technology service providers, there are multiple ways to grow if not approved for the startup programs. For Google Cloud, “Additionally, here are some other credit opportunities and helpful content as you consider building on GCP:

If you’re part of an accredited educational institution, check out the Google Cloud for Education program to apply for research credit or a faculty grant.
Join the Google Cloud Developer community and GCP Community to stay in the loop on product updates and special events.
Explore Cloud Platform documentation for solutions and best practices.”

Irrespective of whether you actually apply for the Google Startup Program and get approved, I believe the resource https://startup.google.com/ is worthy for all startups, freelancers, web developers, small businesses willing to go online.

Comprehensive guide to how Google Cloud can support your startup’s innovation and growth.

Get the whitepaper.

Update: 15 June 2022

Pre-funding startups now covered by the Google for Startups Cloud Program (Source: Google Startup Newsletter dated 15 June 2022)

Bootstrapped or pre-funding startups are now covered by the Google for Startups Cloud Program

While we’ve had great response to our updated Google for Startups Cloud program, one of the big things we were hearing from customers was how they could get more support earlier in their journey, ahead of raising venture funding. Our mission is to enable all startups to build, grow, and scale on Google Cloud regardless of where they are in their journey, and at the Google Cloud Startup Summit on June 2nd we announced that the Google for Startups Cloud Program is now supporting bootstrapped startups.

We will now be offering all startups that meet some basic eligibility criteria $2,000 USD in Google Cloud Credits to be spent over 2 years. If you’re interested, go to our application page and fill out the form using the instructions at the top.

7. hitachi vantara

Founded in 2017, Hitachi Vantara is relatively new and perhaps lesser brand visibility than compared to others we have till now covered.

Partners at Center of Hitachi Vantara’s FY23 Strategy

Know more about their partner program here: Your Next Market Opportunity Meets Our Data-Driven Vision.

8. OVH Cloud

OVH Cloud is a well known cloud hosting service provider in Europe. They have a startup program which demands innovative ideas and its approval rate is limited compared to say startups credits by Google or AWS. OVH Cloud Partner program requires subscription to their Premium Support (56$ per month).