Coggle requires JavaScript to display documents.
Tags are key and value pairs that act as metadata for organizing your AWS resources. With most AWS resources, you have the option of adding tags when you create the resource Tags can help you manage, identify, organize, search for, and filter resources. You can create tags to categorize resources by purpose, owner, environment, or other criteria
A tag key (for example, CostCenter, Environment, or Project). Tag keys are case sensitive A tag value (for example, 111122223333 or Production). Like tag keys, tag values are case sensitive
AWS service API operation – The tagging API operations supported directly an AWS service Tag Editor console – Some services also support tagging with the AWS Tag Editor console Resource Groups Tagging API – Most services also support tagging using the AWS Resource Groups Tagging API
Each resource can have a maximum of 50 user created tags System created tags that begin with aws: are reserved for AWS use, and do not count against this limit. You can't edit or delete a tag that begins with the aws: prefix User created tags begin with User:
Use AWS Organizations to manage tag policies. When you sign in to the organization's management account, you use Organizations to enable the tag policies feature Use AWS Resource Groups to manage compliance with tag policies If you sign in to an account in your organization, you use Resource Groups to find noncompliant tags on resources in the account. You can correct noncompliant tags in the AWS service where you created the resource If you sign in to the management account in your organization, you can view compliance information for all your organization's accounts
If you sign in to an account in your organization, you use Resource Groups to find noncompliant tags on resources in the account. You can correct noncompliant tags in the AWS service where you created the resource If you sign in to the management account in your organization, you can view compliance information for all your organization's accounts
Companies that are most effective in their use of tags typically create business-relevant tag groupings to organize their resources along technical, business, and security dimensions Companies that use automated processes to manage their infrastructure also include additional, automation-specific tags
Technical tags (App ID, App role, Environment, Version, Clutser) Tags for automation (Date/Time, Opt in/Opt out, Security) Business tags (Project, Owner, Cost Center/Business Unit, Customer) Security tags (Confidentiality, Compliance)
User-Defined CATs - tags created, defined, applied to resources by you AWS-Generated-CATs - tags created, defined, applied to resources by AWS for supported resources
AWS Console > Billing Dashboard Cost allocation tags >- activate both user-defined and aws-defined
Turn on group lifecycle events - To send events to EventBridge about lifecycle changes to your resource groups Create EventBridge Rule - Create a rule that captures events and forwards them to a target, such as AWS Lambda, Amazon SQS, or Amazon SNS Receive events for group changes - EventBridge targets receive the notifications defined in your rules whenever a lifecycle change happens to your resource groups
A tag-based resource group bases its membership on a query that specifies a list of resource types and tags. Tags are keys that help identify and sort your resources within your organization. Optionally, tags include values for keys An AWS CloudFormation stack-based resource group bases its membership on a query that specifies an AWS CloudFormation stack in your account in the current region. You can optionally choose resource types within the stack that you want to be in the group. You can base your query on only one AWS CloudFormation stack
You define tag policies in AWS Organizations and attach them to the entire organization, a set of accounts, or individual accounts In AWS Resource Groups, you can find and correct noncompliant tags on your resources
In a tag policy, you specify tagging rules applicable to resources when they are tagged You can also enforce to prevent from completing noncompliant tagging requests on specified resource types Untagged resources or tags that aren't defined in the tag policy aren't evaluated for compliance with the tag policy It does not report the resources that are not already tagged according to the policy
The required-tags managed rule will report on resources that are not tagged according to the definitions that are set within the AWS Config rule However, the rule is not connected to the tag policy that is set on the organization level
You can use CloudWatch Events to monitor when noncompliant tags are introduced
Regions Resources Types (All vs list) (Optional) Tags - Tag Key (required) Tag Value (optional)
Enable CloudWatch billing alerts in the Billing Dashboard > Billing Preferences Creates CloudWatch Alarms based on: Account Costs Service Costs Total Estimate Charge
Account Costs Service Costs Total Estimate Charge
Before you can create an alarm for your estimated charges, you must enable billing alerts on your Billing Dashboard > Accounts Preferences With this you can monitor your estimated AWS charges and create an alarm using billing metric data After you enable billing alerts, you cannot disable data collection, but you can delete any billing alarms that you created
Create Budgets based on: Cost Usage Reservation Savings Plan
Cost Usage Reservation Savings Plan
Serverless managed service to run container for ECS and EKS Build Container Images Define Memory and Compute Resources Run Application Pay only for requested compute (vs EC2 where you pay for the instance size you use) also improve security through isolation of containers
High availability and Durability - data written to EFS is written in 3 AZs and is accessible through all AZs within the Region offering 99,99% availability Elastic and Scalable - EFS only charges for the capacity used and also scales to meet storage and throughput capacity Container and Serverless file storage support - EFS integrates with multiple services such as Lambda and EC2 as well as AWS Backup for automatic backup Storage Classes and Lifecycle Management - EFS offers 4 storage classes (Standard, Standard-IA, One Zone and One Zone-IA). Lifecycle Management moves file based on usage patterns through lifecycle policies
Aurora Serverless - auto-scaling version of Aurora which automatically scales capacity up and down to meet the needs of your application RDS Storage AutoScaling - helps reduce costs by allowing RDS storage to grow with your data Reserved Database Instances - through reserved instance plan, you can purchase compute upfront for a reduced costs
CloudWatch Metrics are data about performance and costs of your system Metrics appears as you create and deploy new services resources Metrics can also be published from your application
Graph - CloudWatch allows to graph your metrics from AWS services or published from your application Dashboard - CloudWatch generates automatic dashboards and allows to create dashboards widgets from your graph for easy data retrieval
Allows to filter, aggregate and graph metrics in the console Choose metric to explore Select Resources by Tag Aggregate and Graph Add to Dashboard
Choose metric to explore Select Resources by Tag Aggregate and Graph Add to Dashboard
Allows to configure our metrics to stream to different AWS services to S3 to Kinesis Data firehose
to S3 to Kinesis Data firehose
Waits SQL queries Host connections Users executing queries
Database Metrics Cache Checkpoint Concurrency (deadlock) I/O SQL Temp Transactions Users WAL (archived_count, archived_failed_cound) Sate (active_count, idle_count ...) OS Metric -
Cache Checkpoint Concurrency (deadlock) I/O SQL Temp Transactions Users WAL (archived_count, archived_failed_cound) Sate (active_count, idle_count ...)
-
Temporary - ephemeral - block-level storage device for EC2 Does not exist independently from the life of the instance Great for frequently changing data, caches, temporary content, buffers, etc. EBS-backed AMI launch faster than instance store-backed AMI (due to S3 copy) It is block-storage (just like EBS) Cannot change size once created
For the instance types that do support instance store volumes, the number and size of the instance store volumes vary by instance size You can have many instance store volumes on a single EC2 instance (based on OS and instance type) Greater throughput than EBS Volumes created from a template in S3 Can be selected as root volume or as additional volumes Must be configured at EC2 launch, can't attach instance store volumes after launch or detach from one and attach to another If you reboot the instance data is persisted (including reboot due to power failure)
Terminates Stops (Cannot be in a stopped state; instances are running or terminated) Hibernates
Distribute instance store data across multiple AZs Automate backups of the instance store volume to persistent storage on a regular basis (at least on Nitro Systems) You can attach EBS volumes to an instance store EC2 instance (here)
Use recent version of AMI Enable swap space on the volume Properly map the SSD instance store on EC2 Launch For instance types with NVMe instance store volumes, all of the supported instance store volumes are automatically attached to the instance at launch (automatically enumerated and assigned a device name on instance launch) For instance types with non-NVMe instance store volumes, such as C1, C3, M1, M2, M3, R3, D2, H1, I2, G2, X1, and X1e, you must manually specify the block device mappings for the instance store volumes that you want to attach at launch
For instance types with NVMe instance store volumes, all of the supported instance store volumes are automatically attached to the instance at launch (automatically enumerated and assigned a device name on instance launch) For instance types with non-NVMe instance store volumes, such as C1, C3, M1, M2, M3, R3, D2, H1, I2, G2, X1, and X1e, you must manually specify the block device mappings for the instance store volumes that you want to attach at launch
Cost Effective - achieving a desired outcome at the lowest possible cost Cost Efficient - achieves the desired outcome while using the least amount of resources