Deepen Panchal Sorry, I should have been more specific. This is basically the profile name I’ve used to grant IAM permissions for serverless deployments. You could use one of the options listed here to configure your AWS credentials. https://serverless.com/framework/docs/providers/aws/guide/credentials/
Maybe it's a good idea to first create and deploy a simple nodejs app to aws-lambda and see if works for you — may be the issue is with local-development env.
Can you also try posting the error logs, I’ll try my best to help you out.
prabhuram I am assuming this response is coming from your alexa device.
So, It looks like you haven’t enabled the skill yet in your alexa device. Once deployed, your skills will appear in https://developer.amazon.com/alexa/console/ask however you still need to enable the skill in https://alexa.amazon.com/spa/index.html#skills check the DEV SKILLS section.
CDN can handle large traffic spikes and bursts — by offloading and caching static content on a CDN, you can accommodate a larger number of simultaneous users with your existing infrastructure. For above use case (a read-heavy news website), CDN has helped us with improved performances, also we could scale down the existing infrastructure for web…
Dennis Micky Jensen — Could be a DNS issue. May be you can consider to map only one of your read replica to a CNAME in your private hosted zone and see it works first. Name: read1.db.yourdomain.com Type: CNAME Value: my-rds-read1.us-east-1.rds.amazonaws.com TTL: 0
@Silvia Berardo I’m talking about using SNS HTTP notification here, not emails. http://docs.aws.amazon.com/sns/latest/dg/SendMessageToHttp.html
You’ll need to create a subscription and then accept the messages sent by transcode service. Please see this gist.
Daron Tancharoen Thanks.
My application is read heavy application, but yes it still have write operations as well.
So in this instance, in the application layer, I have used 2 database connetions. One for read, the other one for writes, which connecting to RDS master.