Amazon API Gateway HTTP APIs

[ewbankkit]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Amazon API Gateway offers faster, cheaper, simpler APIs using HTTP APIs.

The API Gateway HTTP API is in preview.

New or Affected Resource(s)

• aws_api_gateway_v2_api
• ...

Potential Terraform Configuration

resource "aws_api_gateway_v2_api" "example" {
  protocol_type = "HTTP"
}

References

Announcement.
Blog post.
Developer guide.

Requires AWS SDK v1.25.48:

• Update module aws/aws-sdk-go to v1.25.48 #11149

Related:

• API Gateway- Websocket #7004

[rpstreef]

This is an apigatewayv2 resource just like the websockets API

[bionicles]

here is the line of code which designates the api type:
https://github.com/aws/aws-sdk-go/blob/2dfbfbc3d3a60ab6ef72537b890eff246f6cb1f2/models/apis/apigatewayv2/2018-11-29/api-2.json#L4575

seems like a big job to build this, but users (self included) would appreciate websockets and cheaper/faster/simpler api

I am interested to contribute but not sure where to start ... how do you decide what counts as a data source, resource, etc?

[ewbankkit]

HTTP APIs are now GA.

Announcement.
Blog post.

Requires AWS SDK v1.29.23:

• Update module aws/aws-sdk-go to v1.29.24 #12359

[AlienHoboken]

@ewbankkit looking at this it seems that your other PRs with the constituent resources to build on top of the gateway are still pending. Is there any help that you need on those? I haven't contributed here yet but definitely willing to.

Thanks for the great PR and getting this out there day 1 of GA. Many people are looking forward to leveraging HTTP APIs and your work helps make this possible 🎉

[ewbankkit]

Preview functionality:

• aws_apigatewayv2_api resource - r/aws_apigatewayv2_api: Add CORS configuration and quick start attributes #12452
  • Add cors_configuration attribute
  • Add credentials_arn, route_key and target attributes to support quick create.
    This will create API Gateway managed aws_apigatewayv2_integration, aws_apigatewayv2_route and aws_apigatewayv2_stage resources.
• aws_apigatewayv2_authorizer resource
  • Add jwt_configuration attribute to support JSON Web Tokens. This also impacts the aws_apigatewayv2_route resource
• aws_apigatewayv2_stage resource
  • Add auto_deploy attribute
  • Investigate DeleteRouteSettings API
  • Investigate default stage (and route)
• aws_apigatewayv2_integration resource
  • Add payload_format_version attribute

GA functionality:

• Add aws_apigatewayv2_vpc_link resource - New resource: aws_apigatewayv2_vpc_link #12577
• aws_apigatewayv2_stage resource
  • Investigate DeleteAccessLogSettings API
• aws_apigatewayv2_route resource
  • Investigate DeleteRouteRequestParameter API

[vincenting]

Hi, any idea on providing a body attribute for the aws_api_gateway_v2_api resource. It has similar behaviour to the body attribute in resource_aws_api_gateway_rest_api.go, but here we have to call different API to create (ImportApi) and update(ReImportApi) the API.

Is there any plan for that, it will help the developers like me who want to migrate the RestAPIGateway based infra to the new version. (I haven't developed GoLang for a long while, I will try to create an MR for that too)

[ewbankkit]

@vincenting My initial thinking around this was to recommend using the instructions in the developer guide to import the API using the AWS CLI and then use terraform import to adopt the API into Terraform. Either way I think you would have to write the HCL code for the resource.