DOCSEARCHbyAlgolia
Submit Docs

Amazon Web Services (AWS) Documentation

website·Indexed 34 days ago

https://outerbounds.com/docs/

Comprehensive technical documentation for AWS services and tools, including Amazon RDS, ECR, Athena, SageMaker AI, EventBridge, EKS, AWS CLI, IAM, Certificate Manager, AWS Batch, EC2, Bedrock, and Secrets Manager. Covers installation, configuration, API permissions, security best practices, and operational guides for cloud infrastructure and AI/ML workloads.

Tokens
28.3K
Snippets
86
Records
162
Agent score
70%

What's inside AWS

  1. Overview of legacy scheduled rules in Amazon EventBridge

    Scheduled rules are a legacy feature of Amazon EventBridge. They allow you to trigger targets at regular intervals or specific times. All scheduled events use the UTC+0 time zone, and the minimum precision is one minute. Note that there may be a delay of several seconds between the trigger time and the target execution due to the distributed nature of the service.

    AWS recommends using EventBridge Scheduler instead of legacy scheduled rules for improved scalability, more flexible time windows, retry limits, and a wider set of target API operations.

  2. Overview of AWS Secrets Manager

    AWS Secrets Manager is a service used to manage, retrieve, and rotate secrets throughout their lifecycle. It is designed to replace hard-coded credentials in application source code with dynamic runtime calls, reducing the risk of credential compromise. Supported secret types include database credentials, application credentials, OAuth tokens, and API keys. Key features include automatic rotation schedules, which allow long-term secrets to be replaced by short-term ones without requiring application redeployments.

  3. Overview of Elastic Fabric Adapter (EFA)

    The Elastic Fabric Adapter (EFA) is a network device for Amazon EC2 designed to accelerate AI, Machine Learning (ML), and High Performance Computing (HPC) applications. It provides lower and more consistent latency and higher throughput than traditional TCP transport by utilizing the Scalable Reliable Datagram (SRD) protocol and OS-bypass capabilities. EFA integrates with the Libfabric API to allow applications to communicate directly with the network device, bypassing the operating system kernel to reduce overhead.

  4. Overview of exporting Amazon RDS DB snapshots to S3

    Amazon RDS allows exporting DB snapshot data (manual, automated, or AWS Backup snapshots) to an Amazon S3 bucket. The process runs in the background and does not impact active database performance. Data is stored in a compressed, consistent Apache Parquet format.

    Key Constraints:

    • Exported data cannot be restored back to a new DB instance or imported into an existing one.
    • The target S3 bucket must be in the same AWS Region as the snapshot.
    • Exported data is intended for analysis via Amazon Athena, Amazon Redshift Spectrum, or transformation via AWS Glue for subsequent import via AWS DMS or custom scripts.

  5. Overview of IAM Roles for Service Accounts (IRSA)

    IAM Roles for Service Accounts (IRSA) allows you to associate an IAM role with a Kubernetes service account. This enables Pods to make AWS API requests using the AWS SDK or CLI with specific permissions, rather than relying on the Amazon EC2 instance profile of the worker node.

    Key benefits include:

    • Least Privilege: Permissions are scoped to the service account; only Pods using that account have access.
    • Credential Isolation: When the EC2 Instance Metadata Service (IMDS) is restricted, Pods can only retrieve credentials for their assigned IAM role, preventing access to credentials of other Pods on the same node.
    • Auditability: All requests are logged via AWS CloudTrail.

    Constraints: IRSA cannot be used with local clusters for Amazon EKS on AWS Outposts. Pods configured with hostNetwork: true still have IMDS access, though the AWS SDK/CLI will prioritize IRSA credentials if enabled.

  6. Enable Elastic Fabric Adapter (EFA) on Amazon EC2

    Elastic Fabric Adapter (EFA) is an optional networking feature available for supported Amazon EC2 instance types. It can be enabled on any supported instance at no additional cost.

  7. Run distributed applications using AWS Batch Multi-Node Parallel (MNP) jobs

    AWS Batch multi-node parallel (MNP) jobs, also known as gang scheduling, allow a single job to span multiple Amazon EC2 instances. This is used for large-scale high-performance computing (HPC) and distributed GPU model training. MNP jobs are compatible with any framework supporting IP-based inter-node communication, such as Apache MXNet, TensorFlow, Caffe2, or Message Passing Interface (MPI).

    Key operational characteristics:

    • Single-Tenant: Only one job container runs on each EC2 instance.
    • Node Structure: A job consists of one main node (launched first) and multiple child nodes. The job is considered finished only when the main node exits, at which point all child nodes are stopped.
    • Job Status: The final status (SUCCEEDED or FAILED) is determined by the main node. To retrieve status, use the job ID. To retrieve child node details, use the notation {job_id}#{node_index} (e.g., job-id#1 for the second node) via the DescribeJobs API.
    • Retries: If job retries are configured, a failure of the main node triggers a retry. Failures of child nodes do not trigger new attempts.
    • Requirement: The application code must include the necessary frameworks and libraries for distributed communication.

  8. Understand Amazon Athena data source architecture

    Amazon Athena queries data stored in various locations and formats (CSV, JSON, Avro, Parquet, etc.) by using a combination of a dataset and a data catalog.

    Key concepts include:

    • Dataset: The actual raw data stored in a specific format.
    • Metadata/Schema: Data describing the dataset, such as table names, column names, and data types.
    • Data Catalog (Metastore): The system used to organize metadata.
    • Data Source: The combination of a dataset and the data catalog that describes it.

    Athena natively supports the AWS Glue Data Catalog, which can describe datasets in Amazon S3, Amazon Redshift, and Amazon DynamoDB. For other sources, Athena uses connectors or supports external Hive metastores.

  9. Verify AWS CLI installation package integrity via GPG

    To ensure the AWS CLI installer has not been altered, verify its cryptographic signature using GnuPG. Download the .sig file corresponding to your architecture and verify it against the .zip installer. A 'WARNING: This key is not certified with a trusted signature!' is expected and does not indicate a problem.
    # Example for x86_64: Download the signature file
