sendMessage with pinpoint has limitation?

[juicycool92]

Hello,
recently i have a problems about deliver rate about fcm push message.
its sometimes failed to deliver without any other error. send rate is nearly 69%.

so, i tried to try pinpoint for send push message. cause my push codes are way too legacy and not sure is message even delivered or what. and pinpoint seems have dashboard plus much batter library so can make my code much cleaner.

this is example of mine code

const sendPinpointMessage = async ( msgList:Array<MessageRequest> ):Promise<any> => {
        try {
            if ( msgList.length > 0 ) {
                const region = global.Config.PINPOINT_REGION;
                const pinpoint = new Pinpoint({ region });
                const resultList:Array<SendMessagesCommandOutput> = [];
                for( const i of msgList ) {
                    const params:SendMessagesCommandInput = {
                        ApplicationId : global.Config.PINPOINT_APP_ID,
                        MessageRequest : i
                    }
                    try {
                        resultList.push( await pinpoint.sendMessages(params) );
                    } catch ( e ) {
                        global.log.debug(`failed to sendMessages `);
                        global.log.debug( JSON.stringify( e ) );
                        global.log.debug(`params is `);
                        global.log.debug( JSON.stringify( params ) );
                    }

                }
            } 
            // do something if not have list
        } catch ( e ) {
          global.log.error( e );
        }
    }

above codes and below tests are ran on local PC and aws lambda(not local) both.

it working as i expected.

i test receive success rate and its peak almost 100%.
-> tested on foreground web which contained fcm token, and android which also use fcm, send 2 push every 1 min to each device till 12hours

so i tried to test batch sending test.
-> 10 threads request totally 200 times within 2 seconds. sending web and android 200 push each ( total 400 ).
result was quite bad.
it only success first 180 requests(sent 360).
i test again and each test have difference success count ( first 120 request only / first 50 request only etc.. )
i check for a logs and got some hint

{
    "name":"ThrottlingException",
    "$fault":"client",
    "$metadata":{
        "httpStatusCode":400,
        "requestId":"af5a94c1-0525-4645-b139-8001f677679",
        "attempts":3,
        "totalRetryDelay":994
    },
    "__type":"ThrottlingException",
    "message":"Rate exceeded"
}

okay, seems like i hit something of rate and got throttled.
but i have no clue of throttling on pinpoint pushmessage.
only i got is this words.

Maximum number of push notifications that can be sent per second in a campaign	25,000 notifications per second

ref : https://docs.aws.amazon.com/pinpoint/latest/developerguide/quotas.html#quotas-mobile

but i never exceed that number yet. even not close.

im just okay of 25000 notification per seconds, not 100 notification per seconds.

what did i missing?
did i do something wrong?

can someone give me a hint?

[juicycool92]

so, in case theres people like me come by,
this is my conclusion.

my error did not from pinpoint.
that error was came from aws-cli response.

seems like there's like limitation to invoke per seconds are exist to EACH SERVICES.
and each service has difference limitations.
this limitation can increase but you need to prove "why you need that and what did u tried", i guess.
ref: https://aws.amazon.com/ko/premiumsupport/knowledge-center/cloudformation-rate-exceeded-error/

im currently looking for using SQS, and send multiple message at single sendMessage function to preventing spamming api call,
didnt test yet so my answer might not be correct answer.

[juicycool92]

close ticket for now.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.