Urgent.News

What's breaking now, across thousands of outlets.

Tech

AWS Shared Responsibility Model Who Takes Care of What in the Cloud

Boa parte dos incidentes de segurança na nuvem não acontece porque a AWS falhou — acontece porque alguém assumiu, incorretamente, que a AWS cuidaria de algo que na verdade era responsabilidade do cliente. O Shared Responsibility Model (Modelo de Responsabilidade Compartilhada) é o framework que a AWS usa para deixar essa linha explícita, e é provavelmente o conceito de segurança mais citado — e…

Translated from Portuguese Read in Portuguese

The article discusses the Shared Responsibility Model used by AWS, which defines the security responsibilities of both AWS and its clients. The model is often misunderstood, leading to security incidents in the cloud. AWS is responsible for the security "of" the cloud, including infrastructure, hardware, and virtualization, while clients are responsible for security "in" the cloud, including data, identity and access management, and application configuration.

The division of responsibility varies depending on the type of service used, such as IaaS, PaaS, or SaaS, with clients assuming more responsibility in IaaS scenarios like Amazon EC2 and less in managed services like Amazon RDS.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Three things I got wrong measuring my own cache

A team that produces regulatory documents kept getting the same kind of question from other teams: does the current rule allow X?

  • Overlooked issue with negation pairs, labeling error not caught by testing
  • Control group too easy, minimal token differences between accept/reject pairs
  • Misinterpreted embedder failure as semantics issue, not surface form understanding

Backtesting overfitting: why your backtest lies and how to make it honest

Cross-post. Original: stellarbytecapital.com/blog/backtesting-overfitting A profitable backtest is the easiest thing to produce in all of quant trading, and the most worthless.

  • Overfitting occurs when strategies learn noise in historical data instead of genuine patterns
  • Multiple testing and random noise can create impressive Sharpe ratios by chance
  • Honest backtesting requires out-of-sample and walk-forward testing, avoiding over-optimization

My tests could fail. They still could not tell me I was wrong.

A test proves your code does what you meant. It cannot prove that what you meant was correct. I could have written that sentence a year ago. I still shipped on the wrong side of it this week.

  • Test failed to confirm code correctness
  • Bug related to QIF payee and memo fields
  • Writer discovered importance of testing assumptions

More from Tuesday 25 August →