I would like to deploy a local zip file to Elastic Beanstalk using Terraform. I would also like to keep old versions of the application in S3, with some retention policy, such as keep for 90 days. If I rebuild the bundle, I would like Terraform to detect this and deploy the new version. If the hash of the bundle hasn't changed then Terraform should not change anything.
Here is (some of) my config:
resource "aws_s3_bucket" "application" {
bucket = "test-elastic-beanstalk-bucket"
}
locals {
user_interface_bundle_path = "${path.module}/../../build.zip"
}
resource "aws_s3_bucket_object" "user_interface_latest" {
bucket = aws_s3_bucket.application.id
key = "user-interface-${filesha256(local.user_interface_bundle_path)}.zip"
source = local.user_interface_bundle_path
}
resource "aws_elastic_beanstalk_application" "user_interface" {
name = "${var.environment}-user-interface-app"
}
resource "aws_elastic_beanstalk_application_version" "user_interface_latest" {
name = "user-interface-${filesha256(local.user_interface_bundle_path)}"
application = aws_elastic_beanstalk_application.user_interface.name
bucket = aws_s3_bucket_object.user_interface_latest.bucket
key = aws_s3_bucket_object.user_interface_latest.key
}
resource "aws_elastic_beanstalk_environment" "user_interface" {
name = "${var.environment}-user-interface-env"
application = aws_elastic_beanstalk_application.user_interface.name
solution_stack_name = "64bit Amazon Linux 2018.03 v4.15.0 running Node.js"
version_label = aws_elastic_beanstalk_application_version.user_interface_latest.name
}
The problem with this is that each time the hash of the bundle changes, it deletes the old object in S3.
How can I get Terraform to create a new aws_s3_bucket_object and not delete the old one?
This is related but I don't want to maintain build numbers Elastic Beanstalk Application Version in Terraform
Expanding on #Marcin comment...
You should enable bucket versioning and add a lifecycle rule to delete versions older than 90 days
Here is an example:
resource "aws_s3_bucket" "application" {
bucket = "test-elastic-beanstalk-bucket"
versioning {
enabled = true
}
lifecycle_rule {
id = "retention"
noncurrent_version_expiration {
days = 90
}
}
}
You can see more examples in the documentation:
https://www.terraform.io/docs/providers/aws/r/s3_bucket.html#using-object-lifecycle
Then I would simplify your aws_s3_bucket_object since we have versioning we don't really need to do the filesha256 just use the original name build.zip and good to go.
If you don't want to enable bucket versioning another way would be to use the AWS CLI to upload the file before you call terraform or do it in a local-exec from a null_resource here are a couple of examples:
https://www.terraform.io/docs/provisioners/local-exec.html#interpreter-examples
Related
I am currently reading the book called "Terraform-up-and-learning 2nd edition"
In the section introducing setting state file remotely, I faced a trouble.
this is the code that I ran.
terraform {
backend "s3" {
bucket = "my-state"
key = "workspaces-example/terraform.tfstate"
region = "ap-southeast-1"
dynamodb_table = "my-lock"
encrypt = true
}
}
provider "aws" {
region = "ap-southeast-1"
profile = "my-test"
}
resource "aws_instance" "example" {
ami = "ami-02045ebddb047018b"
instance_type = "t2.micro"
}
prior to running this code, I made s3 and DDB using my AWS console by hand.
And
terraform init
terraform plan
works well.
But I can't find any state file in my AWS console.
Following the book, the state file should be in "my-state" s3.
In addition, I can't find any statefile in my local too.
The state file goes to the backend after you run terraform apply.
After that, when you run terraform init again it will look for the remote state file.
In your case, your plan does show the changes list but it did not output any files. You have to apply now.
manual approval -
terraform apply
auto -
terraform apply -auto-approve
Remember to destroy after playing around to save costs. Run terraform destroy
Best wishes.
Version 4 of the AWS Provider introduces significant changes to the aws_s3_bucket:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-4-upgrade#changes-to-s3-bucket-drift-detection
From this version on, each parameter of the S3 bucket should be configured separately from the aws_s3_bucket resource configuration and re-imported into the Terraform state.
Example:
Before:
resource "aws_s3_bucket" "example" {
bucket = "yournamehere"
# ... other configuration ...
acceleration_status = "Enabled"
}
After:
resource "aws_s3_bucket" "example" {
bucket = "yournamehere"
# ... other configuration ...
}
resource "aws_s3_bucket_accelerate_configuration" "example" {
bucket = aws_s3_bucket.example.id
status = "Enabled"
}
The number of buckets I need to reconfigure exceeds 100 which will take many days of work.
Is there a solution or a tool to make the configuration conversion faster?
S3 Bucket Accelerate can be configured in either the standalone resource "aws_s3_bucket_accelerate_configuration" or with the deprecated parameter "acceleration_status" in the resource aws_s3_bucket. Configuring with both will cause inconsistencies and may overwrite configuration.
Resource: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket
I'm trying to setup a remote Terraform backend to S3. I was able to create the bucket, but I used bucket_prefix instead of bucket to define my bucket name. I did this to ensure code re-usability within my org.
My issue is that I've been having trouble referencing the new bucket in my Terraform back end config. I know that I can hard code the name of the bucket that I created, but I would like to reference the bucket similar to other resources in Terraform.
Would this be possible?
I've included my code below:
#configure terraform to use s3 as the backend
terraform {
backend "s3" {
bucket = "aws_s3_bucket.my-bucket.id"
key = "terraform/terraform.tfstate"
region = "ca-central-1"
}
}
AWS S3 Resource definition
resource "aws_s3_bucket" "my-bucket" {
bucket_prefix = var.bucket_prefix
acl = var.acl
lifecycle {
prevent_destroy = true
}
versioning {
enabled = var.versioning
}
server_side_encryption_configuration {
rule {
apply_server_side_encryption_by_default {
sse_algorithm = var.sse_algorithm
}
}
}
}
Terraform needs a valid backend configuration when the initialization steps happens (terraform init), meaning that you have to have an existing bucket before being able to provision any resources (before the first terraform apply).
If you do a terraform init with a bucket name which does not exist, you get this error:
The referenced S3 bucket must have been previously created. If the S3 bucket
│ was created within the last minute, please wait for a minute or two and try
│ again.
This is self explanatory. It is not really possible to have the S3 bucket used for backend and also defined as a Terraform resource. While certainly you can use terraform import to import an existing bucket into the state, I would NOT recommend importing the backend bucket.
Is there a way for Terraform to make changes to an existing S3 bucket without affecting the creation or deletion of the bucket?
For example, I want to use Terraform to enable S3 replication across several AWS accounts. The S3 buckets already exist, and I simply want to enable a replication rule (via a pipeline) without recreating, deleting, or emptying the bucket.
My code looks like this:
data "aws_s3_bucket" "test" {
bucket = "example_bucket"
}
data "aws_iam_role" "s3_replication" {
name = "example_role"
}
resource "aws_s3_bucket" "source" {
bucket = data.aws_s3_bucket.example_bucket.id
versioning {
enabled = true
}
replication_configuration {
role = data.aws_iam_role.example_role.arn
rules {
id = "test"
status = "Enabled"
destination {
bucket = "arn:aws:s3:::dest1"
}
}
rules {
id = "test2"
status = "Enabled"
destination {
bucket = "arn:aws:s3:::dest2"
}
}
}
}
When I try to do it this way, Terraform apply tries to delete the existing bucket and create a new one instead of just updating the configuration. I don't mind trying terraform import, but my concern is that this will destroy the bucket when I run terraform destroy as well. I would like to simply apply and destroy the replication configuration, not the already existing bucket.
I would like to simply apply and destroy the replication configuration, not the already existing bucket.
Sadly, you can't do this. Your bucket must be imported to TF so that it can be managed by it.
I don't mind trying terraform import, but my concern is that this will destroy the bucket when I run terraform destroy as well.
To protect against this, you can use prevent_destroy:
This meta-argument, when set to true, will cause Terraform to reject with an error any plan that would destroy the infrastructure object associated with the resource, as long as the argument remains present in the configuration.
I was trying to create a remote backend for my S3 bucket.
provider "aws" {
version = "1.36.0"
profile = "tasdik"
region = "ap-south-1"
}
terraform {
backend "s3" {
bucket = "ops-bucket"
key = "aws/ap-south-1/homelab/s3/terraform.tfstate"
region = "ap-south-1"
}
}
resource "aws_s3_bucket" "ops-bucket" {
bucket = "ops-bucket"
acl = "private"
versioning {
enabled = true
}
lifecycle {
prevent_destroy = true
}
tags {
Name = "ops-bucket"
Environmet = "devel"
}
}
I haven't applied anything yet, the bucket is not present as of now. So, terraform asks me to do an init. But when I try to do so, I get a
$ terraform init
Initializing the backend...
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Error loading state: BucketRegionError: incorrect region, the bucket is not in 'ap-south-1' region
status code: 301, request id: , host id:
Terraform will initialise any state configuration before any other actions such as a plan or apply. Thus you can't have the creation of the S3 bucket for your state to be stored in be defined at the same time as you defining the state backend.
Terraform also won't create an S3 bucket for you to put your state in, you must create this ahead of time.
You can either do this outside of Terraform such as with the AWS CLI:
aws s3api create-bucket --bucket "${BUCKET_NAME}" --region "${BUCKET_REGION}" \
--create-bucket-configuration LocationConstraint="${BUCKET_REGION}"
or you could create it via Terraform as you are trying to do so but use local state for creating the bucket on the first apply and then add the state configuration and re-init to get Terraform to migrate the state to your new S3 bucket.
As for the error message, S3 bucket names are globally unique across all regions and all AWS accounts. The error message is telling you that it ran the GetBucketLocation call but couldn't find a bucket in ap-south-1. When creating your buckets I recommend making sure they are likely to be unique by doing something such as concatenating the account ID and possibly the region name into the bucket name.