Email Forwarding on Amazon Web Service SES - amazon-web-services

I'm trying to set up an email to go to my custom domain name, which I will call "mydomainname". Currently I can send emails to "contact#mydomainname.com" and receive no error from sending the email, but the received email does not show up in my bucket or spam folder.
I've been following instructions on this github and this tutorial .
I don't understand what the github instructions mean for the instruction that states
"Modify the values in the config object at the top of index.js to specify the S3 bucket and object prefix for locating emails stored by SES. Also provide
the email forwarding mapping from original destinations to new destination."
I've tried to guess at what that means by changing the index.js file to the as shown here
I suspect there is an error in the code above,
As well, I receive the following error for the JSON in my lambda-basic-execution
And the error that I receive
.
.
.
I've included the following screenshots for reference
This is my recipient rule
This shows some information on the settings of my lambda page

The error you show is just a warning for the resource not existing, you should still be able to create the policy for the same.
See if you actually did create the policy and test it again.
Also make sure there are no invalid or duplicate rules which may be causing the issue

Related

AWS API Gateway to Simple Notification Service

I'm trying to use the AWS console to pass a message straight from an API Gateway into an SNS queue. All the examples I've seen seem to go via a Lambda, but all the documentation and settings seem to suggest this step isn't necessarily needed.
I've got the below setup, but keep getting the error of
Execution failed due to configuration error: No match for output mapping and no default output mapping configured. Endpoint Response Status Code: 400
The mapping template section has: "When no template matches the request Content-Type header" set which the "Help" section suggests the body (which is where the json string is posted) is passed through if I've got no template set up, but maybe I'm misunderstanding this.
What am I missing?

API Gateway Error : Site can't be reached

I followed the process from this video : here
I created the Lambda function, and the API, and when I am testing in the API Gateway editor, it is working properly. Giving status 200 and correct output.
Here when I deployed I gave the url + /opencv as said in the video, but the browser doesn't give any output and gave the result site not reachable.
I also tried without the resource /opencv and when I run the url which I get after deployment I get {"message":"Missing Authentication Token"} error.
So, how am I able to get the output while testing in the AWS tool as shown in the picture above but after deployment I am not able to get. What am I missing?
Check Your Stages under Resources and verify the URL and try to create a new stage. i just followed the same steps and i can see it is working fine. In order to reproduce, i deleted the Stage and verified it gives me the error which you have mentioned. So try to reproduce the steps again by creating a new stage under resources as it will enable you to have auto new URL and then verify. Incase if it does not work, do share your stage Screenshot next time.
For others that get the same issue. One solution is to wait a bit:
I also had this error when first time deploying the API GW. It then started working fine ~5-10min later.

S3 error document for static site?

In the context of hosting a static SPA website, under what circumstances would the error document on S3 be served?
Is it something that should never happen if everything is set up correctly?
Source: http://docs.aws.amazon.com/AmazonS3/latest/dev/CustomErrorDocSupport.html
Custom Error Document: You can optionally provide a custom error document that contains a user-friendly error message and additional help. You provide this custom error document as part of adding website configuration to your bucket. Amazon S3 returns your custom error document for only the HTTP 4XX class of error codes.
Lets say your website is example.com/ and a visitor goes to example.com/thispagedoesnotexist, if you setup your Error Document the visitor will get the 'friendly' error-page. As you can't control what a visitor of your website does. My personal opinion is to always setup a 'friendly' error-page as you can't control visitor behaviour to the detail.

Google Cloud Pub/Sub - INVALID ARGUMENT error in Push subscription

I created a topic & then tried to create a Subscription with "Push" delivery type. When I use the domain https://www.omnea.com/push/google-handler (the link doesn't exist), it works. However, when I use the url https://apidev2.omnea.org/push/google-handler, it throws INVALID_ARGUMENT error.
Both have the same certificate authority. The only difference I see here is the domain & sub-domain.
Is there any other reason due to which I receive this error?
Got some hard time too figuring out what's happening.
You need to add your sub domain as verified domain in the API console: https://console.cloud.google.com/apis/credentials/domainverification

Boto error repeatedly appearing on Sentry server

I've configured a Sentry (https://github.com/getsentry/sentry) server to log and manage all the uncaught exceptions on my Django application, that uses Boto to send e-mail via Amazon SES. It is working well and sending e-mail alerts whenever something wrong occurs.
The problem is, almost everytime an error happens and Sentry sends me an alert, it also notifies me of another error (an exception on Boto while sending an email), but it doesn't show me what is the e-mail. I've tried all the bits of my code that send e-mail, and they are all ok. My SES config is also fine, since my application is sending e-mails to a lot of different customers daily
The error reported by Sentry is:
boto in _handle_error
<ErrorResponse xmlns="http://ses.amazonaws.com/doc/2010-12-01/">
<Error>
<Type>Sender</Type>
<Code>MessageRejected</Code>
<Message>Email address is not verified.</Message>
</Error>
<RequestId>4a085303-817a-11e4-b846-79819d3408ac</RequestId>
</ErrorResponse>
After this, i usually receive another error, but all it says is
boto in _handle_error
400 Bad Request
But besides all this MessageRejected warnings, when i go to my AWS Dashboard to check on SES, it shows no Rejects or Complaints, and just a really small number of Bounces (smaller than the amount of warnings i receive)
If i could at least see what email is he trying to send, it would help me debug this, but i can't find any clue about what's happening.
Boto config
The Boto section is used to specify options that control the operation
of boto itself. This section defines the following options:
debug: Controls the level of debug messages that will be printed by
the boto library. The following values are defined:
0 - no debug messages are printed
1 - basic debug messages from boto are printed
2 - all boto debugging messages plus request/response messages from httplib
Make sure you restart your Django server for the log level to take effect
The problem was the default email that Django sends to the emails on the ADMINS setting. Everytime we had an exception, it was trying to email root#localhost (the default value for ADMINS), but since this emails does not exists, it was failing to do so.