You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once the base RA & Deployment Guides have been published, the documents should be updated to include AWS native options from an integration perspective. The following AWS services should be considered as part of this update.
Key Management Service (SSH Key storage)
Elastic Block Store (Shared Storage Pools for Workload Cluster)
AWS CloudWatch (Replacement for Observability)
Database Services with Private Link or Private Endpoint (SQL Server, MySQL, MariaDB, or PostgreSQL and Document DB)
EC2 AutoScaling
Multi-AZ Deployment
The text was updated successfully, but these errors were encountered:
TAP RA is cloud agnostic and can refer for any infra. adding aws specific services will make it tap ra on eks and even some of the services might be applicable for tko
The RA maintained by AWS today includes these services (not all). There may be some outcome-based architectures that we could highlight here if we have some specific examples we're trying to answer. For instance, we could show a fault tolerant TAP deployment in AWS (unique depending on cloud provider or on-premises capabilities).
Once the base RA & Deployment Guides have been published, the documents should be updated to include AWS native options from an integration perspective. The following AWS services should be considered as part of this update.
Key Management Service (SSH Key storage)
Elastic Block Store (Shared Storage Pools for Workload Cluster)
AWS CloudWatch (Replacement for Observability)
Database Services with Private Link or Private Endpoint (SQL Server, MySQL, MariaDB, or PostgreSQL and Document DB)
EC2 AutoScaling
Multi-AZ Deployment
The text was updated successfully, but these errors were encountered: