AWS CloudFormation updates for Amazon API Gateway, AWS CodePipeline, Amazon S3, AWS IAM, Amazon ECS, Amazon RDS, Amazon ES, AWS Lambda and more

As part of both re:invent related launches, as well as community-prioritized requests from our public coverage roadmap, we are pleased to announce support for over two dozen new and updated CloudFormation resource types. You can now use CloudFormation templates to configure and provision additional features for AWS CodePipeline, Amazon API Gateway, AWS Lambda, Amazon Elasticsearch Service (Amazon ES), AWS Identity and Access Management (IAM), and more AWS resources. CloudFormation periodically releases additional support, making it easier for developers to configure and provision AWS services.

With this release, CloudFormation users can:

• Create an HTTP API, JSON web tokens (JWTs) Authorizer and stage for HTTP API, and specify VPC endpoint IDs of an API to create Route53 aliases in Amazon API Gateway.
• Specify a provisioned concurrency configuration for a function's alias and version in AWS Lambda.
• Specify parameter in AWS Step Functions to enable express workflows.
• Specify an access point in Amazon Simple Storage Service (S3).
• Create an analyzer for AWS IAM Access Analyzer.
• Specify a discoverer, schema, and event associated with an event bus in Amazon EventBridge.
• Configure destinations and error handling for asynchronous invocation in AWS Lambda.
• Specify the variable namespace associated with an action in AWS CodePipeline.
• Specify an Amazon Simple Queue Service (Amazon SQS) queue or Amazon Simple Notification Service (Amazon SNS) topic destination for discarded records, the maximum age of a record that AWS Lambda sends to a function for processing, the maximum number of times to retry when a function returns an error, the number of batches to process from each shard concurrently, as well as to split a batch in two and retry if a function returns an error in AWS Lambda.
• Specify the granularity, in seconds, of returned data points in Amazon Cloudwatch Alarms.
• Specify which task set in a service is the primary task set and create a task set in the specified cluster and service, the setting to use when creating a cluster, the deployment controller to use for the service, the FireLens configuration for the container cluster, the total amount of swap memory (in MiB) a container can use. You can also tune a container's memory swappiness behavior in Amazon ECS.
• Use the latest version of AWS WAF, a web application firewall that lets users monitor HTTP(S) requests that are forwarded to an Amazon API Gateway API, Amazon CloudFront, or an Application Load Balancer.
• Create a Contributor Insights rule in Amazon CloudWatch Logs.
• Specify the caching behavior, the conflict detection and resolution strategy, the ARN of the AWS Lambda that is used for handling conflicts, of your AWS AppSync resolver, the delta sync configurations for your versioned AWS AppSync data source and enable resolver caching with AWS AppSync.
• Enable the HTTP endpoint for an Aurora Serverless DB cluster and use Kerberos Authentication to authenticate users that connect to the DB instance in Amazon RDS.
• Specify any tags for the Elastic IP address in Amazon EC2.
• Configure Amazon Elasticsearch to use Amazon Cognito authentication for Kibana.
• Specify which version of AWS Glue a machine learning transform is compatible with.
• Specify a list of tags that you want to attach to the newly created user in AWS IAM.
• Specify a custom domain on an OpsWorks for Chef Automate Server running Chef Automate 2.0, a PEM-formatted HTTPS certificate for a server with a custom domain and a private key in PEM format for connecting to a server that uses a custom domain in AWS OpsWorks.
• Specify the redrive policy JSON assigned to the subscription in Amazon SNS.
• Use ZipFile in nodejs10.x for AWS Lambda RunTime.
• Create a new managed node group in Amazon EKS.

These resources are now available in all public AWS Regions as well as all AWS GovCloud Regions. For more information, see the AWS Region Table.

For more information, please refer to the CloudFormation release history page.