charithreddyv
commented
4 months ago from amplify/backend/analytics/elovumomsapp/pinpoint-cloudformation-template.json
"RegionMapping": {
"us-east-1": {
"pinpointRegion": "us-east-1"
},
"us-east-2": {
"pinpointRegion": "us-east-2"
},
"sa-east-1": {
"pinpointRegion": "us-east-1"
},
"ca-central-1": {
"pinpointRegion": "ca-central-1"
},
"us-west-1": {
"pinpointRegion": "us-west-2"
},
"us-west-2": {
"pinpointRegion": "us-west-2"
},...i understand Pinpoint configured on us-west-1 are mapped to us-west-2 and i can see both staging and prod project there but prod one is not yet enabled
ykethan
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.10.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I have created a new environment names 'staging' add Auth, Function, Analytics and Notifications (pinpoint APNS for now ) that was successful . i did
amplify env addand named the new one prod everything was success except for notification When i runamplify statusall resources shows 'No Change' but Notifications shows 'Create' , When i runamplify add notificationoramplify update notificationand selected the channel as APNS or FCM it yields the following errorI just recognised Pinpoint is not available on us-west-1 but my staging env was also configured on us-west-1
Expected behavior
Should be able to update certs for APNS and FCM and amplify push to use resources.
Reproduction steps
Project Identifier
Project Identifier: 30c6d7ea108cb6bcc4017c50672ccfd5
Log output
Additional information
No response
Before submitting, please confirm: