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
Rely on a centralized identity provider
PostedNovember 27, 2024
UpdatedNovember 27, 2024
ByKevin McCaffrey
For workforce identities (employees and contractors), relying on a centralized identity provider enables you to manage identities in one place. This centralization simplifies managing access across multiple applications and systems, allowing you to create, assign, manage, revoke, and audit access from a single location. Centralized identity management reduces complexity, enhances security, and ensures consistent access control policies are applied across all services and resources.
- Centralize identity management: Use a centralized identity provider (IdP) to manage workforce identities, reducing the need to create and manage separate credentials for each system or application. This simplifies user onboarding and offboarding, ensuring quick access updates.
- Integrate with AWS IAM: Federate identities from your centralized IdP with AWS Identity and Access Management (IAM) using standards such as SAML, OpenID Connect, or AWS Single Sign-On (SSO). This ensures that users have seamless and secure access to AWS resources without managing separate AWS credentials.
- Automate provisioning and deprovisioning: By using a centralized identity provider, you can automate the process of provisioning and deprovisioning access for users. When employees join or leave, their access to all connected systems is adjusted accordingly, reducing the risk of leaving unauthorized access in place.
- Monitor and audit access centrally: A centralized identity provider allows for consolidated monitoring and auditing of user access across multiple systems. This simplifies compliance reporting and ensures that access logs can be reviewed in one place for security purposes.
- Apply consistent access policies: Centralized identity management enables you to enforce consistent access control policies across your organization. This ensures that security policies, such as multi-factor authentication (MFA) and password complexity, are uniformly applied.
Supporting Questions:
- How do you integrate a centralized identity provider with your AWS environment?
- What processes are in place to automate the provisioning and deprovisioning of user access?
- How do you monitor and audit access across multiple systems using your identity provider?
Roles and Responsibilities:
Identity and Access Management Specialist:
- Responsibilities:
- Set up and manage the centralized identity provider to control workforce access.
- Ensure seamless integration of the IdP with AWS IAM for federated access.
- Automate the provisioning and deprovisioning process across all connected systems.
Security Officer:
- Responsibilities:
- Enforce consistent access policies, such as MFA, via the centralized identity provider.
- Monitor access logs and audit user access to ensure compliance with security policies.
- Regularly review user roles and access levels to ensure they align with business requirements.
Artefacts:
- Identity Provider Configuration: Documentation outlining how the centralized identity provider is configured and integrated with AWS and other systems.
- Access Control Policies: Policies defining access requirements, such as MFA enforcement and password complexity, applied through the centralized identity provider.
- Audit Logs: Centralized logs from the identity provider showing user access across various systems, useful for compliance and security audits.
Relevant AWS Services:
- AWS Single Sign-On (SSO): A service that integrates with your centralized identity provider to manage access to AWS accounts and applications, enabling single sign-on for users.
- AWS Identity and Access Management (IAM): Federates identities from a centralized IdP and controls access to AWS resources based on the policies associated with those identities.
- Amazon Cognito: Allows integration of a centralized identity provider for applications, enabling user sign-in and access management for web and mobile apps.
- AWS Directory Service: Provides centralized directory management for AWS resources and applications, allowing for seamless integration with existing Active Directory or other identity providers.
- AWS CloudTrail: Logs and monitors all identity-related actions, providing a centralized view of identity access and activities across the AWS environment.
Table of Contents