[英]How to downsize an AWS RDS instance to free tier
I want to create a free tier clone of a production AWS RDS
PostgreSQL
.我想创建生产
AWS RDS
PostgreSQL
的免费层级克隆。 As per my understanding, following are different ways根据我的理解,以下是不同的方式
t2.micro
t2.micro
t2.micro
and then detach it as independent databaset2.micro
创建生产数据库的只读副本,然后将其分离为独立数据库Option 3 is my last preference.选项 3 是我最后的偏好。
The problem is while creating read replica or restoring from snapshot, AWS doesn't explicitly allow to choose the free tier template.问题是在创建只读副本或从快照还原时,AWS 没有明确允许选择免费套餐模板。 I just want to know if restoring to
t2.micro
without any advanced features like autoscaling, performance monitoring etc. is equivalent to free tier or not?我只是想知道在没有任何高级功能(如自动缩放、性能监控等)的情况下恢复到
t2.micro
是否等同于免费层? I read here that the key thing with AWS production DB is that AWS provisions a secondary database provisioned to fallback in event of failure of the primary database or the Availability Zone in which the database is running.我在这里读到,AWS 生产数据库的关键是 AWS 预置了一个辅助数据库,以便在主数据库或数据库运行所在的可用区发生故障时回退。
AWS Free Tier doesn't actually care about the kind of service you use. AWS 免费套餐实际上并不关心您使用的服务类型。 Per their website you just get 750 instance hours per month for a
db.t2.micro
. 根据他们的网站,您每月只需为
db.t2.micro
获得 750 个实例小时。
You can use these in any service you see fit and the discount will be applied automatically for the first 12 months .您可以在任何您认为合适的服务中使用它们,并且折扣将在前 12 个月内自动应用。
Looking at the pricing page for RDS Postgres I can see, that these instances aren't listed anymore, which seems weird.查看 RDS Postgres 的定价页面,我可以看到这些实例不再列出,这看起来很奇怪。 The
t2
instance family is fairly old, so they're probably trying to phase it out, but typically you can provision older instance types using the API directly if they're not available in the Console. t2
实例系列相当陈旧,因此他们可能正在尝试逐步淘汰它,但通常您可以使用 API 直接配置较旧的实例类型,如果它们在控制台中不可用。
So what you want to do is create your db.t2.micro
instance using one of the SDKs or the AWS CLI and restore from a snapshot .因此,您要做的是使用开发工具包或 AWS CLI 之一创建您的
db.t2.micro
实例,然后从快照中恢复。 Alternatively you can create a read replica from the CLI and set the class to db.t2.micro
.或者,您可以从 CLI 创建只读副本并将 class 设置为
db.t2.micro
。 Later detaching that from the main cluster should work.稍后将其从主集群中分离应该可以工作。
The production ready stuff refers to the Multi-AZ deployment, which is good for production use, but for anything production related a t2.micro
seems like a bad choice, so I'm going to assume you're not planing to do that.生产就绪的东西是指多可用区部署,这对生产使用很有好处,但对于任何与生产相关的
t2.micro
似乎都是一个糟糕的选择,所以我假设你不打算这样做。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.