![]() You will need to investigate possible alternatives if you depend on this feature. Scheduled server stops / starts will be disabled.Scheduled server backups will be disabled.If you are using a *. domain to access your applications, you must configure a custom domain to prevent future access problems. Learn how to fetch secrets from Bitnami Cloud Hosting. Therefore, you must ensure that you fetch and store them securely before the deprecation date. Passwords and SSH keys will be removed from Bitnami systems.Static IPs in Bitnami Cloud Hosting are Elastic IPs in AWS.Bitnami Cloud Hosting assigns two security groups per server: one shared across all servers ( bch-shared-firewall-id) and another specific for each server ( bch-server-firewall-id). Firewalls in Bitnami Cloud Hosting are Security Groups in AWS.Their description matches their name in Bitnami Cloud Hosting. They are stored in the same region as the server. Backups in Bitnami Cloud Hosting are EBS Snapshots in AWS.The instance Name label matches the server name in Bitnami Cloud Hosting. They are listed on the AWS Console in the specific region where they are running. Servers in Bitnami Cloud Hosting are EC2 Instances in AWS.Also, in the following section, you will find a list of Bitnami Cloud Hosting concepts and the equivalent terms on the AWS Console. This document provides information about different operations you may need to perform when moving to the AWS Console. After this deprecation date, you will have to use the Amazon Web Services (AWS) Console or the AWS API to manage those servers created using Bitnami Cloud Hosting. The Bitnami Cloud Hosting service will be deprecated by February 15th, 2022. Manage Bitnami Cloud Hosting Servers from the AWS Console
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |