Amazon Lightsail Update: This release adds support to enable access logging for buckets in the Lightsail object storage service.

Author: AWS

.changes/next-release/feature-AmazonLightsail-f530afc.json

@@ -0,0 +1,6 @@
+{
+    "type": "feature",
+    "category": "Amazon Lightsail",
+    "contributor": "",
+    "description": "This release adds support to enable access logging for buckets in the Lightsail object storage service."
+}

services/lightsail/src/main/resources/codegen-resources/service-2.json

@@ -3463,10 +3463,39 @@
         "state":{
           "shape":"BucketState",
           "documentation":"<p>An object that describes the state of the bucket.</p>"
+        },
+        "accessLogConfig":{
+          "shape":"BucketAccessLogConfig",
+          "documentation":"<p>An object that describes the access log configuration for the bucket.</p>"
         }
       },
       "documentation":"<p>Describes an Amazon Lightsail bucket.</p>"
     },
+    "BucketAccessLogConfig":{
+      "type":"structure",
+      "required":["enabled"],
+      "members":{
+        "enabled":{
+          "shape":"boolean",
+          "documentation":"<p>A Boolean value that indicates whether bucket access logging is enabled for the bucket.</p>"
+        },
+        "destination":{
+          "shape":"BucketName",
+          "documentation":"<p>The name of the bucket where the access is saved. The destination can be a Lightsail bucket in the same account, and in the same AWS Region as the source bucket.</p> <note> <p>This parameter is required when enabling the access log for a bucket, and should be omitted when disabling the access log.</p> </note>"
+        },
+        "prefix":{
+          "shape":"BucketAccessLogPrefix",
+          "documentation":"<p>The optional object prefix for the bucket access log.</p> <p>The prefix is an optional addition to the object key that organizes your access log files in the destination bucket. For example, if you specify a <code>logs/</code> prefix, then each log object will begin with the <code>logs/</code> prefix in its key (for example, <code>logs/2021-11-01-21-32-16-E568B2907131C0C0</code>).</p> <note> <p>This parameter can be optionally specified when enabling the access log for a bucket, and should be omitted when disabling the access log.</p> </note>"
+        }
+      },
+      "documentation":"<p>Describes the access log configuration for a bucket in the Amazon Lightsail object storage service.</p> <p>For more information about bucket access logs, see <a href=\"https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-bucket-access-logs\">Logging bucket requests using access logging in Amazon Lightsail</a> in the <i>Amazon Lightsail Developer Guide</i>.</p>"
+    },
+    "BucketAccessLogPrefix":{
+      "type":"string",
+      "max":100,
+      "min":1,
+      "pattern":"^[\\w/!.*')(-]+$"
+    },
     "BucketBundle":{
       "type":"structure",
       "members":{
@@ -3963,7 +3992,7 @@
       "members":{
         "image":{
           "shape":"string",
-          "documentation":"<p>The name of the image used for the container.</p> <p>Container images sourced from your Lightsail container service, that are registered and stored on your service, start with a colon (<code>:</code>). For example, <code>:container-service-1.mystaticwebsite.1</code>. Container images sourced from a public registry like Docker Hub don't start with a colon. For example, <code>nginx:latest</code> or <code>nginx</code>.</p>"
+          "documentation":"<p>The name of the image used for the container.</p> <p>Container images sourced from your Lightsail container service, that are registered and stored on your service, start with a colon (<code>:</code>). For example, if your container service name is <code>container-service-1</code>, the container image label is <code>mystaticsite</code>, and you want to use the third (<code>3</code>) version of the registered container image, then you should specify <code>:container-service-1.mystaticsite.3</code>. To use the latest version of a container image, specify <code>latest</code> instead of a version number (for example, <code>:container-service-1.mystaticsite.latest</code>). Lightsail will automatically use the highest numbered version of the registered container image.</p> <p>Container images sourced from a public registry like Docker Hub don't start with a colon. For example, <code>nginx:latest</code> or <code>nginx</code>.</p>"
         },
         "command":{
           "shape":"StringList",
@@ -4644,7 +4673,7 @@
         },
         "tags":{
           "shape":"TagList",
-          "documentation":"<p>The tag keys and optional values to add to the certificate during create.</p> <p>Use the <code>TagResource</code> action to tag a resource after it's created.</p> <p>For more information about tags in Lightsail, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-tags\">Amazon Lightsail Developer Guide</a>.</p>"
+          "documentation":"<p>The tag keys and optional values to add to the container service during create.</p> <p>Use the <code>TagResource</code> action to tag a resource after it's created.</p> <p>For more information about tags in Lightsail, see the <a href=\"https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-tags\">Amazon Lightsail Developer Guide</a>.</p>"
         },
         "publicDomainNames":{
           "shape":"ContainerServicePublicDomains",
@@ -10987,6 +11016,10 @@
         "readonlyAccessAccounts":{
           "shape":"PartnerIdList",
           "documentation":"<p>An array of strings to specify the AWS account IDs that can access the bucket.</p> <p>You can give a maximum of 10 AWS accounts access to a bucket.</p>"
+        },
+        "accessLogConfig":{
+          "shape":"BucketAccessLogConfig",
+          "documentation":"<p>An object that describes the access log configuration for the bucket.</p>"
         }
       }
     },