DevOps Engineer/SRE - AWS at Lavoro autom inf e com ltda
Real User
Top 10
2024-10-25T19:52:00Z
Oct 25, 2024
API Gateway could be more user-friendly, especially in defining routes for new users. A friend of mine had difficulty with understanding where the API Gateway stages were and whether they were deployed. An interface more friendly for new users would be helpful.
There are features lacking in API Gateway, such as the timeout settings, which currently are set at 29 seconds. If the API Gateway doesn't get a response within that time, it results in a timeout. These parameters should depend upon the use cases.
The solution should include change data capture (CDC) features that will help reduce workload. The aforementioned feature can be introduced as a mini plug-in or additional license. In future versions of the product, there can be automated integration capabilities for applications through AI.
Senior Professional I-Software Engineer Lead at Capgemini
Real User
Top 5
2024-03-27T14:05:16Z
Mar 27, 2024
The solution has a major limitation compared to Google Cloud. Amazon API Gateway will wait for only 30 seconds to get a response from other services, such as the Lambda function. API Gateway can be directly integrated with the Lambda function, and a response from the Lambda function must be obtained within 30 seconds.
I faced issues with the timeout because some machine-learning scripts would take more than 30 seconds. Since the first invocation of AWS Lambda takes more than 30 seconds because of Lambda's cold start, Amazon API Gateway blocks that resource, thereby aborting the invocation.
Amazon API Gateway is expensive, making it one of the product's shortcomings where improvements are required. Amazon API Gateway needs to focus on minimizing latency.
It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end. Their support services come at a considerable cost, leaving room for improvement.
Head of Data & ML Engineering at a financial services firm with 10,001+ employees
Real User
Top 10
2023-09-01T04:23:46Z
Sep 1, 2023
The main concern is connectivity. When someone requests a mobile score, we need to query the backend DB using prospect numbers. This involves going from AWS to the Oracle DB in Oracle Cloud, fetching data through SQL queries, and then feeding it back to the model running on AWS. This process takes a considerable amount of time. It's like dealing with connectivity issues because of the direct connection. Although I find AWS API Gateway better than Oracle in many aspects, the network connectivity challenges force us to consider using Oracle API Gateway for our new product, LOS (Load Origination System). This new product will involve extensive interaction with the databases, and we cannot afford network connectivity issues. This is the only drawback I've encountered. Even though AWS API Gateway is better in several respects, we are leaning towards Oracle API Gateway due to its compatibility with our Oracle backend databases. Traditionally, enterprise databases are Oracle databases, and that's why we work with Oracle Cloud. We're also exploring MuleSoft, which offers a wide range of features and services, although cost is a concern.
When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions. This has led me to devise shortcuts that aren't entirely straightforward but serve my needs. It's important to consider the type of gateway endpoint carefully. There appear to be two distinct types. It's crucial to make an informed selection based on your project's requirements. When utilizing API Gateway, the choices one makes regarding endpoint types and properties are pivotal. After initially choosing an endpoint type, it is difficult to switch to a different type later on.
As for improvements, I haven't fully explored Amazon API Gateway yet, but I believe better governance and monitoring features would be beneficial. We are also interested in telemetry, analytics, and other features that are important for our API management. I would appreciate more comprehensive telemetry information, diagnostics, and improved monitoring capabilities for the services and endpoints.
The solution could improve signature validation. They should offer signature validation if there is any request. There needs to be some sort of mechanism. They need to be able to validate the signature at the API gateway level.
Independent Technology Consultant - Financial Softwares at a tech services company with 51-200 employees
Real User
2022-10-07T10:32:27Z
Oct 7, 2022
Currently, I'm not facing any issues with Amazon API Gateway, which satisfies my requirements. I'm pretty happy with what Amazon API Gateway offers, but as its pricing is on the higher side, that's one area for improvement in the solution. What I'd like to see in the next release of Amazon API Gateway is an improvement in the status checks you get from the monitoring feature of the solution. Currently, you get the number of requests received, the number of reports, etc., but if there are more details than what's given by Amazon API Gateway, that will improve the solution.
Amazon API Gateway can improve the user interface in some areas it could be more polished. In a future release, it would be beneficial for more documentation, even though their documentation is already very good, but better documentation could help us build more of what you want yourself.
The UI and UX of this solution could be improved. From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution.
The user interface could be improved, as well as customer support and having a local customer representative in a country. Monitoring could also be improved a bit.
Cloud Engineer at a retailer with 10,001+ employees
Real User
2021-09-30T15:25:22Z
Sep 30, 2021
When it comes to integration, it is currently integrated with CloudWatch monitoring. As a result, monitoring the APIs to external servers is not an option. This is a feature that should be added, similar to what we have for ServiceManager. Monitoring could be improved.
Software Development Manager at a financial services firm with 10,001+ employees
Real User
2021-09-29T15:56:14Z
Sep 29, 2021
We have not yet explored all of the capabilities. We are looking for a developer portal that may or may not be included, we are not sure. The integration could be improved.
Technical Manager at a computer software company with 10,001+ employees
Real User
2020-12-10T10:38:45Z
Dec 10, 2020
The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface.
Sr. Technology Specialist at a computer software company with 5,001-10,000 employees
Real User
2020-12-07T15:18:00Z
Dec 7, 2020
I am not completely satisfied with Technical Support. They were finding it difficult to get to the AWS API gateway. Also, the traffic percentage was not calculating correctly.
Digital Architecture Manager at a tech services company with 10,001+ employees
Real User
2020-07-13T06:55:00Z
Jul 13, 2020
It would be useful to have a more complete development environment for the developer, with different integrative capabilities to manage all the life cycles for the API. I think the full version formula for that is really useful. They should improve the development environment for easier integration.
One of the problems with using this solution is that you have to know a lot about the Amazon ecosystem, in terms of services, to be able to use it. For example, if you use it without the Web Application Firewall then you're going to get some attacks. You have to read the documentation and learn how to use it. This is a very large product, which means that there is a lot to learn and a lot of documentation to read. It is not clear to us how you create a direct connection between your on-premises network and the API gateway. In the documentation, it tells you to create a VPN, but I find this troubling at the application level. You should be able to use MTLS. This is what you want rather than direct connect because of security issues. I don't think that this is a documentation issue. Rather, I think that it is a feature that can be improved.
Software architect at a insurance company with 10,001+ employees
Real User
2019-08-11T06:26:00Z
Aug 11, 2019
The way they manage the headers could be improved and made easier. There are some certificates that they will not let us use. I would like to see the web console improved. There should be more videos and documentation about the new features that are released every month.
Software Architect at a retailer with 51-200 employees
Real User
2019-07-16T05:40:00Z
Jul 16, 2019
You can code anything and hook it on to it but it doesn't give you stuff out of the box like the other gateways give you. You can do anything with it because you just attach a LAN to it and it will do anything, but that's to the custodian. You know you're not using the power of the gateway. It's hard to configure. There's a lot of options but it's very hard, it's very confusing. In the future, I'd like to see Amazon develop a portal and monetization that is not only for the Amazon Marketplace.
Amazon API Gateway facilitates internal APIs exposure to external users, manages requests, and enhances security with authentication. It efficiently handles serverless architectures with AWS Lambda integration, supporting cloud-based API management. Amazon API Gateway acts as a gateway for backend microservices, making it suitable for real-time use cases. It enables secure communication, traffic routing, and access control management. With its strength in integrating AWS services, it offers...
API Gateway could be more user-friendly, especially in defining routes for new users. A friend of mine had difficulty with understanding where the API Gateway stages were and whether they were deployed. An interface more friendly for new users would be helpful.
There are features lacking in API Gateway, such as the timeout settings, which currently are set at 29 seconds. If the API Gateway doesn't get a response within that time, it results in a timeout. These parameters should depend upon the use cases.
The solution should include change data capture (CDC) features that will help reduce workload. The aforementioned feature can be introduced as a mini plug-in or additional license. In future versions of the product, there can be automated integration capabilities for applications through AI.
The solution has a major limitation compared to Google Cloud. Amazon API Gateway will wait for only 30 seconds to get a response from other services, such as the Lambda function. API Gateway can be directly integrated with the Lambda function, and a response from the Lambda function must be obtained within 30 seconds.
I faced issues with the timeout because some machine-learning scripts would take more than 30 seconds. Since the first invocation of AWS Lambda takes more than 30 seconds because of Lambda's cold start, Amazon API Gateway blocks that resource, thereby aborting the invocation.
The tool's UI requires time to understand.
A lower price would definitely be an improvement. I would like to see more AI-based capabilities in future releases.
Amazon API Gateway is expensive, making it one of the product's shortcomings where improvements are required. Amazon API Gateway needs to focus on minimizing latency.
It is somewhat costly, particularly when it introduces server-related features, which are often scheduled on our end. Their support services come at a considerable cost, leaving room for improvement.
The main concern is connectivity. When someone requests a mobile score, we need to query the backend DB using prospect numbers. This involves going from AWS to the Oracle DB in Oracle Cloud, fetching data through SQL queries, and then feeding it back to the model running on AWS. This process takes a considerable amount of time. It's like dealing with connectivity issues because of the direct connection. Although I find AWS API Gateway better than Oracle in many aspects, the network connectivity challenges force us to consider using Oracle API Gateway for our new product, LOS (Load Origination System). This new product will involve extensive interaction with the databases, and we cannot afford network connectivity issues. This is the only drawback I've encountered. Even though AWS API Gateway is better in several respects, we are leaning towards Oracle API Gateway due to its compatibility with our Oracle backend databases. Traditionally, enterprise databases are Oracle databases, and that's why we work with Oracle Cloud. We're also exploring MuleSoft, which offers a wide range of features and services, although cost is a concern.
When working with XML payloads, there can be issues due to the lack of a seamless connection between API Gateway and Lambda functions. This has led me to devise shortcuts that aren't entirely straightforward but serve my needs. It's important to consider the type of gateway endpoint carefully. There appear to be two distinct types. It's crucial to make an informed selection based on your project's requirements. When utilizing API Gateway, the choices one makes regarding endpoint types and properties are pivotal. After initially choosing an endpoint type, it is difficult to switch to a different type later on.
The solution's configuration for API gateways using SAM and CloudFormation templates could be more accessible.
The solution's performance and scalability could be better than Azure.
As for improvements, I haven't fully explored Amazon API Gateway yet, but I believe better governance and monitoring features would be beneficial. We are also interested in telemetry, analytics, and other features that are important for our API management. I would appreciate more comprehensive telemetry information, diagnostics, and improved monitoring capabilities for the services and endpoints.
The solution could improve signature validation. They should offer signature validation if there is any request. There needs to be some sort of mechanism. They need to be able to validate the signature at the API gateway level.
When it comes to DDoS protection, I would like to see that become available at the API Gateway level.
Currently, I'm not facing any issues with Amazon API Gateway, which satisfies my requirements. I'm pretty happy with what Amazon API Gateway offers, but as its pricing is on the higher side, that's one area for improvement in the solution. What I'd like to see in the next release of Amazon API Gateway is an improvement in the status checks you get from the monitoring feature of the solution. Currently, you get the number of requests received, the number of reports, etc., but if there are more details than what's given by Amazon API Gateway, that will improve the solution.
Amazon API Gateway can improve the user interface in some areas it could be more polished. In a future release, it would be beneficial for more documentation, even though their documentation is already very good, but better documentation could help us build more of what you want yourself.
The UI and UX of this solution could be improved. From a use cases perspective, you need to have an internal and external gateway. AWS can only handle external traffic so has to be used together with another solution.
The user interface could be improved, as well as customer support and having a local customer representative in a country. Monitoring could also be improved a bit.
When it comes to integration, it is currently integrated with CloudWatch monitoring. As a result, monitoring the APIs to external servers is not an option. This is a feature that should be added, similar to what we have for ServiceManager. Monitoring could be improved.
We have not yet explored all of the capabilities. We are looking for a developer portal that may or may not be included, we are not sure. The integration could be improved.
The user interface, in general, can be better. The user interface for the entire Amazon cloud can be more friendly. There are some scenarios that are not really easy to manage and configure through the user interface.
I am not completely satisfied with Technical Support. They were finding it difficult to get to the AWS API gateway. Also, the traffic percentage was not calculating correctly.
It would be useful to have a more complete development environment for the developer, with different integrative capabilities to manage all the life cycles for the API. I think the full version formula for that is really useful. They should improve the development environment for easier integration.
One of the problems with using this solution is that you have to know a lot about the Amazon ecosystem, in terms of services, to be able to use it. For example, if you use it without the Web Application Firewall then you're going to get some attacks. You have to read the documentation and learn how to use it. This is a very large product, which means that there is a lot to learn and a lot of documentation to read. It is not clear to us how you create a direct connection between your on-premises network and the API gateway. In the documentation, it tells you to create a VPN, but I find this troubling at the application level. You should be able to use MTLS. This is what you want rather than direct connect because of security issues. I don't think that this is a documentation issue. Rather, I think that it is a feature that can be improved.
The way they manage the headers could be improved and made easier. There are some certificates that they will not let us use. I would like to see the web console improved. There should be more videos and documentation about the new features that are released every month.
The pricing could be better. Also, possibly better technical support services or possibly just more documentation to assist users.
You can code anything and hook it on to it but it doesn't give you stuff out of the box like the other gateways give you. You can do anything with it because you just attach a LAN to it and it will do anything, but that's to the custodian. You know you're not using the power of the gateway. It's hard to configure. There's a lot of options but it's very hard, it's very confusing. In the future, I'd like to see Amazon develop a portal and monetization that is not only for the Amazon Marketplace.