Ну архитект про в принципе интересный

А спешалти - секьюрити самый простой, мл есс-но требует знания мл, нетворкинг - я хз. Я целился в бывшую бигдату, но я там уже слишком много трогал чтобы было интересно

Я на следующей неделе про нетворкинг расскажу

Service: AWS Internet Connectivity
Region: 🇧🇷South America (São Paulo)
URL: http://status.aws.amazon.com/#internetconnectivity-sa-east-1_1636421771

We are investigating internet connectivity issues within the SA-EAST-1 Region. This is affecting connectivity into the SA-EAST-1 Region but also causing increased error rates and latencies for AWS service APIs within the region.

#internetconnectivity #saeast1

Service: AWS Internet Connectivity
Region: 🇧🇷South America (São Paulo)
URL: http://status.aws.amazon.com/#internetconnectivity-sa-east-1_1636422693

Between 5:15 PM and 5:41 PM PST we experienced Internet connectivity issues for a single Availability Zone (sae1-az1) within the SA-EAST-1 Region. Some AWS services also experienced increased error rates and latencies during this time. The issue has been resolved and the service is operating normally.

#internetconnectivity #saeast1

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636495106

We are investigating increased 5xx error rates and latencies for requests to the Amazon S3 APIs in the US-EAST-1 Region. Where possible, we recommend that requests that fail with a 5xx error be retried.

#s3 #usstandard

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1636496591

We are investigating cluster reboots and degraded performance for Redshift Clusters in the US-EAST-1 Region.

#redshift #useast1

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636498122

We have identified the S3 subsystem responsible for increased 5xx error rates for the S3 PUT APIs, and are working to isolate the root cause within this subsystem. Customers may also be experiencing increased latency when performing PUT operations. During this time, we recommend customers retry any failed requests.

#s3 #usstandard

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1636501654

We continue to investigate cluster reboots and degraded performance for Redshift RA3 Clusters in the US-EAST-1 Region. The cluster reboots are being triggered by writes that are being impacted by the elevated S3 put latencies. Redshift attempts to retry these writes automatically but if they are unsuccessful after extended attempts, the cluster may restart. If you are able to pause write workloads while we work towards resolving the S3 put latency issue, your clusters will no longer restart and can serve read queries normally.

#redshift #useast1

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636502963

We are continuing to see increased 5xx error rates and latencies for S3 API requests, in particular S3 PUT API calls. We have narrowed down the root cause to a specific sub-system within S3 and continue to make progress in mitigating the impact to this service but have not yet seen significant improvement. S3 API error rates and latencies have stayed a consistent low level with the vast majority of request retries succeeding. While the vast majority of requests are being processed within the normal latency levels, request tail latencies are exceeding 1 second in some cases. In some applications, increasing client timeouts may also help to mitigate the issue.

#s3 #usstandard

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636505546

We are starting to see some improvement in the 5xx error rates and latencies for S3 API requests, in particular S3 PUT API calls. The issue affected a subsystem stores routing metadata used by Amazon S3 to map API requests to the storage nodes. A recent update caused increased load within this subsystem, which led to increased error rates and latencies for the S3 APIs. We have now successfully mitigated this increased load within this subsystem and are seeing early signs of recovery. As the sub-system processes the backlog of requests, S3 API error rates and latencies will continue to improve.

#s3 #usstandard

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1636505587

We have identified and continue to work on mitigating the root cause of the Redshift RA3 Clusters reboots and degraded performance in the US-EAST-1 Region. The cluster reboots are triggered by Redshift writes to S3 that have been impacted by the elevated S3 PUT API latencies. If you are impacted and able to pause Redshift write workloads on your RA3 clusters while we work towards recovery, your clusters will no longer restart and can serve read queries normally. As S3 API error rates and latencies continue to improve, we expect Redshift RA3 cluster restarts to decline as well.

#redshift #useast1

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636509189

We continue to see a gradual improvement in error rates as we process the backlog of mappings between request metadata and data storage in the sub-system affected by the increased load. We are currently working on mitigations to speed up the processing of the backlog during this event. Once the backlog is resolved, we expect that the error rate will fully recover. The vast majority of requests to S3 APIs continue to operate normally.

#s3 #usstandard

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636513138

We continue to process the backlog of mappings between request metadata and data storage in the sub-system affected by the increased load. We have implemented two parallel mitigations to improve the speed of processing. Both mitigations are in process of deployment. Once the backlog is resolved, we expect that the error rate will fully recover. The vast majority of requests to S3 APIs continue to operate normally.

#s3 #usstandard

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1636514355

While the S3 API error rates and latencies continue to hold steady, we continue to see a low rate of Redshift RA3 Cluster restarts. While we continue to take steps to mitigate and reduce the risk of a restart for affected Redshift clusters, we expect to see full recovery when the S3 error rates and latencies have fully recovered. Please refer to the S3 Service Health Dashboard updates for progress towards recovery.

#redshift #useast1

Service: Amazon Redshift
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#redshift-us-east-1_1636516052

As S3 has completed their mitigation and is operating normally, Redshift RA3 clusters are seeing writes succeed and clusters are no longer rebooting. For the vast majority of customers the issue has been resolved and the service is operating normally. We continue to work with a small number of impacted customers individually to recover their clusters and will reach out via the AWS Personal Health Dashboard and AWS Support.

#redshift #useast1

Service: Amazon Simple Storage Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#s3-us-standard_1636516284

We have completed the mitigation to accelerate processing of the mappings between S3 API request metadata and storage. The backlog has been fully processed and S3 API errors and latencies have returned to normal levels. The issue has been resolved and the service is operating normally.

#s3 #usstandard

что это?

Спам обыкновенный

ааа,  жаль, думал денег заработать