适用于100,000个主题的AWS SNS解决方法 [英] AWS SNS workaround for 100,000 topics limit

问题描述

我正在开发使用带有APNS和GCM的AWS SNS进行推送通知的架构.我遵循的模型是

I am developing an architecture for push notifications using AWS SNS with APNS and GCM. The model that I am following is

• 每个用户(不是设备)都将有一个与其对应的SNS主题
• 每个用户可以拥有多个设备
• 为每个设备创建平台应用程序终结点
• 为平台应用程序端点订阅属于设备用户的主题

这样，当我们必须向用户的所有设备发送通知时，我们需要使用用户的topicArn调用publish方法，并且其所有设备都应该收到消息.

This way, when we have to send a notification to all the devices of a user, we need to call the publish method using the user's topicArn and all its devices should get the message.

但是，默认情况下，AWS限制为100,000个主题.如果我们希望有更多的用户(例如100万或说1000万)感到乐观，那么这种方法有什么解决方法吗?

However, by default AWS has a limit of 100,000 topics. If we are anticipating higher number of users like 1 million or say 10 million to be optimistic, is there any workaround for this approach?

我是否应该要求AWS提前提高限额?他们会轻易将限额提高到1亿个数字吗?是否有成本隐含，其中大多数在开始的几个月内没有使用?

Should I ask AWS to raise the limit beforehand? Do they raise limit to a number like 100 million easily? Is there any cost implication of most of them are not used in the beginning few months?

推荐答案

披露:我以前在Amazon SNS上工作

您提出的架构是Amazon SNS中的一种常见模式，并且是健全的.

The architecture you propose is a common pattern within Amazon SNS and is sound.

您应该要求主题限制增加.即使您创建主题并且不使用主题，也没有较高主题限制的成本暗示.但是，对于每个支付$ 0.50/百万个请求. docs.aws.amazon.com/sns/latest/api/API_CreateTopic.html"rel =" noreferrer> CreateTopic 调用，每月前100万个请求免费.

You should ask for a topic limit increase. There is no cost implication for having a higher topic limit, even if you create the topics and don't use them. However, you will pay $0.50/million requests for each CreateTopic call, with the first 1 million requests being free per month.

提交支持票时，请记录您的用例.它可以帮助团队加快您的限额增加请求.

When you submit the support ticket, please document your use case. It helps the team expedite your limit increase request.

这篇关于适用于100,000个主题的AWS SNS解决方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！