curl -o awscliv2.sig https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip.sig

# Verify the signature against the zip file
gpg --verify awscliv2.sig awscliv2.zip

  10. Validate IAM policies using IAM Access Analyzer

    Use IAM Access Analyzer policy validation to ensure your JSON policies adhere to IAM policy language and security best practices. The tool provides over 100 policy checks and actionable recommendations to refine policies during creation or editing in the console. It is recommended to review and validate all existing policies to ensure they are secure and functional.

  11. Install AWS CLI on Windows using PowerShell script

    The recommended installation method for Windows is the PowerShell install script. By default, it installs for the current user in %LOCALAPPDATA%\Programs\Amazon\AWSCLIV2. To install for all users (requiring Administrator privileges), use the -System argument.
    # Install for current user
irm https://awscli.amazonaws.com/v2/install.ps1 | iex

# Install for all users (Run in elevated Administrator prompt)
irm 'https://awscli.amazonaws.com/v2/install.ps1' -OutFile install.ps1; try { .\install.ps1 -System } finally { Remove-Item install.ps1 }

# View help options
irm 'https://awscli.amazonaws.com/v2/install.ps1' -OutFile install.ps1; try { .\install.ps1 -Help } finally { Remove-Item install.ps1 }

  12. Identify use cases for IAM long-term access keys

    While temporary credentials are preferred, long-term IAM user access keys are necessary for specific scenarios:

    • Workloads unable to use IAM roles: Such as certain WordPress plugins or workloads running in locations where IAM roles cannot provide temporary credentials.
    • Third-party AWS clients: Tools or vendors not hosted on AWS that do not support IAM Identity Center.
    • AWS CodeCommit: Using SSH keys or service-specific credentials (though the git-remote-codecommit utility is recommended for rotating credentials).
    • Amazon Keyspaces (for Apache Cassandra): For testing Cassandra compatibility when IAM Identity Center cannot be used.