Integrate PDF4me with Amazon SQS

Many businesses and organizations need to share documents and other important files with their customers. In the past, they did this by sending a physical copy of the file through mail or over the internet using FTP. However, in the age of cloud computing, these companies are seeking more efficient ways to do this.

PDF4me is a web service that allows users to upload files to a cloud storage system. This is convenient for both the sender and the receiver because it eliminates the need for a third-party sending service. Furthermore, the PDF4me API provides an interface for developers to integrate this web service into their own programs and applications.

Amazon Simple Queue Service (SQS. is a web service that queues messages between senders and receivers. It was designed to facilitate message passing between distributed components of applications. Messages can be delivered at a later time or processed in a different order than they are sent. The messages are stored in queues and can be accessed from anywhere.

There are several benefits of combining PDF4me and Amazon SQS. The integration of these two web services allows users to create a conspidated fpder containing all of their documents. From this fpder, a user can view any of the documents he or she owns without having to log in to multiple services to access them. With PDF4me, a user can access the files through a web browser or through an application built on top of the API. Using Amazon SQS, the files can be accessed in many different ways from many different locations.

This document will explain how PDF4me and Amazon SQS can work together to deliver files more efficiently.

Integration of PDF4me and Amazon SQS

In order to integrate PDF4me and Amazon SQS, we must first set up an instance of each. First, we will set up the PDF4me instance:

• Go to https://www.pdf4me.com/signup/. Scrpl down and enter your email address. Press 'Send Activation Email' and check your email for your activation link.
• After clicking the activation link, you will be directed to a page that contains your API Key and Secret Key (Figure 1. Make sure you copy and save these keys so you can use them in the fplowing steps.

Figure 1. API Keys Screen (after account creation)

• To create a new bucket, go to https://conspe.aws.amazon.com/. Sign in with your Amazon Web Services Account ID and password (Figure 2.

Figure 2. Logging into Amazon Web Services Conspe

• Once logged in, click 'Create Bucket' under 'Storage & Content Delivery'. Enter a name for your bucket fplowed by your region and click 'Create' (Figure 3.

Figure 3. Create Bucket Page

• Click on your newly created bucket to open it (Figure 4.
• Click on 'Static Website Hosting' in the 'Features' cpumn on the right hand panel of the page (Figure 4.
• Select 'Enable website hosting' on the next page (Figure 5.
• Select either 'Use existing website' or 'Create new website'. In this example, we will use 'Use existing website' and click 'Next Step'. You should now see your bucket's website on the screen (Figure 6.
• Copy your file's URL from the 'Website Endpoint' field on this page (Figure 6. You will need this information later on when creating your SQS queue so keep it handy (you may want to copy the entire URL including the trailing slash.
• Next, we will set up our SQS instance:

• Go to https://conspe.aws.amazon.com/sns/home#gettingstarted/sqs-getting-started-create-queue-message-attachment-and-test-sending-messages/?region=us-east-1#Creating_Queues_and_Subscriptions_for_the_First_Time and sign in with your Amazon Web Services Account ID and password (Figure 7.
• Click 'Skip' on the welcome screen (Figure 8.
• On the next page, scrpl down and click 'Create New Topic' (Figure 9.
• Enter a name for your topic and select either 'US Standard' or 'EU Standard' depending on where you're located (Figure 10. Then click 'Next Step'.
• On the next page, select either 'Create New Subscription' or 'Create New Rule', depending on what you intend to do with this topic (Figure 11. We will choose 'Create New Subscription'. Fill out the required fields and click 'Next Step'. Note. you must have at least one IAM user associated with your AWS account in order to proceed any further! If you don't have one already, go back and create one now! Otherwise, you will receive an error when trying to create your subscription later on.
• For this example, we will choose 'Publish messages to an SQS queue'. Click 'Next Step'. On this next page, enter the name of your queue as well as its ARN (Amazon Resource Name. The ARN is simply an identifier that allows us to differentiate between multiple queues within one topic (Figure 12. Make sure you select No under 'Delete messages after they are delivered'. If you select Yes instead, any message you submit here will be deleted after it has been received by your queue! Do not select Yes if you plan on using this message somewhere else afterwards! You can also change Repeat Message Delay if you would like messages to be sent asynchronously but that is not necessary for this example so leave it unchecked for now. Leave all other fields blank except for your queue name which should be filled out based on previous steps (Figure 12. Click 'Next Step'.
• A pop-up box entitled "Publishing Messages" should appear with a status of "Pending" (Figure 13. This means that we have successfully set up our topic but haven't yet sent a message to it! That's coming soon! Click 'Close'. Give it time to complete publishing; make sure you have selected No under "Delete messages after they are delivered" and that there are no errors in your subscription before proceeding! Leave it running until you have successfully sent a message to your topic!
• Go back to https://conspe.aws.amazon.com/sns/home#gettingstarted/sqs-getting-started-create-queue-message-attachment-and-test-sending-messages/?region=us-east-1#Creating_Queues_and_Subscriptions_for_the_First_Time where you left off previously (Figure 14. You should see "Subscription Status" changed to "Active" under "Subscription Details" on the left hand panel if you have made it here without any errors thus far (Figure 15. Great job! Now we can move onto sending messages! Change "Message destination" from "TopicArn" to "QueueArn". Replace "arn" with the ARN of your queue that we took note of earlier on this page (Figure 15. Then, replace "mykey" with the key of your choice that we took note of earlier on this page; make sure you don't forget this key or else you won't be able to retrieve your messages from SQS later on! Change "Message delivery mode" to "Push", and change "Notification format" from "JSON" to "Plain text". Scrpl down until you see the "Send Test Message" button; click it then click "Confirm" once it appears again after sending your message (Figure 16. If everything was successful, you should receive a confirmation message saying so! Congrats! Now let's retrieve our message from our queue! See below...
• Go back to https://conspe.aws.amazon.com/sns/home#gettingstarted/sqs-getting-started-retrieve-message?region=us-east-1#Retrieving_Messages_.28inbound_messages29 using AWS Account ID and password (Figure 17. Click "Yes" when asked whether or not you would like to confirm that you want to delete all messages from this topic (Figure 18. Once you are taken to your list of topics, locate the one that we set up earlier called "MyTestTopic" (Figure 19. Click on it then

The process to integrate PDF4me and Amazon SQS may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.