Size: a a a

2020 December 18

LB

Let Eat Bee in AWS_RU
L K
ребят, есть вопрос по пушу логов с ec2 у CloudWatch
как я вижу CloudWatch агент ставится на ec2 и шлет логи с файла у который пишутся логи.
Вопрос, этот же файл с логами надо ротировать ? нету же такого функционала у CloudWatch
ну типа все это выглядит костыльно по мне
если уже есть сборщик логов, то они могут поддерживать cloudwatch, так что ничего нового ставить не надо: https://docs.fluentbit.io/manual/pipeline/outputs/cloudwatch
источник

DZ

Dmitriy Zaytsev in AWS_RU
Karen Tovmasyan
А данных не стало больше?
Неа
источник

KT

Karen Tovmasyan in AWS_RU
Сделай фильтр по UsageType - ChargedBackupUsage и группируй по ресурсам
источник

KT

Karen Tovmasyan in AWS_RU
Возможно что-то не видишь
источник

DZ

Dmitriy Zaytsev in AWS_RU
Karen Tovmasyan
Сделай фильтр по UsageType - ChargedBackupUsage и группируй по ресурсам
Там просто растёт каждый ресурс.
источник

DZ

Dmitriy Zaytsev in AWS_RU
По 1-2 бакса в день, но их несколько и в месячной перспективе оно мне дороже сильно, чем обычно встаёт. Не понимаю причин.
источник

DZ

Dmitriy Zaytsev in AWS_RU
По детальному биллингу тоже ничего полезного не нашёл. Выключу все бекапы на выходные, видимо. Посмотрим как среагирует.
источник

KT

Karen Tovmasyan in AWS_RU
Dmitriy Zaytsev
По детальному биллингу тоже ничего полезного не нашёл. Выключу все бекапы на выходные, видимо. Посмотрим как среагирует.
Напиши в суппорт лучше
источник

KT

Karen Tovmasyan in AWS_RU
Пусть объяснят косты (они это делают)
источник

DZ

Dmitriy Zaytsev in AWS_RU
Karen Tovmasyan
Напиши в суппорт лучше
М. Тож хорошо 👍
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Load Balancing
Region: 🇰🇷Asia Pacific (Seoul)
URL: http://status.aws.amazon.com/#elb-ap-northeast-2_1608306650

We are investigating network connectivity issues for Network Load Balancers using TLS within a single Availability Zone (APNE2-AZ1) in the AP-NORTHEAST-2 Region. Network Load Balancers configured for multiple Availability Zones will automatically fail away from the affected Availability Zone, mitigating any impact. For Network Load Balancers configured for only the affected Availability Zone, customers can create a replacement Network Load Balancer in another Availability Zone to mitigate the issue until it is fully resolved. If you have any questions or are experiencing any operational issue, please contact the AWS Support department via the AWS Support Center at https://console.aws.amazon.com/support

#elb #apnortheast2
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Load Balancing
Region: 🇰🇷Asia Pacific (Seoul)
URL: http://status.aws.amazon.com/#elb-ap-northeast-2_1608307716

We are seeing signs of recovery for the network connectivity issues for Network Load Balancers using TLS within a single Availability Zone (APNE2-AZ1) in the AP-NORTHEAST-2 Region. We continue to work towards full recovery. If you have any questions or are experiencing any operational issue, please contact the AWS Support department via the AWS Support Center at https://console.aws.amazon.com/support

#elb #apnortheast2
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Load Balancing
Region: 🇰🇷Asia Pacific (Seoul)
URL: http://status.aws.amazon.com/#elb-ap-northeast-2_1608310799

