This page describes how to integrate your Sensedia solutions (Adaptive Governance and Developer Portal) with AWS gateways, allowing for the import and governance of APIs (native connections) published in Amazon API Gateway.
See in this page:
The Amazon API Gateway is structured into two main infrastructures (v1 and v2). API import through native AWS connections supports both.
REST API (v1). The traditional version of API Gateway, providing the most comprehensive set of API management features. View official documentation
HTTP API (v2). The newer Amazon API Gateway infrastructure, optimized for lower latency and reduced cost, focused on high-performance HTTP APIs and simplified integrations with AWS services. View official documentation
For a detailed comparison between these two versions, see: Differences between REST APIs and HTTP APIs
The table below summarizes the main characteristics of the supported API types:
Feature | REST API (v1) | HTTP API (v2) |
|---|---|---|
| Primary focus | Advanced API management features | High performance and lower cost |
| Portal Apps support | Yes | No (limitation of the AWS HTTP API model) |
| Import via native connection | Yes | Yes |
NOTE
- The creation of the native connection with AWS and the configuration of credentials is identical for both versions. The distinction occurs only at the time of API import.
- Currently, our solutions only support APIs of types REST (v1) and HTTP (v2). APIs of type WebSocket are not supported in this integration flow.
To create a connection for AWS API Gateway, you must enter your AWS credentials on the Connections screen.
These credentials must be obtained from the AWS side.
Access the AWS Management Console and follow the steps below to:
TIPRefer to the AWS documentation for more details.
NOTETo list and import your APIs, ensure that your access policy in AWS grants permission to the correct apigateway service resources, depending on the gateway version:
- For v1 gateways (REST): The policy must allow access to resources under the /restapis namespace.
- For v2 gateways (HTTP): The policy must allow access to resources under the /apis namespace.
If your policy only allows one of these resource sets, you will only see the corresponding APIs. If there is no permission for either of them, an error will be displayed on the import screen.
There are several ways to create an IAM user in your AWS account.
Follow the steps below to create a user through the AWS Management Console:
In the Permissions tab, under Permissions policies, click the Add Permissions button, and then click Create inline policy.

In the user list, select adaptive_governance_integration_aws and click the Security credentials tab.

Select the option Application running on an AWS compute service.

NOTECheck the confirmation box at the bottom of the page.
Follow the steps below to create a new connection.
Select the connection mode: whether it is native (data updated directly with the provider) or not (manual upload).

Non-native connection:
Define a name for the connection and click NEXT.

Confirm the information and click SAVE.
Native connection:
Define a name for the connection and click NEXT.

Select a connection mode: Access Key or IAM (Role).

For Access Key, provide:
AWS Access Key Id: the key for your AWS resource.
AWS Secret Access Key Id: the AWS key secret.

Review the information and click SAVE.
For IAM:
Configure your role: copy the example code shown in this section and use it in your AWS provider to create a role:
Role ARN: paste the generated Role ARN here.
Review the information and click SAVE.

Importing APIs through a native AWS connection supports multiple types of API Gateways.
The supported API types are:
See more details about each type.
These types are displayed in the Protocol Type column during the import process.
To import APIs, follow the steps below:
Access the Connections screen by clicking on the left side menu or the card on the home screen.
Find the connection you want to edit and click the
icon. If necessary, use the search bar to locate the desired connection.
IMPORTANTCredential generation (App creation) in the Developer Portal is currently not supported for HTTP (v2) type APIs, due to an inherent limitation of this version of the AWS Gateway.
In these cases, the Enable Apps registration option remains disabled in the API Docs settings of the Portal Manager.
NOTEThe Discovery feature also automatically identifies and unifies APIs from both versions (REST and HTTP), provided that the IAM user's access permissions cover the necessary resources. If you have permission for only one of the versions, only the corresponding APIs will be listed.
NOTEWhenever an API is updated, click
.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more