You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version updates the bucket policy to deny connections where the TLS version is below 1.2. Prior to this, non-TLS connections were denied, but now less-secure TLS versions will also be denied.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Trivy will check the following folders:
terraform/environments/performance-hub
Running Trivy in terraform/environments/performance-hub
2024-08-16T00:16:29Z INFO [db] Need to update DB
2024-08-16T00:16:29Z INFO [db] Downloading DB... repository="ghcr.io/aquasecurity/trivy-db:2"
2024-08-16T00:16:31Z INFO [vuln] Vulnerability scanning is enabled
2024-08-16T00:16:31Z INFO [misconfig] Misconfiguration scanning is enabled
2024-08-16T00:16:31Z INFO Need to update the built-in policies
2024-08-16T00:16:31Z INFO Downloading the built-in policies...
74.86 KiB / 74.86 KiB [-----------------------------------------------------------] 100.00% ? p/s 0s2024-08-16T00:16:31Z INFO [secret] Secret scanning is enabled
2024-08-16T00:16:31Z INFO [secret] If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2024-08-16T00:16:31Z INFO [secret] Please see also https://aquasecurity.github.io/trivy/v0.54/docs/scanner/secret#recommendation for faster secret detection
2024-08-16T00:16:33Z INFO Number of language-specific files num=0
2024-08-16T00:16:33Z INFO Detected config files num=11
HIGH: No public access block so not ignoring public acls
════════════════════════════════════════
S3 buckets should ignore public ACLs on buckets and any objects they contain. By ignoring rather than blocking, PUT calls with public ACLs will still be applied but the ACL will be ignored.
HIGH: No public access block so not restricting public buckets
════════════════════════════════════════
S3 buckets should restrict public policies for the bucket. By enabling, the restrict_public_buckets, only the bucket owner and AWS Services can access if it has a public policy.
CRITICAL: Security group rule allows egress to multiple public internet addresses.
════════════════════════════════════════
Opening up ports to connect out to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that are explicitly required where possible.
HIGH: Application load balancer is not set to drop invalid headers.
════════════════════════════════════════
Passing unknown or invalid headers through to the target poses a potential risk of compromise.
By setting drop_invalid_header_fields to true, anything that doe not conform to well known, defined headers will be removed by the load balancer.
HIGH: Load balancer is exposed publicly.
════════════════════════════════════════
There are many scenarios in which you would want to expose a load balancer to the wider internet, but this check exists as a warning to prevent accidental exposure of internal assets. You should ensure that this resource should be exposed publicly.
CRITICAL: Listener for application load balancer does not use HTTPS.
════════════════════════════════════════
Plain HTTP is unencrypted and human-readable. This means that if a malicious actor was to eavesdrop on your connection, they would be able to see all of your data flowing back and forth.
You should use HTTPS, which is HTTP over an encrypted (TLS) connection, meaning eavesdroppers cannot read your traffic.
CRITICAL: Security group rule allows egress to multiple public internet addresses.
════════════════════════════════════════
Opening up ports to connect out to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that are explicitly required where possible.
CRITICAL: Security group rule allows ingress from public internet.
════════════════════════════════════════
Opening up ports to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that explicitly require it where possible.
See https://avd.aquasec.com/misconfig/avd-aws-0107
────────────────────────────────────────
loadbalancer.tf:98
via loadbalancer.tf:92-99 (ingress)
via loadbalancer.tf:87-127 (aws_security_group.load_balancer_security_group)
────────────────────────────────────────
87 resource "aws_security_group" "load_balancer_security_group" {
..
98 [ cidr_blocks = ["0.0.0.0/0", ]
...
127 }
────────────────────────────────────────
CRITICAL: Security group rule allows ingress from public internet.
════════════════════════════════════════
Opening up ports to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that explicitly require it where possible.
See https://avd.aquasec.com/misconfig/avd-aws-0107
────────────────────────────────────────
loadbalancer.tf:107
via loadbalancer.tf:101-108 (ingress)
via loadbalancer.tf:87-127 (aws_security_group.load_balancer_security_group)
────────────────────────────────────────
87 resource "aws_security_group" "load_balancer_security_group" {
..
107 [ cidr_blocks = ["0.0.0.0/0", ]
...
127 }
────────────────────────────────────────
CRITICAL: Security group rule allows egress to multiple public internet addresses.
════════════════════════════════════════
Opening up ports to connect out to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that are explicitly required where possible.
See https://avd.aquasec.com/misconfig/avd-aws-0104
────────────────────────────────────────
module/ecs/main.tf:88
via module/ecs/main.tf:83-90 (content)
via module/ecs/main.tf:81-91 (dynamic.egress["cluster_ec2_lb_egress"])
via module/ecs/main.tf:64-99 (aws_security_group.cluster_ec2)
via ecs.tf:5-33 (module.windows-new-ecs)
────────────────────────────────────────
64 resource "aws_security_group" "cluster_ec2" {
..
88 [ cidr_blocks = lookup(egress.value, "cidr_blocks", null)
..
99 }
────────────────────────────────────────
HIGH: No public access block so not ignoring public acls
════════════════════════════════════════
S3 buckets should ignore public ACLs on buckets and any objects they contain. By ignoring rather than blocking, PUT calls with public ACLs will still be applied but the ACL will be ignored.
HIGH: No public access block so not restricting public buckets
════════════════════════════════════════
S3 buckets should restrict public policies for the bucket. By enabling, the restrict_public_buckets, only the bucket owner and AWS Services can access if it has a public policy.
*****************************
Setting default tflint config...
Running tflint --init...
Installing "terraform" plugin...
Installed "terraform" (source: github.com/terraform-linters/tflint-ruleset-terraform, version:0.5.0)
tflint will check the following folders:
terraform/environments/performance-hub
*****************************
Running tflint in terraform/environments/performance-hub
Excluding the following checks: terraform_unused_declarations
3issue(s) found:
Warning: [Fixable] Interpolation-only expressions are deprecated in Terraform v0.12.14 (terraform_deprecated_interpolation)
on terraform/environments/performance-hub/data.tf line 26:26:storage_bucket="${aws_s3_bucket.upload_files.id}"
Reference: https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.5.0/docs/rules/terraform_deprecated_interpolation.md
Warning: Missing version constraint for provider "template" in `required_providers` (terraform_required_providers)
on terraform/environments/performance-hub/db_manager.tf line 51:51:data"template_cloudinit_config""cloudinit-db-mgmt" {
Reference: https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.5.0/docs/rules/terraform_required_providers.md
Warning: Missing version constraint for provider "random" in `required_providers` (terraform_required_providers)
on terraform/environments/performance-hub/secrets.tf line 5:5:resource"random_password""random_password" {
Reference: https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.5.0/docs/rules/terraform_required_providers.mdtflint_exitcode=2
Trivy Scan Failed
Show Output
*****************************
Trivy will check the following folders:
terraform/environments/performance-hub
*****************************
Running Trivy in terraform/environments/performance-hub
2024-08-16T00:16:29Z INFO [db] Need to update DB
2024-08-16T00:16:29Z INFO [db] Downloading DB...repository="ghcr.io/aquasecurity/trivy-db:2"2024-08-16T00:16:31Z INFO [vuln] Vulnerability scanning is enabled
2024-08-16T00:16:31Z INFO [misconfig] Misconfiguration scanning is enabled
2024-08-16T00:16:31Z INFO Need to update the built-in policies
2024-08-16T00:16:31Z INFO Downloading the built-in policies...74.86 KiB /74.86 KiB [-----------------------------------------------------------] 100.00%? p/s 0s2024-08-16T00:16:31Z INFO [secret] Secret scanning is enabled
2024-08-16T00:16:31Z INFO [secret] If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2024-08-16T00:16:31Z INFO [secret] Please see also https://aquasecurity.github.io/trivy/v0.54/docs/scanner/secret#recommendation for faster secret detection2024-08-16T00:16:33Z INFO Number of language-specific files num=02024-08-16T00:16:33Z INFO Detected config files num=11
database.tf (terraform)
=======================
Tests:16 (SUCCESSES:11, FAILURES:4, EXCEPTIONS:1)
Failures:4 (HIGH:4, CRITICAL:0)
HIGH: No public access block so not blocking public acls
════════════════════════════════════════
S3 buckets should block public ACLs on buckets and any objects they contain. By blocking, PUTs with fail if the object has any public ACL a.
See https://avd.aquasec.com/misconfig/avd-aws-0086
────────────────────────────────────────
database.tf:171-187
────────────────────────────────────────
171 ┌ resource"aws_s3_bucket""database_backup_files" {
172 │ #checkov:skip=CKV_AWS_18173 │ #checkov:skip=CKV_AWS_144174 │ #checkov:skip=CKV2_AWS_6175 │ bucket="${local.application_name}-db-backups-${local.environment}"176 │
177 │ lifecycle {
178 │ prevent_destroy=true179 └ }
...
────────────────────────────────────────
HIGH: No public access block so not blocking public policies
════════════════════════════════════════
S3 bucket policy should have block public policy to prevent users from putting a policy that enable public access.
See https://avd.aquasec.com/misconfig/avd-aws-0087
────────────────────────────────────────
database.tf:171-187
────────────────────────────────────────
171 ┌ resource"aws_s3_bucket""database_backup_files" {
172 │ #checkov:skip=CKV_AWS_18173 │ #checkov:skip=CKV_AWS_144174 │ #checkov:skip=CKV2_AWS_6175 │ bucket="${local.application_name}-db-backups-${local.environment}"176 │
177 │ lifecycle {
178 │ prevent_destroy=true179 └ }
...
────────────────────────────────────────
HIGH: No public access block so not ignoring public acls
════════════════════════════════════════
S3 buckets should ignore public ACLs on buckets and any objects they contain. By ignoring rather than blocking, PUT calls with public ACLs will still be applied but the ACL will be ignored.
See https://avd.aquasec.com/misconfig/avd-aws-0091
────────────────────────────────────────
database.tf:171-187
────────────────────────────────────────
171 ┌ resource"aws_s3_bucket""database_backup_files" {
172 │ #checkov:skip=CKV_AWS_18173 │ #checkov:skip=CKV_AWS_144174 │ #checkov:skip=CKV2_AWS_6175 │ bucket="${local.application_name}-db-backups-${local.environment}"176 │
177 │ lifecycle {
178 │ prevent_destroy=true179 └ }
...
────────────────────────────────────────
HIGH: No public access block so not restricting public buckets
════════════════════════════════════════
S3 buckets should restrict public policies for the bucket. By enabling, the restrict_public_buckets, only the bucket owner and AWS Services can access if it has a public policy.
See https://avd.aquasec.com/misconfig/avd-aws-0093
────────────────────────────────────────
database.tf:171-187
────────────────────────────────────────
171 ┌ resource"aws_s3_bucket""database_backup_files" {
172 │ #checkov:skip=CKV_AWS_18173 │ #checkov:skip=CKV_AWS_144174 │ #checkov:skip=CKV2_AWS_6175 │ bucket="${local.application_name}-db-backups-${local.environment}"176 │
177 │ lifecycle {
178 │ prevent_destroy=true179 └ }
...
────────────────────────────────────────
db_manager.tf (terraform)
=========================
Tests:2 (SUCCESSES:1, FAILURES:1, EXCEPTIONS:0)
Failures:1 (HIGH:0, CRITICAL:1)
CRITICAL: Security group rule allows egress to multiple public internet addresses.
════════════════════════════════════════
Opening up ports to connect out to the public internet is generally to be avoided. You should restrict access to IP addresses or ranges that are explicitly required where possible.
See https://avd.aquasec.com/misconfig/avd-aws-0104
────────────────────────────────────────
db_manager.tf:147-149
via db_manager.tf:141-150 (egress)
via db_manager.tf:128-158 (aws_security_group.db_mgmt_server_security_group)
────────────────────────────────────────
128resource"aws_security_group""db_mgmt_server_security_group" {
...147 ┌ cidr_blocks=[
148 │ "0.0.0.0/0",
149 └ ]
...158 }
────────────────────────────────────────
loadbalancer.tf (terraform)
===========================
Tests:9 (SUCCESSES:3, FAILURES:6, EXCEPTIONS:0)
Failures:6 (HIGH:2, CRITICAL:4)
HIGH: Application load balancer is not set to drop invalid headers.
════════════════════════════════════════
Passing unknown or invalid headers through to the target poses a potential risk of compromise.
By setting drop_invalid_header_fields to true, anything that doe not conform to well known, defined headers will be removed by the load balancer.
See https://avd.aquasec.com/misconfig/avd-aws-0052
────────────────────────────────────────
loadbalancer.tf:5-25
────────────────────────────────────────
5 ┌ resource"aws_lb""external" {
6 │ #checkov:skip=CKV_AWS_917 │ #checkov:skip=CKV_AWS_1318 │ #checkov:skip=CKV2_AWS_209 │ #checkov:skip=CKV2_AWS_2810 │ name="${local.application_name}-loadbalancer"11 │ load_balancer_type="application"12 │ subnets=data.aws_subnets.shared-public.ids13 └ enable_deletion_protection=true..
────────────────────────────────────────
HIGH: Load balancer is exposed publicly.
════════════════════════════════════════
There are many scenarios in which you would want to expose a load balancer to the wider internet, but this check exists as a warning to prevent accidental exposure of internal assets. You should ensure that this resource should be exposed publicly.
See https://avd.aquasec.com/misconfig/avd-aws-0053
────────────────────────────────────────
loadbalancer.tf:5-25
────────────────────────────────────────
5 ┌ resource"aws_lb""external" {
6 │ #checkov:skip=CKV_AWS_917 │ #checkov:skip=CKV_AWS_1318 │ #checkov:skip=CKV2_AWS_209 │ #checkov:skip=CKV2_AWS_2810 │ name="${local.application_name}-loadbalancer"11 │ load_balancer_type="application"12 │ subnets=data.aws_subnets.shared-public.ids13 └ enable_deletion_protection=true..
────────────────────────────────────────
CRITICAL: Listener for application load balancer does not use HTTPS.
════════════════════════════════════════
Plain HTTP is unencrypted and human-readable. This means that if a malicious actor was to eavesdrop on your connection, they would be able to see all of your data flowing back and forth.
You should use HTTPS, which is HTTP over an encrypted (TLS) connection, meaning eavesdroppers cannot read your traffic.
See https://avd.aquasec.com/misconfig/avd-aws-0054
────────────────────────────────────────
loadbalancer.tf:63
via loadbalancer.tf:58-69 (aws_lb_listener.listener)
────────────────────────────────────────
58resource"aws_lb_listener""listener" {
..63 [ protocol = "HTTP"..69 }
────────────────────────────────────────
CRITICAL:Securitygroupruleallowsegresstomultiplepublicinternetaddresses.
════════════════════════════════════════
Openingupportstoconnectouttothepublicinternetisgenerallytobeavoided.YoushouldrestrictaccesstoIPaddressesorrangesthatareexplicitlyrequiredwherepossible.Seehttps://avd.aquasec.com/misconfig/avd-aws-0104
────────────────────────────────────────
loadbalancer.tf:116-118vialoadbalancer.tf:110-119 (egress)
vialoadbalancer.tf:87-127 (aws_security_group.load_balancer_security_group)
────────────────────────────────────────
87resource"aws_security_group""load_balancer_security_group" {
..
116 ┌ cidr_blocks = [
117 │ "0.0.0.0/0",
118 └ ]
...127 }
────────────────────────────────────────
CRITICAL:Securitygroupruleallowsingressfrompublicinternet.
════════════════════════════════════════
Openingupportstothepublicinternetisgenerallytobeavoided.YoushouldrestrictaccesstoIPaddressesorrangesthatexplicitlyrequireitwherepossible.Seehttps://avd.aquasec.com/misconfig/avd-aws-0107
────────────────────────────────────────
loadbalancer.tf:98vialoadbalancer.tf:92-99 (ingress)
vialoadbalancer.tf:87-127 (aws_security_group.load_balancer_security_group)
────────────────────────────────────────
87resource"aws_security_group""load_balancer_security_group" {
..
98 [ cidr_blocks = ["0.0.0.0/0", ]
...127 }
────────────────────────────────────────
CRITICAL:Securitygroupruleallowsingressfrompublicinternet.
════════════════════════════════════════
Openingupportstothepublicinternetisgenerallytobeavoided.YoushouldrestrictaccesstoIPaddressesorrangesthatexplicitlyrequireitwherepossible.Seehttps://avd.aquasec.com/misconfig/avd-aws-0107
────────────────────────────────────────
loadbalancer.tf:107vialoadbalancer.tf:101-108 (ingress)
vialoadbalancer.tf:87-127 (aws_security_group.load_balancer_security_group)
────────────────────────────────────────
87resource"aws_security_group""load_balancer_security_group" {
..
107 [ cidr_blocks = ["0.0.0.0/0", ]
...127 }
────────────────────────────────────────
module/ecs/main.tf (terraform)
==============================Tests:64 (SUCCESSES:6, FAILURES:1, EXCEPTIONS:57)
Failures:1 (HIGH:0, CRITICAL:1)
CRITICAL:Securitygroupruleallowsegresstomultiplepublicinternetaddresses.
════════════════════════════════════════
Openingupportstoconnectouttothepublicinternetisgenerallytobeavoided.YoushouldrestrictaccesstoIPaddressesorrangesthatareexplicitlyrequiredwherepossible.Seehttps://avd.aquasec.com/misconfig/avd-aws-0104
────────────────────────────────────────
module/ecs/main.tf:88viamodule/ecs/main.tf:83-90 (content)
viamodule/ecs/main.tf:81-91 (dynamic.egress["cluster_ec2_lb_egress"])
viamodule/ecs/main.tf:64-99 (aws_security_group.cluster_ec2)
viaecs.tf:5-33 (module.windows-new-ecs)
────────────────────────────────────────
64resource"aws_security_group""cluster_ec2" {
..
88 [ cidr_blocks =lookup(egress.value, "cidr_blocks", null)
..
99 }
────────────────────────────────────────
monitoring.tf (terraform)
=========================
Tests:2 (SUCCESSES:1, FAILURES:1, EXCEPTIONS:0)
Failures:1 (HIGH:1, CRITICAL:0)
HIGH:Topicdoesnothaveencryptionenabled.
════════════════════════════════════════
Topicsshouldbeencryptedtoprotecttheircontents.Seehttps://avd.aquasec.com/misconfig/avd-aws-0095
────────────────────────────────────────
monitoring.tf:21-23
────────────────────────────────────────
21 ┌ resource"aws_sns_topic""ddos_alarm" {
22 │ name ="ddos_alarm"23 └ }
────────────────────────────────────────
s3.tf (terraform)
=================
Tests:11 (SUCCESSES:3, FAILURES:4, EXCEPTIONS:4)
Failures:4 (HIGH:4, CRITICAL:0)
HIGH:Nopublicaccessblocksonotblockingpublicacls
════════════════════════════════════════
S3bucketsshouldblockpublicACLsonbucketsandanyobjectstheycontain.Byblocking, PUTswithfailiftheobjecthasanypublicACLa.Seehttps://avd.aquasec.com/misconfig/avd-aws-0086
────────────────────────────────────────
s3.tf:7-23
────────────────────────────────────────
7 ┌ resource"aws_s3_bucket""upload_files" {
8 │ #checkov:skip=CKV_AWS_189 │ #checkov:skip=CKV_AWS_14410 │ #checkov:skip=CKV2_AWS_611 │ bucket ="${local.application_name}-uploads-${local.environment}"12 │
13 │ lifecycle {
14 │ prevent_destroy =true15 └ }
..
────────────────────────────────────────
HIGH: No public access block so not blocking public policies
════════════════════════════════════════
S3 bucket policy should have block public policy to prevent users from putting a policy that enable public access.
See https://avd.aquasec.com/misconfig/avd-aws-0087
────────────────────────────────────────
s3.tf:7-23
────────────────────────────────────────
7 ┌ resource "aws_s3_bucket""upload_files" {
8 │ #checkov:skip=CKV_AWS_189 │ #checkov:skip=CKV_AWS_14410 │ #checkov:skip=CKV2_AWS_611 │ bucket ="${local.application_name}-uploads-${local.environment}"12 │
13 │ lifecycle {
14 │ prevent_destroy =true15 └ }
..
────────────────────────────────────────
HIGH: No public access block so not ignoring public acls
════════════════════════════════════════
S3 buckets should ignore public ACLs on buckets and any objects they contain. By ignoring rather than blocking, PUT calls with public ACLs will still be applied but the ACL will be ignored.
See https://avd.aquasec.com/misconfig/avd-aws-0091
────────────────────────────────────────
s3.tf:7-23
────────────────────────────────────────
7 ┌ resource "aws_s3_bucket""upload_files" {
8 │ #checkov:skip=CKV_AWS_189 │ #checkov:skip=CKV_AWS_14410 │ #checkov:skip=CKV2_AWS_611 │ bucket ="${local.application_name}-uploads-${local.environment}"12 │
13 │ lifecycle {
14 │ prevent_destroy =true15 └ }
..
────────────────────────────────────────
HIGH: No public access block so not restricting public buckets
════════════════════════════════════════
S3 buckets should restrict public policies forthebucket.Byenabling, therestrict_public_buckets, onlythebucketownerandAWSServicescanaccessifithasapublicpolicy.
See https://avd.aquasec.com/misconfig/avd-aws-0093
────────────────────────────────────────
s3.tf:7-23
────────────────────────────────────────
7 ┌ resource "aws_s3_bucket""upload_files" {
8 │ #checkov:skip=CKV_AWS_189 │ #checkov:skip=CKV_AWS_14410 │ #checkov:skip=CKV2_AWS_611 │ bucket ="${local.application_name}-uploads-${local.environment}"12 │
13 │ lifecycle {
14 │ prevent_destroy =true15 └ }
..
────────────────────────────────────────
trivy_exitcode=1
dependabotbot
deleted the
dependabot/terraform/terraform/environments/performance-hub/ap_landing_bucket--github--ministryofjustice/modernisation-platform-terraform-s3-bucket--v7.1.0-8.1.0
branch
September 18, 2024 00:36
dependenciesPull requests that update a dependency fileenvironments-repositoryUsed to exclude PRs from this repo in our Slack PR updateterraformPull requests that update Terraform code
0 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
github-actions
bot
added
the
environments-repository
Bumps ap_landing_bucket::modernisation-platform-terraform-s3-bucket from 7.1.0 to 8.1.0.
Release notes
Sourced from ap_landing_bucket::modernisation-platform-terraform-s3-bucket's releases.
... (truncated)
Commits
4e17731Merge pull request #510 from ministryofjustice/dependabot/github_actions/brid...8431e01Merge pull request #509 from ministryofjustice/dependabot/github_actions/gith...6c10893Merge pull request #511 from ministryofjustice/enforce_tls_12_or_highereb12580Commit changes made by code formatterse810ef3Revise bucket policy to enforce tls v1.2 or higher connectionsde70f45Bump bridgecrewio/checkov-action from 12.2849.0 to 12.2851.0df49d9dBump github/codeql-action from 3.26.1 to 3.26.2f95c656Merge pull request #508 from ministryofjustice/dependabot/github_actions/gith...85eb05bBump github/codeql-action from 3.26.0 to 3.26.1ae42a20Merge pull request #507 from ministryofjustice/dependabot/github_actions/brid...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)