We have resolved the issue affecting network connectivity issues for Network Load Balancers using TLS within a single Availability Zone (APNE2-AZ1) in the AP-NORTHEAST-2 Region. Starting at 12:30 AM PST, some Network Load Balancers within the AP-NORTHEAST-2 Region experienced periods of network connectivity issues. At 7:13 AM, Network Load Balancers within a single Availability Zone (APNE2-AZ1) experienced connectivity issues for TLS connections. At 7:56 AM PST, all connectivity issues for Network Load Balancers within the AP-NORTHEAST-2 Region were resolved. The issue has been resolved and the service is operating normally. Customers do not need to take additional measures to restore the availability of this service. If you have any questions or are experiencing any operational issue, please contact the AWS Support department via the AWS Support Center at https://console.aws.amazon.com/support .

#elb #apnortheast2
источник

☁️ AWStatus in AWS_RU
Service: AWS NAT Gateway
Region: 🇰🇷Asia Pacific (Seoul)
URL: http://status.aws.amazon.com/#natgateway-ap-northeast-2_1608318576

태평양시간 오전12:30 (한국시간 오후 5:30) 에서 오전7:10 (한국시간 오전 12:10) 사이에 AP-NORTHEAST-2 리전 내에서 NAT 게이트웨이에 대한 네트워크 연결 문제가 발생합니다. 문제가 해결되었으며 서비스가 정상적으로 작동하고 있습니다. 고객분들은 서비스의 가용률을 복원하기 위한 추가 조치를 취할 필요가 없습니다. 이와 관련하여 질문이나 운영관련 문제를 겪고 있으시다면 https://console.aws.amazon.com/support AWS 지원 센터를 통해 AWS 지원 부서에 문의하십시오. | Between 12:30 AM and 7:10 AM PST we experience periods of network connectivity issues for NAT Gateway within the AP-NORTHEAST-2 Region. The issue has been resolved and the service is operating normally. Customers do not need to take additional measures to restore the availability of this service. If you have any questions or are experiencing any operational issue, please contact the AWS Support department via the AWS Support Center at https://console.aws.amazon.com/support .

#natgateway #apnortheast2
источник

АП

Агент Печенька... in AWS_RU
☁️ AWStatus
Service: AWS NAT Gateway
Region: 🇰🇷Asia Pacific (Seoul)
URL: http://status.aws.amazon.com/#natgateway-ap-northeast-2_1608318576

태평양시간 오전12:30 (한국시간 오후 5:30) 에서 오전7:10 (한국시간 오전 12:10) 사이에 AP-NORTHEAST-2 리전 내에서 NAT 게이트웨이에 대한 네트워크 연결 문제가 발생합니다. 문제가 해결되었으며 서비스가 정상적으로 작동하고 있습니다. 고객분들은 서비스의 가용률을 복원하기 위한 추가 조치를 취할 필요가 없습니다. 이와 관련하여 질문이나 운영관련 문제를 겪고 있으시다면 https://console.aws.amazon.com/support AWS 지원 센터를 통해 AWS 지원 부서에 문의하십시오. | Between 12:30 AM and 7:10 AM PST we experience periods of network connectivity issues for NAT Gateway within the AP-NORTHEAST-2 Region. The issue has been resolved and the service is operating normally. Customers do not need to take additional measures to restore the availability of this service. If you have any questions or are experiencing any operational issue, please contact the AWS Support department via the AWS Support Center at https://console.aws.amazon.com/support .

#natgateway #apnortheast2
Ясно понятно.
источник
2020 December 19

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1608329628

We are investigating connectivity issues affecting NAT Gateway in a single Availability Zone (use1-az1) in the US-EAST-1 Region.

#ec2 #useast1
источник

☁️ AWStatus in AWS_RU
Service: AWS VPCE PrivateLink
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#privatelink-us-east-1_1608329932

We are investigating connectivity issues affecting VPCE PrivateLink Endpoints in a single Availability Zone (use1-az1) in the US-EAST-1 Region.

#privatelink #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1608331345

We are investigating connectivity issues affecting Network Load Balancers in a single Availability Zone (use1-az1) in US-EAST-1 Region.

#elb #useast1
источник

AS

Alexey Stekov in AWS_RU
Етить
источник

VS

Vladimir Samoylov in AWS_RU
Ну хоть сработала multi-az:)
источник