Search for Well Architected Advice
-
Operational Excellence
-
- Resources have identified owners
- Processes and procedures have identified owners
- Operations activities have identified owners responsible for their performance
- Team members know what they are responsible for
- Mechanisms exist to identify responsibility and ownership
- Mechanisms exist to request additions, changes, and exceptions
- Responsibilities between teams are predefined or negotiated
-
- Executive Sponsorship
- Team members are empowered to take action when outcomes are at risk
- Escalation is encouraged
- Communications are timely, clear, and actionable
- Experimentation is encouraged
- Team members are encouraged to maintain and grow their skill sets
- Resource teams appropriately
- Diverse opinions are encouraged and sought within and across teams
-
- Use version control
- Test and validate changes
- Use configuration management systems
- Use build and deployment management systems
- Perform patch management
- Implement practices to improve code quality
- Share design standards
- Use multiple environments
- Make frequent, small, reversible changes
- Fully automate integration and deployment
-
Security
-
- Evaluate and implement new security services and features regularly
- Automate testing and validation of security controls in pipelines
- Identify and prioritize risks using a threat model
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and validate control objectives
- Secure account root user and properties
- Separate workloads using accounts
-
- Analyze public and cross-account access
- Manage access based on life cycle
- Share resources securely with a third party
- Reduce permissions continuously
- Share resources securely within your organization
- Establish emergency access process
- Define permission guardrails for your organization
- Grant least privilege access
- Define access requirements
-
- Build a program that embeds security ownership in workload teams
- Centralize services for packages and dependencies
- Manual code reviews
- Automate testing throughout the development and release lifecycle
- Train for application security
- Regularly assess security properties of the pipelines
- Deploy software programmatically
- Perform regular penetration testing
-
-
Reliability
-
- How do you ensure sufficient gap between quotas and maximum usage to accommodate failover?
- How do you automate quota management?
- How do you monitor and manage service quotas?
- How do you accommodate fixed service quotas and constraints through architecture?
- How do you manage service quotas and constraints across accounts and Regions?
- How do you manage service quotas and constraints?
- How do you build a program that embeds reliability into workload teams?
-
- How do you enforce non-overlapping private IP address ranges in all private address spaces?
- How do you prefer hub-and-spoke topologies over many-to-many mesh?
- How do you ensure IP subnet allocation accounts for expansion and availability?
- How do you provision redundant connectivity between private networks in the cloud and on-premises environments?
- How do you use highly available network connectivity for workload public endpoints?
-
- Monitor end-to-end tracing of requests through your system
- Conduct reviews regularly
- Analytics
- Automate responses (Real-time processing and alarming)
- Send notifications (Real-time processing and alarming)
- Define and calculate metrics (Aggregation)
- Monitor End-to-End Tracing of Requests Through Your System
-
- Monitor all components of the workload to detect failures
- Fail over to healthy resources
- Automate healing on all layers
- Rely on the data plane and not the control plane during recovery
- Use static stability to prevent bimodal behavior
- Send notifications when events impact availability
- Architect your product to meet availability targets and uptime service level agreements (SLAs)
-
-
Cost Optimization
-
- Establish ownership of cost optimization
- Establish a partnership between finance and technology
- Establish cloud budgets and forecasts
- Implement cost awareness in your organizational processes
- Monitor cost proactively
- Keep up-to-date with new service releases
- Quantify business value from cost optimization
- Report and notify on cost optimization
- Create a cost-aware culture
-
- Perform cost analysis for different usage over time
- Analyze all components of this workload
- Perform a thorough analysis of each component
- Select components of this workload to optimize cost in line with organization priorities
- Perform cost analysis for different usage over time
- Select software with cost effective licensing
-
-
Performance
-
- Learn about and understand available cloud services and features
- Evaluate how trade-offs impact customers and architecture efficiency
- Use guidance from your cloud provider or an appropriate partner to learn about architecture patterns and best practices
- Factor cost into architectural decisions
- Use policies and reference architectures
- Use benchmarking to drive architectural decisions
- Use a data-driven approach for architectural choices
-
- Use purpose-built data store that best support your data access and storage requirements
- Collect and record data store performance metrics
- Evaluate available configuration options for data store
- Implement Strategies to Improve Query Performance in Data Store
- Implement data access patterns that utilize caching
-
- Understand how networking impacts performance
- Evaluate available networking features
- Choose appropriate dedicated connectivity or VPN for your workload
- Use load balancing to distribute traffic across multiple resources
- Choose network protocols to improve performance
- Choose your workload's location based on network requirements
- Optimize network configuration based on metrics
-
- Establish key performance indicators (KPIs) to measure workload health and performance
- Use monitoring solutions to understand the areas where performance is most critical
- Define a process to improve workload performance
- Review metrics at regular intervals
- Load test your workload
- Use automation to proactively remediate performance-related issues
- Keep your workload and services up-to-date
-
-
Sustainability
-
- Optimize geographic placement of workloads based on their networking requirements
- Align SLAs with sustainability goals
- Optimize geographic placement of workloads based on their networking requirements
- Stop the creation and maintenance of unused assets
- Optimize team member resources for activities performed
- Implement buffering or throttling to flatten the demand curve
-
- Optimize software and architecture for asynchronous and scheduled jobs
- Remove or refactor workload components with low or no use
- Optimize areas of code that consume the most time or resources
- Optimize impact on devices and equipment
- Use software patterns and architectures that best support data access and storage patterns
- Remove unneeded or redundant data
- Use technologies that support data access and storage patterns
- Use policies to manage the lifecycle of your datasets
- Use shared file systems or storage to access common data
- Back up data only when difficult to recreate
- Use elasticity and automation to expand block storage or file system
- Minimize data movement across networks
-
- Articles coming soon
< All Topics
Print
Manage access based on life cycle
PostedNovember 27, 2024
UpdatedNovember 27, 2024
ByKevin McCaffrey
Integrating access controls with both operator and application lifecycle events ensures that access to your resources is always aligned with the current roles and responsibilities of users and applications. By tightly coupling access management with your centralized identity provider, you can ensure that permissions are updated or revoked automatically when users leave the organization, change roles, or when applications are decommissioned. This approach reduces the risk of orphaned accounts or excessive permissions lingering in the system.
- Automate access provisioning and deprovisioning: Integrate with your centralized identity provider (such as AWS Single Sign-On or an external federation provider) to automatically provision and revoke access based on lifecycle events. When users join, leave, or change roles within your organization, their access to AWS resources should be automatically updated to reflect these changes.
- Integrate with HR and identity systems: Use integration with your HR system or identity provider to trigger access control updates. For example, when an employee is terminated or moves to a new role, the HR system should trigger the removal or adjustment of their access privileges in AWS.
- Remove access when roles change or users leave: Ensure that user access is revoked when they no longer require it. This includes removing access when users change roles within the organization or leave the company entirely, preventing lingering access that could be misused.
- Enforce temporary access for contractors or external parties: Use time-bound access for temporary users such as contractors or external partners. Ensure that access is granted only for the duration of their work and is automatically revoked afterward.
- Manage application lifecycle access: As applications or services are decommissioned or retired, ensure that associated permissions and access controls are also removed. This prevents unnecessary permissions from remaining in your environment, reducing security risks.
- Audit access regularly: Conduct regular audits to ensure that access controls remain in line with the current lifecycle status of users and applications. Use AWS CloudTrail and IAM reports to identify any orphaned accounts or misaligned permissions.
Supporting Questions:
- How do you ensure that user access is automatically updated or revoked when roles change or users leave the organization?
- What systems are integrated with your identity provider to manage the lifecycle of users and applications?
- How do you handle temporary access for contractors and ensure it is revoked when no longer needed?
Roles and Responsibilities:
Identity and Access Management Specialist:
- Responsibilities:
- Ensure that access is provisioned and deprovisioned automatically based on lifecycle events such as user terminations or role changes.
- Integrate identity management systems with HR systems to automate access controls.
- Regularly review and update access policies to ensure they reflect the current organizational structure.
Cloud Administrator:
- Responsibilities:
- Configure and manage access controls to ensure they align with the lifecycle of both operators and applications.
- Ensure that temporary access for contractors and external parties is managed and revoked in a timely manner.
- Audit lifecycle-related access changes using AWS CloudTrail and IAM reports.
Artefacts:
- Lifecycle Access Management Policies: Documentation that outlines the processes for granting, updating, and revoking access based on user and application lifecycle events.
- Access Deprovisioning Logs: Logs from AWS CloudTrail or IAM reports that track the removal of access following lifecycle changes, such as employee terminations or role changes.
- Audit Reports: Reports generated from periodic access audits to ensure that permissions align with current user roles and lifecycle status.
Relevant AWS Services:
AWS Identity Services:
- AWS Identity and Access Management (IAM): Use IAM to manage access permissions for users and applications, automatically updating or revoking access based on lifecycle changes.
- AWS Single Sign-On (SSO): Integrate with your centralized identity provider to automate access provisioning and deprovisioning, ensuring that user permissions reflect their current roles.
- AWS Directory Service: Manage lifecycle access for users in Active Directory or other identity directories, ensuring access is controlled based on user lifecycle status.
Monitoring and Compliance Services:
- AWS CloudTrail: Monitor and log all changes in user and application access, ensuring that permissions are aligned with lifecycle events and any anomalies are detected.
- AWS Config: Track changes in access policies and permissions to ensure compliance with lifecycle-based access management policies.
Table of Contents