No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Looking at the code for aws-apigateway, it seems that this wraps aws.apigateway. Is there any reason to use one or the other?

aws.apigateway is the AWS Classic library. It's the same as the Terraform module.
awsx.apigateway is an opinionated wrapper for aws.apigateway. If you like its conventions and don't want to configure any more than you have to, it might be the one for you.
@pulumi/aws-apigateway seems to be a wrapper over awsx.apigateway, at least according to the blurb at the top of the registry page. I don't know why this one has an advantage over the other two?

Ah, it says "as a package available in all Pulumi languages". Maybe awsx.apigateway is JS/TS only?

here's what chatGPT had to say :slightly_smiling_face:

When to Use Each
• *awsx.apigateway*:
    ◦ Use this if you want quick and easy setup with sensible defaults.
    ◦ Ideal for common use cases where you don't need extensive customization.
• *aws.apigateway*:
    ◦ Choose this when you need granular control over the API Gateway configuration.
    ◦ Useful if you have specific requirements that higher-level abstractions don't cover.
• *@pulumi/aws-apigateway*:
    ◦ Opt for this if you need a balance between simplicity and control, with features specifically designed for API Gateway.
    ◦ Good for cases where `awsx.apigateway` is too abstract but `aws.apigateway` feels too low-level.


The first two seem about right. I'll bow to ChatGPT's superior knowledge about the 3rd one.

ha! well, it sounds reasonable :slightly_smiling_face:

thanks for the help :slightly_smiling_face: