VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: Why did the bands of my anomaly detector in CloudWatch change suddenly?

I created an anomaly detection band on my Amazon CloudWatch metric but the band has changed significantly. Why did my anomaly band shift?ResolutionCloudWatch applies statistical and machine learning algorithms when you enable anomaly detection for a metric. These algorithms analyze the metric, detect normal baselines, and then surface anomalies with no user intervention. The algorithms generate an anomaly detection model. The model generates a range of expected values that represent normal metric behavior.After you create a model, CloudWatch anomaly detection continually evaluates the model and makes adjustments. It does this to make sure that its analysis is as accurate as possible. If another anomaly detection model that is trained with the most recent data performs better than the current model, then CloudWatch anomaly detection switches to the new model. This can cause the anomaly detection bands to shift.

Related informationUsing CloudWatch anomaly detection
Question: Why do I receive an error when I try to unlink a member account from my organization in AWS Organizations?

I received an error when I tried to unlink a member account from my organization:"One or more of the member accounts that you want to remove has not completed the account sign-up steps."What does this error message mean, and how do I fix the error?ResolutionBefore an account can be removed (unlinked) from an organization, you or the administrator of the member account must do the following:Provide a valid payment method.Verify the account by phone.Choose an AWS Support plan for the account.The error indicates that one or more of these steps is incomplete:You can add this information and then remove the account by following one of these procedures:If you're signing in as the member account that you want to remove from an organization, follow the instructions at Leaving an organization as a member account.If you're signing in as the management account in an organization and can access the member accounts, follow the instructions at Removing a member account from your organization.If you're signing in as the management account in an organization and can't access the member accounts, see How do I remove a member account from an organization in AWS Organizations when I can't sign in to the member account?Note: AWS Support can't change the structure or membership of your organization.

Related informationHow do I remove a member account from an organization's consolidated bill in AWS Organizations?
Question: How are Amazon EC2 instance-hours billed?

I want to know how I am billed for my Amazon Elastic Compute Cloud (Amazon EC2) instances.

ResolutionYour Amazon EC2 usage is calculated by either the hour or the second based on the size of the instance, operating system, and the AWS Region where the instances are launched. Pricing is per instance-hour consumed for each instance, from the time an instance is launched until it's terminated or stopped.Each partial instance-hour consumed is billed per-second for instances launched in Linux, Windows, or Windows with SQL Enterprise, SQL Standard, or SQL Web instances.Each partial instance-hour is billed as a full hour for all other instance types.When reviewing your Amazon EC2 usage, consider the following:If your instance is billed by the hour, then you're billed for a minimum of one hour each time a new instance is started—that is, when the instance enters the running state.If your instance is billed by the second, then you're billed for a minimum of 60 seconds each time a new instance is started—that is, when the instance enters the running state.An instance stays in the running state while being rebooted.If your instance is stopped and started, the AWS accounting mechanism charges more units in the hour that the instance is stopped and started. You're then billed fewer units in the hour the instance is terminated so that your overall billing remains unaffected.Instances that are in any other state aren't billed.For more information on instance pricing based on purchase options, see Amazon EC2 pricing.If you purchase an Amazon EC2 Reserved Instance, then the terms of your Reserved Instance contract can modify the way that you're billed. For more information, see What is an Amazon EC2 Reserved Instance?If you signed up for Savings Plans, then see Savings Plans FAQ.

Related informationAmazon EC2 FAQsWhy am I charged for Amazon EC2 when all my instances were terminated?How are charges for Amazon EBS volumes calculated on my bill?
Question: Why aren't my retention policies deleting Amazon EBS snapshots that are created by Amazon Data Lifecycle Manager?

I'm using Amazon Data Lifecycle Manager to create Amazon Elastic Block Store (Amazon EBS) snapshot policies with a retention schedule. However, the lifecycle policy isn't deleting the snapshots.

ResolutionIf the lifecycle policy that you created using Data Lifecycle Manager isn't deleting the snapshots, then consider the following scenarios.Note: You can't use Data Lifecycle Manager to manage snapshots that you created outside of Amazon Data Lifecycle Manager. Also, make sure that the lifecycle policy is in the enabled state.Updated schedule namesIf you change your lifecycle schedule name, then Data Lifecycle Manager doesn't delete snapshots that were created under the old schedule name. Be sure to delete any unwanted snapshots before you update your schedule name.Age-based retention policiesAn age-based retention policy deletes up to only the last snapshot from the standard and archive tiers. The policy doesn't delete the last snapshot. For example, you delete a volume or terminate an instance that's managed by an age-based retention policy. However, you still see an undeleted snapshot that's targeted by an age-based retention policy. You must use the Amazon Elastic Compute Cloud (Amazon EC2) console or AWS Command Line Interface (AWS CLI) to delete the last snapshot. It's a best practice to have a backup of the volume in case of a rollback.If Data Lifecycle Manager is turned off or in an error state, then snapshots and AMIs are retained from that period. This is true even if the snapshots and AMIs were set to expire during that time. Instead, you must manually delete the snapshots or deregister the AMIs.Count-based retention policiesIf you delete a volume or terminate an instance that's managed by a count-based retention policy, then the policy no longer manages the snapshots. You must use the Amazon EC2 console or AWS CLI to delete the snapshots. Also, if you modify or remove tags that are associated with your target resources, then Amazon Data Lifecycle Manager no longer manages the snapshot.After a count-based policy creates a snapshot and the retention number is already reached, the policy deletes the oldest snapshot. For example, you specify a count-based policy with a retention of 10. After the policy creates the 11th snapshot, the oldest snapshot is deleted. This is also true if you manually delete a snapshot that's created by a lifecycle policy with a count-based retention. Continuing the example, Amazon Data Lifecycle Manager waits until the policy creates the 11th snapshot to delete the oldest snapshot.

Related informationConsiderations for snapshot lifecycle policies
Question: How do I resolve the "Lambda could not update the function's execution role" error when attaching Amazon RDS Proxy to a Lambda function?

When I try to attach Amazon RDS Proxy to an AWS Lambda function, I get the following error message: "Lambda could not update the function's execution role". How do I resolve the error?Short descriptionLambda can return the Lambda could not update the function's execution role error for the following reasons:The Lambda execution role has more than one trusted entity associated with it.The Lambda function's execution role has 10 policies attached to it.The logged in AWS Identity and Access Management (IAM) user doesn't have "CreatePolicy" and "AttachRolePolicy" permissions.

ResolutionVerify that the Lambda function's execution role has only one trusted entity associated with itReview your function's execution role and verify that only the Lambda service (lambda.amazonaws.com) can assume the role.Note: To have the same role assumed by other services, create a new role and configure those services as its trusted entities.Verify that the Lambda function's execution role doesn't have 10 policies attached to itReview your function's execution role to determine whether there are 10 policies attached to it. If the role does have 10 policies attached to it, thencreate a single, custom policy to replace the existing ones.Note: If the execution role has 10 policies attached, then the Lambda function can't create and attach the required RDS Proxy policy to the role.Sample RDS Proxy policy{    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Action": "rds-db:connect",            "Resource": "Proxy ARN"        }    ]}Verify that the logged in IAM user has "CreatePolicy" and "AttachRolePolicy" permissionsReview the logged in IAM user's IAM policy and verify that the policy includes "CreatePolicy" and "AttachRolePolicy" permissions. If the user's policy doesn't include the required permissions, then grant the user "CreatePolicy" and "AttachRolePolicy" permissions.Note: If the logged in IAM user doesn't have the required permissions, then the Lambda console displays one or both of the following errors:"User <user-arn> is not authorized to perform: iam:CreatePolicy on resource: policy <policy-name>""User <user-arn> is not authorized to perform: iam:AttachRolePolicy on resource: role <role-name>"
Question: How do I change the language of emails that I receive from AWS?

I want to change the language preference for emails that I receive from AWS.

ResolutionTo customize your language preference for communications from AWS, do the following:Open the AWS Email Preference Center.Choose Email Signup & Preferences.For Email Address, enter your email address.Clear the box for any email types that you want to stop receiving.For Language Preference, choose your preferred language for communications from AWS.Choose Save your preferences.Within few minutes, you receive an email from AWS mentioning that your language preference is updated.

Related informationHow do I change the language of the AWS Management Console?
Question: How do I get more elastic network interfaces if I’ve reached the limit in an AWS Region?

I've reached the quota for elastic network interfaces in an AWS Region and I want to add more.

ResolutionYour quota for elastic network interfaces increases automatically as new instances are launched on the account. If you need more elastic network interfaces than are automatically provisioned to you, then do one or both of the following:Delete unused elastic network interfacesTo free up more elastic network interfaces, start by deleting any unused elastic network interfaces in that AWS Region:Sign in to your account and open the Network Interfaces pane of the Amazon Elastic Compute Cloud (Amazon EC2) console.(Optional) Detach any elastic network interfaces that you don't need from their resources.Select the elastic network interfaces that you want to delete.Choose Delete.Request a service quota for elastic network interfaces in a specific AWS RegionOpen the Service Quotas console.Choose AWS Services, search for VPC, and then select Amazon Virtual Private Cloud (Amazon VPC).Choose Network Interfaces per Region, and then choose Request quota increase.For Change quota value, enter the number of elastic network interfaces that you need.Complete the remaining fields.Choose Request.(Optional) If you need more elastic network interfaces in more than one AWS Region, change the Region using the dropdown list at the top of the console. Repeat steps 1 through 6 in the new Region.

Related informationElastic network interfacesRequesting a quota increase
Question: How do I troubleshoot issues with invoking a Lambda function with an Amazon S3 event notification using Systems Manager Automation?

My Amazon Simple Storage Service (Amazon S3) event notification doesn't invoke my AWS Lambda function. Or, I receive an error when I try to create an Amazon S3 event notification to invoke my Lambda function. Can I use AWS Systems Manager Automation to troubleshoot Amazon S3 event notification issues with Lambda?Short descriptionTo troubleshoot issues when sending Amazon S3 event notifications to Lambda, use the AWSSupport-TroubleshootLambdaS3Event Systems Manager Automation runbook.The runbook verifies if an event configuration exists for the Lambda function and Amazon S3 bucket parameter values that you enter. If an event configuration exists, then the runbook verifies that the configuration, resource policies, and permissions are correct. The runbook's output provides AWS Command Line Interface (AWS CLI) commands that allow you to add the required resource policies or permissions.Note: If the Amazon S3 event notification is no longer needed, then it's a best practice to delete the event notification.Resolution1.    Open the AWS Systems Manager console.2.    In the navigation pane, under Change Management, choose Automation.3.    Choose Execute automation.4.    In the Owned by Amazon tab, in the Automation document search box, enter and search for AWSSupport-TroubleshootLambdaS3Event.5.    Select the check box in the upper right of the AWSSupport-TroubleshootLambdaS3Event card. Then, choose Next.6.    In the Input parameters section, do the following:For AutomationAssumeRole, enter an AWS Identity and Access Management (IAM) role for the runbook to assume that includes lambda:GetPolicy and s3:GetBucketNotification permissions.For LambdaFunctionArn, enter the Lambda function's Amazon Resource Name (ARN).For S3BucketName, enter the Amazon S3 bucket's name.7.    Choose Execute.Note: If the output suggests validating and configuring your Lambda function concurrency, see Asynchronous invocation and AWS Lambda function scaling.

Related informationWhy doesn't my Amazon S3 event notification invoke my Lambda function?Why do I get the error "Unable to validate the following destination configurations" when creating an Amazon S3 event notification to invoke my Lambda function?
Question: How do I remove the restriction on port 25 from my Amazon EC2 instance or AWS Lambda function?

I'm having trouble sending email over port 25 from my Amazon Elastic Compute Cloud (Amazon EC2) instance or AWS Lambda function.

ResolutionAWS blocks outbound traffic on port 25 (SMTP) of all EC2 instances and Lambda functions by default. If you want to send outbound traffic on port 25, you can request for this restriction to be removed.To remove the port 25 restriction on your Lambda function, associate your function with an Amazon Virtual Private Cloud (Amazon VPC). Then, give internet access to your Lambda function using a network address translation (NAT) gateway. The port 25 restriction can't be removed from non-VPC functions.After you complete this task, request AWS to remove the port 25 restriction on either your EC2 instance or your NAT gateway by following these steps:Sign in with your AWS account, and then open the Request to remove email sending limitations form.Enter your email address so that AWS Support can contact you with updates about your request.Provide the required information in the Use case description field:A clear and detailed use case for sending email from your EC2 instance or NAT Gateway.A statement outlining your plan for assuring that your account isn't implicated in sending unwanted emails.The Region for your EC2 instance or NAT Gateway.(Optional) Provide the AWS owned Elastic IP addresses that you use to send outbound emails as well as any reverse DNS (rDNS) records that AWS needs to associate with the Elastic IP addresses. When you send emails, it's a best practice to set up an rDNS record to help prevent outbound emails from being flagged as spam.Make sure to link the rDNS record to your Elastic IP address using a DNS A record. For example, if mail.example.com is the rDNS record that you're setting, be sure that you create an A record for mail.example.com that points to the Elastic IP address.Choose Submit.Note: If you have instances in more than one Region, then submit a separate request for each Region. If you have instances in a single Region a request needs to be submitted once for only that Region. If you have instances in more than one Region, then submit a separate request for each Region.You receive an email with the Request ID after submitting the request form. It might take up to 48 hours to process your request. If your request is approved, you receive an email to notify you that the port 25 restriction is removed. If you don't receive an update within 48 hours after submitting the request, reply to the initial email that you received.Note: It's a best practice to use Amazon Simple Email Service (Amazon SES) instead of sending emails directly from your resources. Email providers can block cloud IP ranges, preventing delivery of emails sent directly from your resources.

Related informationConnecting to an Amazon SES SMTP endpointHow do I remove the restriction on port 25 from my Lightsail instance?
Question: How do I troubleshoot a “No endpoints available” error in the DAX client?

I received a "No endpoints available" error in Amazon DynamoDB Accelerator (DAX).

Short descriptionThe "No endpoints available" error occurs when the client doesn't have a network route to any nodes of the DAX cluster. This error might also occur when a cluster is down or experiencing high CPU utilization.Here are some example cases that might result in this error:A failed health check to DAX nodes: The client can't perform a health check on cluster nodes because of high CPU load from the nodes.Multiple consecutive I/O Exceptions to each node: The DAX client counts the number of I/O Exceptions to determine if a server node is down. The client retrieves a list of server nodes from the configuration endpoint. If it receives more than five failures from a server node, then the client removes the node from the list of active server nodes. If all server nodes are removed in this way, then the client ends up with an empty list of active nodes. In response, the client shows a "No endpoints available" error.

ResolutionTo resolve the error, use the following troubleshooting steps:In the DAX client, there's a thread to refresh the list of active server nodes. To restore your active nodes in the list, use the refresh option.Increase the RequestTimeout based on the client's traffic pattern. For more information, see Tuning AWS Java SDK HTTP request settings for latency-aware Amazon DynamoDB applications.Increase the health check interval. By default, the health-check-interval is 5 seconds.Note: Increasing this interval puts the endpoint back into the client-side endpoint set only when it's removed because of a socket-timeout-exception.To reduce the reoccurrence of this error, scale up to a larger instance type. Or, add more nodes to the cluster to scale out.This error is more likely to occur with single node clusters. If your cluster has only one node, then scale out the cluster. Place each node in a different Availability Zone.

Related informationClientConfig (DAX)
Question: How do I identify who disconnected a call in my Amazon Connect contact center?

I want to know the reason why calls with agents in my Amazon Connect contact center are disconnected. I want to see if the customer or the agent disconnected a call.

ResolutionLog in to Amazon Connect with a user account that has permissions to search for contacts.Choose Metrics and quality, and then choose Contact search.On the Contact search page, use the filters to search for your contact, and then choose Search.In the Contact ID column of the search results, choose the contact ID of the contact that you're investigating the disconnect reason for.On the Contact Trace Record page for your contact, find the field Disconnect reason.Now, you can see the reason why your contact was disconnected. For more information on disconnect reasons, see the "DisconnectReason" entry for ContactTraceRecord.Note: The disconnect reason that you see on the Contact Trace Record page doesn't always align with the exact wording of the documented disconnect reasons. For example, CUSTOMER_DISCONNECT appears as Customer disconnect on the Contact Trace Record page.
Question: How do I prepare for consolidated controls view and consolidated control findings?

I'm using AWS Security Hub to run security checks against controls and generate control findings. I want to prepare for new, upcoming features that will affect how I view and receive control findings.

Short descriptionAWS Security Hub identifies security controls and generates control findings in the context of security standards. In early 2023, Security Hub will release two features that decouple controls from standards. The new features also streamline how you view and receive control findings:Consolidated controls viewConsolidated control findingsAfter the release of consolidated controls view, you'll see a consolidated list of your controls from the new Controls page in the Security Hub console. Security Hub will also assign controls a consistent security control ID across standards. This helps you to investigate failed findings that affect multiple compliance frameworks.Consolidated control findings will streamline your control findings. When this feature is turned on, Security Hub produces a single finding for a security check even when a check is shared across multiple standards. This reduces finding noise and helps you focus on the security issues affecting your environment.Note: Both features will bring changes to control finding fields and values in the AWS Security Finding Format (ASFF).

ResolutionIf your workflows don’t rely on the specific format of any control finding fields, no action is required to prepare for these feature releases. It's a best practice to immediately turn on consolidated control findings.If you're using the Automated Security Response on AWS solution for predefined response and remediation actions, it's a best practice to wait to make changes. This feature doesn't support consolidated control findings at this time. If you turn on consolidated control findings, actions you deployed using the Automated Security Response solution will no longer work.If you rely on the specific format of any control finding fields (such as custom automation), review the upcoming finding field and value changes. Confirm that your workflows will continue to function as intended. For more information and examples, see How to prepare for control finding field and value changes.If you created custom insights by using the control finding fields or values that will change, it's a best practice to update those insights to use the new fields or values.For more information, including generator IDs, control titles, and complete example findings before and after the releases, see Upcoming features: consolidated controls view and consolidated control findings.