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
Analyze public and cross-account access
PostedNovember 27, 2024
UpdatedNovember 27, 2024
ByKevin McCaffrey
Continuously analyzing public and cross-account access to your AWS resources helps ensure that only the necessary entities have access to specific resources, minimizing security risks. By reducing public and cross-account access to only what is absolutely required, you protect your cloud environment from unintended exposure or unauthorized access.
- Monitor public and cross-account access: Use tools such as AWS IAM Access Analyzer and AWS Config to continuously monitor for resources that are publicly accessible or shared across accounts. This monitoring helps you detect any unintended access or potential vulnerabilities.
- Identify and reduce public access: Regularly review all resources exposed to the public internet. Where possible, remove public access to resources like S3 buckets, databases, or EC2 instances, and restrict access to only specific trusted accounts or networks. Ensure that public access is only enabled for resources where it is explicitly required.
- Manage cross-account access: For resources that need to be shared across AWS accounts, ensure that cross-account access is tightly controlled. Use IAM policies and resource-based policies to specify which accounts or entities are allowed access, applying the least privilege principle to restrict access to the necessary resources.
- Use AWS IAM Access Analyzer: Leverage IAM Access Analyzer to automatically detect resources with public or cross-account access. This tool helps you quickly identify potential security risks and take action to reduce unnecessary exposure.
- Audit and review access policies regularly: Perform regular audits of public and cross-account access policies to ensure they align with current security best practices. Remove or tighten access when it is no longer needed, and ensure that access remains scoped appropriately.
- Implement resource tagging for visibility: Tag resources that are exposed to the public or shared across accounts to provide clear visibility into their access status. Tags can help track and review access permissions and ensure that public and cross-account resources are carefully managed.
Supporting Questions:
- How do you continuously monitor and review public and cross-account access to your AWS resources?
- What processes are in place to reduce unnecessary public and cross-account access?
- How do you manage and enforce least privilege for resources that require cross-account access?
Roles and Responsibilities:
Cloud Security Architect:
- Responsibilities:
- Design and implement strategies to minimize public and cross-account access, ensuring that resources are only accessible by authorized entities.
- Use AWS IAM Access Analyzer to continuously monitor for public and cross-account access risks.
- Review and update access policies regularly to remove unnecessary or excessive access.
Cloud Administrator:
- Responsibilities:
- Manage and configure cross-account access using IAM and resource-based policies to restrict access to specific resources.
- Monitor and log access using AWS tools to detect public exposure or unauthorized cross-account sharing.
- Work with the security team to reduce public access and enforce access controls based on current organizational needs.
Artefacts:
- Access Control Policies: Documentation outlining the public and cross-account access policies for each resource, including how access is managed and restricted.
- Access Analyzer Reports: Reports generated by AWS IAM Access Analyzer showing resources with public or cross-account access and recommendations for reducing exposure.
- Audit Logs: Logs from AWS CloudTrail or AWS Config that track access to resources and identify any anomalies or unauthorized access patterns.
Relevant AWS Services:
AWS Identity Services:
- AWS Identity and Access Management (IAM): Use IAM policies to control cross-account access and resource-based policies to restrict public access, ensuring least privilege is applied.
- AWS IAM Access Analyzer: A tool that helps detect resources with public or cross-account access and provides recommendations to reduce unnecessary exposure.
Monitoring and Compliance Services:
- AWS CloudTrail: Logs all access events for resources, enabling you to monitor public and cross-account access patterns and detect potential security risks.
- AWS Config: Tracks configuration changes to resources, including updates to public and cross-account access policies, ensuring compliance with your security requirements.
Table of Contents