A Practical Guide to AWS IAM Sign in
A Practical Guide to AWS IAM
Sign in
  • Introduction Preview
    • Structure of this book Preview
  • Access control basics Preview
    • Access elements
    • CloudTrail logging
  • IAM Policies
    • Structure
    • Policy types
    • Visual editor
  • Evaluation flow
    • Step 1: Build the request context
    • Step 2: Collect all applicable policies
    • Step 3: Run the evaluation logic
  • Evaluation examples
    • Identity policies to allow access
    • Resource policy to deny access
    • Using conditions
    • Restricted resources
  • How to secure an AWS account
    • Security as an AWS administrator
    • Security as a developer
  • Conclusion
  • Glossary
  • About the author
  • Changelog
  • Copyright
  • Introduction Preview
    • Structure of this book Preview
  • Access control basics Preview
    • Access elements
    • CloudTrail logging
  • IAM Policies
    • Structure
    • Policy types
    • Visual editor
  • Evaluation flow
    • Step 1: Build the request context
    • Step 2: Collect all applicable policies
    • Step 3: Run the evaluation logic
  • Evaluation examples
    • Identity policies to allow access
    • Resource policy to deny access
    • Using conditions
    • Restricted resources
  • How to secure an AWS account
    • Security as an AWS administrator
    • Security as a developer
  • Conclusion
  • Glossary
  • About the author
  • Changelog
  • Copyright

Security as a developer Follow an additive permission strategy Use roles instead of users where possible Maintain an identical test environment Automate security checks

Security as a developer

Follow an additive permission strategy

Use roles instead of users where possible

Maintain an identical test environment

Automate security checks

This chapter is not included in the preview
  • Sign in with your license key or
  • Buy the book
Previous
< Security as an AWS administrator
Next
Conclusion >
© Tamás Sallai - advancedweb.hu
Security as a developer Follow an additive permission strategy Use roles instead of users where possible Maintain an identical test environment Automate security checks