Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have a general understanding of serverless architecture.
I was wondering what are the top pro's and con's using this architecture compared to the previous generally used architectures.
Pros
Invoke Lambda Functions only during event triggering VS keeping Instance(s) idle for a reasonable amount of time.
Pay only for what you are going to use VS pay for the running idle instance.
Easily Integrate with other popular AWS Services e.g API Gateway, S3, SNS, CloudTrail, etc.
IAM Policies are configurable to each lambda function.
Scalable depending on the rate of invocations.
Cons
Only 15 minutes with finite RAM is supported as of now ,so not for heavy and complex processing.
Only popular programming language support.
Conclusion
It depends on your use-case as to whether use lambda or not !
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 days ago.
Improve this question
What's the best way to track custom metrics from Lambda functions?
I have a GraphQL API running on AWS Lambda and would like metrics on which queries are being called, how much they're called, errors and successes rates, duration's, etc. Additional, I'd like to have the ability to add alerts for these metrics.
Is it possible to use Prometheus for this? Or is AWS CloudWatch more suitable?
I've looked into using Prometheus however it looks like it would require setting up a Pushgateway which it seems is discouraged. For most metrics and alerting I use Prometheus and Grafana because I've found them to be more ergonomic. I do use CloudWatch with custom dashboards and alerts for a variety of default metrics however I'd prefer to use Prometheus+Grafana if feasible.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 months ago.
Improve this question
What is the best approach when I want to have a two AWS lambdas talk to each other?
I want one lambda to be called by users in my cognito pool but the other lambda should only be called by my first lambda.
Should i utilise a message queue, or how can i properly call into my other lambda as a rest endpoint?
An AWS Lambda function can Invoke() another AWS Lambda function.
Please note that the two Lambda functions do not "communicate with" or "talk to" each other. Rather, one function calls the AWS Lambda service with the Invoke API call, asking it to run the other Lambda function. The result of the second Lambda function will then be returned as a response to the Invoke request.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
If we have a requirement on 24 hours max for RPO on data stored in Amazon S3, would S3IA be able to satisfy that?
Yes, you can say it could because Amazon S3 data is automatically replicated to 3 AZs in the region, so having a 24 hrs max RPO can ba handled. But what if disaster happens in the entire region?
Would we need a cross region replicate to satisfy this RPO requirement?
Part of your business's recovery objective goals should include identifying what type of outages are worth spending the money to guard against. Do you want to protect your business from a temporary regional AWS outage? Do you want to protect your business from a huge natural disaster that permanently destroys an entire AWS region? Do you want to protect your business from some sort of social or political upheaval that causes AWS to be shutdown in an entire country? Your business has to evaluate the level of outage that they anticipate to be an actual threat, as well as the level of outage that is worth the investment of capital to guard against.
I'm saying all this to explain why asking random strangers on the Internet if you need to implement cross region replication makes no sense. Only your business can answer that question, and simply staging an RPO number does not provide enough information.
Cross region replication, not only to a different region but also to an S3 bucket in a different account, is always a good idea. This gives you protection not only from an AWS regional outage, but also from your AWS account being hacked. Depending on what sort of outages you want to guard against, you may want that bucket to be in a different country, or even in a different hemisphere.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
How can I create a real time graph ticker updating every 2-3 secs just like NASDAQ for data streams coming from my AWS Kinesis Firehose to AWS Kinesis Analytics? How do I get the output from Kinesis Analytics? Trying to achieve something close to this.
We did something similar. One possible solution for your use case:
Configure an Elasticsearch cluster.
Use a Kinesis to Elasticsearch connector. This will take care of automatically flowing your data from Kinesis to ES.
Use Kibana to visualize your ES data. It allows configuring the refresh interval and creating dashboards.
You might have to put some effort in setting up Elasticsearch. But it is all open-source, and so is Kibana.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I run a EU-based website on Amazon EC2, and currently send around 13,000 emails a day through Amazon SES. Much of the email throughput is during the early hours of the morning.
Now that Amazon SES has instances in Europe, are there any advantages to me switching from the current US-west SES servers into Europe? Does it make any difference in terms of deliverability or anything else?
The only benefit I can really see is one of slight speed increase; but email sending is done away from anything user-facing anyway.
The only advantage would be in terms pricing, only if you have the servers that are sending email in the same EC2 region as the SES region. In other words if both of them are in the same region, you wouldn't get charged any "OUT" data.
Otherwise you would get charged $0.02 /GB . If you look at the AWS EC2 pricing here: http://aws.amazon.com/ec2/pricing/ , it would be here:
Of course, if your clients are outside Amazon you would get charged "IN" and "OUT" data.