Module 5
Module 5
AWS Config is a service that enables you to assess, audit, and evaluate the configurations of
your AWS resources. Config continuously monitors and records your AWS resource
configurations and allows you to automate the evaluation of recorded configurations against
desired configurations.
With Config, you can review changes in configurations and relationships between AWS
resources, dive into detailed resource configuration histories, and determine your overall
compliance against the configurations specified in your internal guidelines.
AWS Config is designed to help you oversee your
application resources in the following scenarios:
1. Resource Administration
To exercise better governance over your resource
configurations and to detect resource
misconfigurations, you need fine-grained visibility into
what resources exist and how these resources are
configured at any time.
CONT,
2. Auditing and Compliance
You might be working with data that requires
frequent audits to ensure compliance with internal
policies and best practices. To demonstrate
compliance, you need access to the historical
configurations of your resources. This information is
provided by AWS Config.
CONT
3. Managing and Troubleshooting Configuration
Changes
When you use multiple AWS resources that depend on
one another, a change in the configuration of one
resource might have unintended consequences on
related resources. With AWS Config, you can view how
the resource you intend to modify is related to other
resources and assess the impact of your change.
You can also use the historical configurations of your
resources provided by AWS Config to troubleshoot
issues and to access the last known good
configuration of a problem resource.
CONT
4. Security Analysis
To analyze potential security weaknesses, you need detailed
historical information about your AWS resource configurations,
such as the AWS Identity and Access Management (IAM)
permissions that are granted to your users, or the Amazon EC2
security group rules that control access to your resources.
You can use AWS Config to view the IAM policy that was
assigned to a user, group, or role at any time in which AWS
Config was recording. This information can help you determine
the permissions that belonged to a user at a specific time: for
example, you can view whether the user John Doe had
permission to modify Amazon VPC settings on Jan 1, 2015.
AWS Systems Manager
AWS Systems Manager is the operations hub for your AWS applications and
resources and a secure end-to-end management solution for hybrid and multicloud
environments that enables secure operations at scale.
Systems Manager capabilities perform actions on your resources as the following,
Access Systems Manager – Use one of the available options for accessing
Systems Manager.
Verification and processing – Systems Manager verifies that your user, group, or
role has the required AWS Identity and Access Management (IAM) permissions to
perform the action you specified. If the target of your action is a managed node, the
Systems Manager Agent (SSM Agent) running on the node performs the action. For
other types of resources, Systems Manager performs the specified action or
communicates with other AWS services to perform the action on behalf of Systems
CONT
Reporting – Systems Manager, SSM Agent, and other AWS services
that performed an action on behalf of Systems Manager report status.
Systems Manager can send status details to other AWS services, if
configured.
12 months free
You can use these offers for 12 months following your initial sign
up date to AWS.
Short-term trials
You can use a free tier limit each month for less than 12 months.
Most short-term free trial offers start from the date that you
activate a particular service.
AWS Account Management
An AWS account represents a formal business relationship you establish
with AWS. You create and manage your AWS resources in an AWS
account, and your account provides identity management capabilities
for access and billing.
Each AWS account has a unique ID which differentiates it from other
AWS accounts.
Your cloud resources and data are contained in an AWS account. An
account acts as an identity and access management isolation boundary.
When you need to share resources and data between two accounts, you
must explicitly allow this access. By default, no access is allowed
between accounts.
For example, if you designate different accounts to contain your
production and non-production resources and data, no access is allowed
between those environments by default.
AWS Account Management
AWS accounts are also a fundamental part of accessing AWS services. As
shown in the following illustration, an AWS account serves two primary
functions:
• Resources container – An AWS account is the basic container for all the
AWS resources you create as an AWS customer. For example, an Amazon
Simple Storage Service (Amazon S3) bucket, an Amazon Relational
Database Service (Amazon RDS) database, and an Amazon Elastic
Compute Cloud (Amazon EC2) instance are all resources. Every resource is
uniquely identified by an Amazon Resource Name (ARN) that includes the
account ID of the account that contains, or owns, the resource.
• Security boundary – An AWS account is also the basic security boundary
for your AWS resources. Resources that you create in your account are
available to users who have credentials for your account. Among the key
resources you can create in your account are identities, such as users and
roles. Identities have credentials that someone can use to sign in
(authenticate) to AWS. Identities also have permission policies that specify
what a user can do (authorization) with the resources in the account.
AWS Budgets
You can use AWS Budgets to track and take action on your AWS costs and usage. You can
use AWS Budgets to monitor your aggregate utilization and coverage metrics for your
Reserved Instances (RIs) or Savings Plans. If you're new to AWS Budgets, see Best practices
for AWS Budgets.
You can use AWS Budgets to enable simple-to-complex cost and usage tracking. Some
examples include:
Setting a monthly cost budget with a fixed target amount to track all costs associated with
your account. You can choose to be alerted for both actual (after accruing) and forecasted
(before accruing) spends.
Setting a monthly cost budget with a variable target amount, with each subsequent month
growing the budget target by 5 percent. Then, you can configure your notifications for 80
percent of your budgeted amount and apply an action. For example, you could automatically
apply a custom IAM policy that denies you the ability to provision additional resources within
an account.
Setting a monthly usage budget with a fixed usage amount and forecasted notifications to
help ensure that you are staying within the service limits for a specific service. You can also
be sure you are staying under a specific AWS Free Tier offering.
Setting a daily utilization or coverage budget to track your RI (Reserved Instances) or
Savings Plans. You can choose to be notified through email and Amazon SNS topics when
your utilization drops below 80 percent for a given day.
AWS Budgets
AWS Budgets information is updated up to three times a day. Updates typically occur 8–12
hours after the previous update. Budgets can track your unblended, amortized, and blended
costs. Budgets can include or exclude charges such as discounts, refunds, support fees, and
taxes.