Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The new sending Regions are Hyderabad, Melbourne, Zurich and GovCloud (US-East), with the mobile push platforms listed in the announcement.
- An SNS sending Region is separate from a device or user’s country; the Region list does not determine application or platform admission.
- The topic or mobile endpoint ARN used by Publish must be in the same AWS Region as the call.
- After CreatePlatformEndpoint succeeds, read endpoint attributes and confirm the latest valid token and Enabled state.
- Re-estimate costs before launch, including requests, deliveries, data transfer and any additional services in use.
The four new Regions expand where mobile push can be sent
On November 12, 2026, Amazon SNS announced mobile push sending from Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Europe (Zurich) and AWS GovCloud (US-East). These are additional sending Regions, not a new push service or recipient type.
The announcement lists Amazon Device Messaging (ADM), Apple Push Notification Service (APNs), Baidu Cloud Push, Firebase Cloud Messaging (FCM) and Windows Push Notification Services (WNS). Before rollout, verify the current credential, application and device-registration requirements for the platform you selected.
Separate the sending Region from recipient location
An SNS Region identifies where you create resources and call Publish. A device or user’s country is a separate business and push-platform condition. Adding Hyderabad, Melbourne or Zurich as sending Regions does not make every device in those locations automatically reachable.
Confirm that the intended recipients, mobile platform and application are available for your use case, then choose an SNS deployment Region. The supported-Region list describes service capability; it does not decide application availability, permissions, platform-account access or recipient policies for you.
Keep GovCloud (US-East) within its separate account boundary
AWS GovCloud (US) consists of Regions isolated from standard AWS Regions and is designed for workloads with specific regulatory needs. Its appearance in the SNS support list does not grant a standard AWS account access to GovCloud, and an ARN or identity from a standard Region should not be assumed to work across the environment boundary.
For a GovCloud workload, follow the AWS GovCloud account and service setup process first, then confirm access and responsibility boundaries. GovCloud does not by itself guarantee that a workload meets a regulation; customers remain responsible for access to account content and workload security.
Check ARNs and the call Region before publishing
Make the intended Region part of the deployment configuration. Confirm that the SNS client calls that Region and check the Region in PlatformApplicationArn, EndpointArn and TopicArn. The platform application and mobile endpoint should come from the intended Region; do not drop an ARN from another Region into the current publishing flow.
The Amazon SNS Publish API requires the target topic or mobile platform endpoint to be in the same AWS Region as the call. For one app device, use its EndpointArn as TargetArn. For a group of subscribers, mobile endpoints can subscribe to a topic and the message can be published to its TopicArn. Both paths follow the same-Region rule.
Treat the device token and Enabled flag as endpoint lifecycle state
A mobile app obtains a device token from its push platform, and SNS uses that token to create a mobile platform endpoint. The token can change as the app installation or platform state changes, so the app should store and send its latest valid token. An initial token or an old endpoint record does not show that a device is still reachable.
A successful CreatePlatformEndpoint response does not guarantee that the endpoint is enabled: SNS can return an existing endpoint that is disabled. After creation, call GetEndpointAttributes and check Enabled and Token. If the token changed, update the endpoint with the current valid token before enabling it as needed. Re-enabling an invalid token can lead the push platform to disable it again.
Estimate current costs and run a controlled rollout check
SNS charges can include API requests, notification deliveries based on endpoint type, message size and data transfer. Additional capabilities such as encryption, filtering or archiving can add charges too. Do not infer a fixed price, free allowance or identical regional price from the Region announcement; check current published rates and the terms that apply to your account before launch.
Estimate expected Publish calls, payload sizes, subscription counts and delivery types, then review cross-service or cross-Region data transfer and enabled items such as KMS. AWS says monthly free usage is aggregated across all Regions and does not roll over. Use the current pricing page or calculator for your workload, and verify actual app display with a controlled application test.
Sources
- Amazon SNS announcement: push notifications in four additional Regions, November 12, 2026
- Amazon SNS Developer Guide: supported mobile application Regions
- Amazon SNS Developer Guide: mobile push subscriptions and setup
- AWS: Amazon SNS pricing
- Amazon SNS API Reference: Publish
- Amazon SNS Developer Guide: mobile platform endpoints
- Amazon SNS Developer Guide: mobile push API errors
- AWS GovCloud (US) User Guide: What Is AWS GovCloud (US)?
Frequently Asked Questions
Do the new Hyderabad, Melbourne and Zurich Regions automatically support every device there?
No. These are SNS mobile push sending Regions. Recipient location, push platform, app configuration, platform credentials and device registration still need separate checks; the Region list does not promise admission for every destination.
Why can CreatePlatformEndpoint return an ARN when a push still fails?
The call can return an existing endpoint that is disabled or still uses an old token. Read Enabled and Token for the EndpointArn, confirm the latest valid token, and make sure the Publish target and call use the same Region.
Does a Publish MessageId prove that a notification appeared on a phone?
No. MessageId is an identifier assigned by SNS to a published message, not a receipt from the mobile app. Also check SNS endpoint state, provider delivery results and whether the application and device processed the message.