1 "We have identified TLS 1.0 or TLS 1.1 connections to Amazon Simple Storage Service (Amazon S3) objects hosted in your account, which must be immediately updated for these connections to maintain their access to your S3 objects. Please update your client software as soon as possible to use TLS 1.2 or higher to avoid an availability impact. We recommend considering the time needed to verify your changes in a staging environment before introducing them into production.
As of June 28, 2023, we have begun deploying updates to the TLS configuration for all AWS API endpoints to a minimum of version TLS 1.2 even if you still have connections using these versions. These deployments will complete by no later than December 31, 2023. This update removes the ability to use TLS versions 1.0 and 1.1 with all AWS APIs in all AWS Regions [1].
What actions can I take to maintain access?
To avoid potential interruption, you must update all client software accessing your Amazon S3 objects using TLS 1.0 or 1.1, to use TLS 1.2 or higher. If you are unable or would prefer to not update all impacted clients, we recommend replacing direct client access to the S3 objects with use of a proxy, such as an Amazon CloudFront distribution. This will allow clients to access your S3 objects via Amazon CloudFront using any TLS version you choose to allow. Amazon CloudFront will forward the calls to your S3 objects using TLS 1.2 or higher. For more guidance for how to setup your CloudFront distribution to front your S3 object access, please review this Knowledge Center article [2].
How can I determine the client(s) I need to update?
We have provided the affected S3 bucket(s) in your account following this messaging. In order to gather additional information about the affected objects and user agents performing these calls, we recommend enabling Amazon CloudTrail data events on the affected S3 bucket(s) [3] [4]. The information contained in the S3 data events will help you pinpoint your client software that is responsible for using TLS 1.0 or TLS 1.1, so you may update it accordingly. Additionally, our related AWS Security blog post [1] provides information on how you may use TLS information in the CloudTrail tlsDetails field. Please note there is an associated cost for enabling CloudTrail data events, please see the CloudTrail pricing page for more detail [5]. Another alternative is to use Amazon S3 server-access logs, see the S3 Logging options page for more details and pricing information [6].
How can I enforce connections to my bucket(s) be over TLSv1.2 and above?
As a best practice, and to prepare for our enforcement of TLS 1.2 or higher, we recommend you proactively enforce a minimum of TLS 1.2 directly on all of your shared S3 bucket(s). You may do this by applying a bucket policy with the s3:TlsVersion condition key as per the documented this Knowledge Center article [7].
If you need further guidance or assistance, please contact AWS Support [8] or your Technical Account Manager."
&
2
Hello,
Amazon EC2 has detected degradation of the underlying hardware hosting your EC2 instance (instance-ID: i-9ec28d0e) associated with your AWS account (AWS Account ID: 283862649416) in the us-east-1 region. This instance is scheduled for maintenance and will be rebooted any time between 2023-09-04 06:00:00 UTC and 2023-09-04 08:00:00 UTC.
The affected instance(s) are listed below:
i-9ec28d0e
What will happen to my instance during this maintenance event?
During maintenance, the instance will be rebooted. The reboot generally takes a few minutes to complete. After the reboot, your instance retains its IP address, DNS name, and any data on local instance-store volumes.
What will happen when I stop and start the instance?
You can stop and start the instance at any time before the scheduled start time of the scheduled reboot event. This will migrate the instance to a new host and the instance will not have to undergo the scheduled maintenance. Please note that the data on any local instance-store volumes will not be preserved when you stop and start your instance. For more information about stopping and starting your instance see the EC2 User Guide https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html.
If you have any questions or concerns, you can contact the AWS Support Team on the community forums and via AWS Premium Support at: https://console.aws.amazon.com/support."
Hi Brendan,
Just emailed you both of these updates from AWS:
1 "We have identified TLS 1.0 or TLS 1.1 connections to Amazon Simple Storage Service (Amazon S3) objects hosted in your account, which must be immediately updated for these connections to maintain their access to your S3 objects. Please update your client software as soon as possible to use TLS 1.2 or higher to avoid an availability impact. We recommend considering the time needed to verify your changes in a staging environment before introducing them into production.
As of June 28, 2023, we have begun deploying updates to the TLS configuration for all AWS API endpoints to a minimum of version TLS 1.2 even if you still have connections using these versions. These deployments will complete by no later than December 31, 2023. This update removes the ability to use TLS versions 1.0 and 1.1 with all AWS APIs in all AWS Regions [1].
What actions can I take to maintain access? To avoid potential interruption, you must update all client software accessing your Amazon S3 objects using TLS 1.0 or 1.1, to use TLS 1.2 or higher. If you are unable or would prefer to not update all impacted clients, we recommend replacing direct client access to the S3 objects with use of a proxy, such as an Amazon CloudFront distribution. This will allow clients to access your S3 objects via Amazon CloudFront using any TLS version you choose to allow. Amazon CloudFront will forward the calls to your S3 objects using TLS 1.2 or higher. For more guidance for how to setup your CloudFront distribution to front your S3 object access, please review this Knowledge Center article [2].
How can I determine the client(s) I need to update? We have provided the affected S3 bucket(s) in your account following this messaging. In order to gather additional information about the affected objects and user agents performing these calls, we recommend enabling Amazon CloudTrail data events on the affected S3 bucket(s) [3] [4]. The information contained in the S3 data events will help you pinpoint your client software that is responsible for using TLS 1.0 or TLS 1.1, so you may update it accordingly. Additionally, our related AWS Security blog post [1] provides information on how you may use TLS information in the CloudTrail tlsDetails field. Please note there is an associated cost for enabling CloudTrail data events, please see the CloudTrail pricing page for more detail [5]. Another alternative is to use Amazon S3 server-access logs, see the S3 Logging options page for more details and pricing information [6].
How can I enforce connections to my bucket(s) be over TLSv1.2 and above? As a best practice, and to prepare for our enforcement of TLS 1.2 or higher, we recommend you proactively enforce a minimum of TLS 1.2 directly on all of your shared S3 bucket(s). You may do this by applying a bucket policy with the s3:TlsVersion condition key as per the documented this Knowledge Center article [7].
If you need further guidance or assistance, please contact AWS Support [8] or your Technical Account Manager."
&
2
Hello,
Amazon EC2 has detected degradation of the underlying hardware hosting your EC2 instance (instance-ID: i-9ec28d0e) associated with your AWS account (AWS Account ID: 283862649416) in the us-east-1 region. This instance is scheduled for maintenance and will be rebooted any time between 2023-09-04 06:00:00 UTC and 2023-09-04 08:00:00 UTC.
The affected instance(s) are listed below: i-9ec28d0e
You can find more information on maintenance events scheduled for your EC2 instances in the AWS Management Console https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Events
You can define weekly recurring event windows for scheduled events that may occur in the future. For more information on event windows see the EC2 user guide : https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/event-windows.html You can also customize your event notification to include tags associated with your EC2 instances. For more information on customizing event notifications see the EC2 user guide : https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html#customizing_scheduled_event_notifications
During maintenance, the instance will be rebooted. The reboot generally takes a few minutes to complete. After the reboot, your instance retains its IP address, DNS name, and any data on local instance-store volumes.
What will happen when I stop and start the instance? You can stop and start the instance at any time before the scheduled start time of the scheduled reboot event. This will migrate the instance to a new host and the instance will not have to undergo the scheduled maintenance. Please note that the data on any local instance-store volumes will not be preserved when you stop and start your instance. For more information about stopping and starting your instance see the EC2 User Guide https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html.
Why does my instance require maintenance?
EC2 routinely performs maintenance on the underlying systems in order to strengthen the security, reliability and operational performance of the EC2 service for our customers. Additional information about maintenance events can be found at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html.
If you have any questions or concerns, you can contact the AWS Support Team on the community forums and via AWS Premium Support at: https://console.aws.amazon.com/support."
Thank you!