Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COThanks for the response. Actually In my Java application Im using `SubscribeRequest` to subscribe user from SNS topic. So It sends an email to customer, he needs to confirm it. My coding is like this: `SubscribeRequest subscribeReq = new SubscribeRequest() .withTopicArn(TopicArn) .withProtocol(theNotificationType) .withEndpoint(emailId); AWS_SNS_CREDENTIALS.subscribe(subscribeReq);` Is there any way to subscribe the user without sending emails to customer? How can we get the token value? I'm new to Amazon web service. Sorry for asking too much questions.
      singulars
    2. COThe whole point of the token confirmation is to make it so that you cannot subscribe email addresses you don't have access to because of spam reasons. SNS does not incorporate the trust logic that SES has, so they can't just let you send emails using the service without getting a confirmation from the person who can access the email.
      singulars
    3. COIMO, SNS is not a good product to use to send emails directly to customers. It is a nice thing for internal tools to get notifications or to subscribe admins to alerts and stuff. However, the email offering does not provide the flexibility required to develop an application around it. Your best bet would be to use SNS for the fanout, and then use SES to actually send you email. That way you can control the formatting of the email, and the from address, and get bounce notifications and everything else SES provides.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload