Releases: widdix/aws-cf-templates
Releases · widdix/aws-cf-templates
v4.0.0
Breaking changes in VPC templates: http://templates.cloudonaut.io/en/v4.0.0/migrate-v4/
v3.3.0
- [Security] Updated WordPress to 4.7.5
v3.2.1
- [Security] Updated Jenkins to 2.46.2
v3.2.0
v3.1.1
- [Improvement] Using more than two Availability Zones if possible (vpc-3azs, vpc-4azs)
- [Improvement] Provide a fallback Email for operational alerts
- [Improvement] Moved docs to http://templates.cloudonaut.io/ and also host each release versioned on S3
v3.1.0
- [Security] Updated WordPress to 4.7.4
- [New template] Alert topic that integrates with all other templates for operational alerts via SNS
- [Improvement] Added host based routing in ECS service template
- [Improvement] Jenkins agents now get the agent label
- [Improvement] Updated to Amazon Linux 2017.03
v3.0.2
- [Security] Updated Jenkins to 2.46.1
- [Improvement] Enabled HTTP/2 for CloudFront in WordPress and Static Website templates
v3.0.1
- [Security] Updated Jenkins to 2.32.3
- [Security] Updated WordPress to 4.7.3
v3.0.0
- [Security] Updated Jenkins to 2.32.2
- [New template] ECS cluster & service
- [New template] Wrapper template for legacy VPCs
- [Improvement] We open sourced the test suite of our templates as well
- [Improvement] Allow ssh from the world (0.0.0.0/0) in all templates if no bastion host is set
- [Improvement] Allow CloudTrail and Config to store their files on an s3 bucket in another account
- [Improvement] Updated Amazon Linux AMI to 2016.09.1.20161221
- [Improvement] Using new EFS region wide endpoint instead of AZ endpoints
- [Improvement] Added timeouts when downloading content on an EC2 instance
- [Bug Fix] fixed race condition in WordPress template during installation
v2.1.0
- [Security] Updated Jenkins to 2.19.3
- [New template] VPC Endpoint to S3
- [Improvement] The Wordpress template use of EFS now to share state on disk
- [Improvement] Subnets in VPC templates now export their AZ
- [Improvement] The Jenkins Agents template now uses only one ALB to save costs
VPC Endpoint to S3
This template describes a VPC endpoint to securely route traffic within a VPC for private instances to access S3 without the need of a NAT Gateway, NAT instance, or public internet. Refer to AWS VPC endpoint documentation if this is necessary for your stack. By default, access to all S3 actions and buckets is allowed, but may be constrained with a policy document.