VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How can I set up VMware High Availability on my file gateway?

I created a file gateway on AWS Storage Gateway. My file gateway uses VMware ESXi as the host platform. I want to configure VMware High Availability (HA) on my file gateway.

ResolutionLog in to the vSphere Web Client. For more information, see Log in to vCenter Server using the vSphere Web Client on the VMware vSphere Documentation Center.From the navigation pane, choose Cluster.Choose the Configure tab.From the cluster's navigation pane, choose VM Overrides. Then, choose Add.In the Add VM Override Cluster dialog box, for Select a VM, select your file gateway. Then, choose Next.For Add VM Override, under vSphere HA - VM Monitoring, select the check box for Override. Then, confirm that VM and Application Monitoring is selected.Choose Finish.From the cluster's navigation pane, choose vSphere Availability. Then, choose EDIT.In the Edit Cluster Settings dialog box, for VM Monitoring, select VM and Application Monitoring. Then, choose OK.To test the VMware HA configuration on your file gateway, do the following:Copy test files to a file share from your file gateway that's mounted on your client.While the copy job is in progress, go back to the vSphere Web Client.From the navigation pane, open the context (right-click) menu for your file gateway, and then choose Power, Restart Guest OS.In the Confirm Guest Restart dialog box, choose YES.Restarting the guest OS pauses the transfer. After your gateway is back online, confirm that your copy job resumes.
Question: How can I find the AWS VAT number?

How can I find the AWS VAT number?ResolutionIf your account is with AWS Europe (Amazon Web Services EMEA SARL), then the AWS VAT number appears in the footer of your VAT invoice.Note: If you're a linked account and can't access VAT invoices, then contact the AWS account root user or account administrator and ask that they retrieve the invoices for you.In some countries, the VAT invoice footer includes the VAT number of both the AWS Europe headquarters in Luxembourg and the AWS Europe branch, if required.Note: AWS Europe branches are the same legal entity as AWS Europe in Luxembourg, but each branch has its own local VAT number. All VAT collected is reported to the local tax authorities on the local VAT return of the branch or headquarters.For more information on AWS VAT policies and procedures, see AWS Tax Help.If you have further questions about how VAT applies to your AWS usage or the AWS VAT number that you should use, consult your tax advisor.

Related informationVAT questions
Question: How can I optimize performance when I upload large amounts of data to Amazon S3?

I am uploading a large amount of data to Amazon Simple Storage Service (Amazon S3), or copy a large amount of data between S3 buckets. How can I optimize the performance of this data transfer?ResolutionConsider the following methods of transferring large amounts of data to or from Amazon S3 buckets:Parallel uploads using the AWS Command Line Interface (AWS CLI)Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.To potentially decrease the overall time that it takes to complete the transfer, split the transfer into multiple mutually exclusive operations. You can run multiple instances of aws s3 cp (copy), aws s3 mv (move), or aws s3 sync (synchronize) at the same time.One way to split up your transfer is to use --exclude and --include parameters to separate the operations by file name. For example, you want to copy a large amount of data from one bucket to another bucket. In this example, all of the file names begin with a number. You can run the following commands on two instances of the AWS CLI.Note: The --exclude and --include parameters are processed on the client side. Because of this, the resources of your local machine might affect the performance of the operation.Run this command to copy the files with names that begin with the numbers 0 through 4:aws s3 cp s3://srcbucket/ s3://destbucket/ --recursive --exclude "*" --include "0*" --include "1*" --include "2*" --include "3*" --include "4*"Run this command to copy the files with names that begin with the numbers 5 through 9:aws s3 cp s3://srcbucket/ s3://destbucket/ --recursive --exclude "*" --include "5*" --include "6*" --include "7*" --include "8*" --include "9*"Important: If you must transfer a large number of objects (hundreds of millions), consider building a custom application using an AWS SDK to perform the copy. While the AWS CLI can perform the copy, a custom application might be more efficient at that scale.AWS SnowballConsider using AWS Snowball for transfers between your on-premises data centers and Amazon S3, particularly when the data exceeds 10 TB.Note the following limitations:AWS Snowball doesn't support bucket-to-bucket data transfers.AWS Snowball doesn't support server-side encryption with keys managed by AWS Key Management System (AWS KMS). For more information, see Encryption in AWS Snowball.S3DistCp with Amazon EMRConsider using S3DistCp with Amazon EMR to copy data across Amazon S3 buckets. S3DistCp enables parallel copying of large volumes of objects.Important: Because this option requires you to launch an Amazon EMR cluster, be sure to review Amazon EMR pricing.

Related informationRequest rate and performance guidelines
Question: How can I resolve the errors "Daemon socket connection error" or "Invalid Operation" for my CloudHSM client?

I am attempting to connect to the key management utility (KMU) command line tool or the AWS CloudHSM client, and receive the error "Daemon socket connection error" or "Invalid Operation".

Short descriptionCloudHSM Client software uses a client daemon to connect and perform operations on the HSM using the KMU command line tool. These errors occur if:The client daemon is stopped.-or-The client configuration file doesn't contain the IP address of an active and reachable HSM in the cluster.

ResolutionFollow the instructions for troubleshooting lost connections to the cluster.Note: This resolution is for use only with Client SDK 3, not Client SDK 5. For more information, see Using the AWS CloudHSM Client SDK.

Related informationTroubleshooting AWS CloudHSMWhich CloudHSM certificates are used for the client-server end-to-end encrypted connection?How do I restore a CloudHSM cluster from a previous backup?
Question: Why did my Lambda Amazon SQS trigger get disabled?

I configured my AWS Lambda function to process messages in an Amazon Simple Queue Service (Amazon SQS) queue but the SQS trigger is not active.

Short descriptionYou can use a Lambda function to process messages in an Amazon SQS queue. Event source mapping reads from an event source and invokes a Lambda function. The state of the event source mapping are either Creating, Enabling, Enabled, Disabling, Disabled, Updating, or Deleting.Lambda pollers constantly make the ReceiveMessage API action call to the Amazon SQS queue. If the ReceiveMessage API call doesn't complete, then the EventSourceMapping resource is disabled.

ResolutionLambda function permissionsMake sure that your Lambda function execution role has access to the following permissions:ChangeMessageVisibilityDeleteMessageGetQueueAttributesReceiveMessageAWS Key Management Service (AWS KMS) permissionsIf the Amazon SQS queue is configured with SSE-KMS encryption, make sure that:The AWS KMS key exists.The Lambda function execution role has permissions for Encrypt, Decrypt, and GenerateDataKey.The AWS KMS key policy permissions are configured to allow events to send to Amazon SQS queues.Note: Amazon SQS queues with SSE-KMS encryption can't invoke a Lambda function in a different AWS account (cross-account).CloudTrail event historyYou can use AWS CloudTrail to look up events. CloudTrail is turned on by default for your AWS account.For an ongoing record of events in your AWS account, create a trail. Using a trail, CloudTrail creates logs of API calls made on your account. These logs are delivered to an Amazon Simple Storage Service (Amazon S3) bucket that you specify. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in Event history.1.    Open the CloudTrail console.2.    In the navigation pane, choose Event history.3.    Follow the instructions for viewing, displaying, and filtering CloudTrail events for your use case.You can also download recorded event history as a file in CSV or JSON format.Check for the CloudTrail event name LambdaESMDisabled. The event log contains the parameter ESMDisableReason with more information on the cause of why the Amazon SQS trigger's is not active.For more information, see Logging Lambda API calls with CloudTrail.Amazon CloudWatch alarms (optional)You can create a CloudWatch alarm for Amazon SQS metrics to get notified on the number of messages received, sent, deleted, and so on. For example, you can use the Amazon SQS metric NumberOfMessagesReceived to get the number of recent messages returned. If the count is 0, then invoke a new Lambda function to check the status of the Amazon SQS trigger. If the Amazon SQS trigger is still disabled, then use the new Lambda function to activate it.For more information, see Available CloudWatch metrics for Amazon SQS.

Related informationWhat permissions do I need to access an Amazon SQS queue?How do I troubleshoot Lambda function failures?
Question: Can I schedule my EC2 Reserved Instance to renew automatically?

I want to schedule my Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instance (RI) to renew automatically.

ResolutionYou can queue your Reserved Instance purchases for a specific date and time in the future. To renew your EC2 RI automatically, you can queue an RI purchase for the date and time that your existing RI expires. On the scheduled date and time, AWS automatically purchases the RI for you using your account's default payment method. For more information, see Queuing your purchase.To view your active RIs and see when they expire, check the Amazon EC2 console. You can also set reservation expiration alerts to remind you when your RIs are about to expire. However, reservation expiration alerts don't automatically renew RIs, or purchase new RIs for you. You can queue your RI purchases to ensure uninterrupted coverage.Note: EC2 RIs impact only the price of EC2 instances on your account. When an EC2 RI expires, it doesn't cause any instances to shut down or terminate.

Related informationAmazon EC2 Reserved InstancesHow do I tell if my EC2 Reserved Instances are being used?How to Purchase Reserved Instances
Question: How can I route traffic based on a custom HTTP header using an Application Load Balancer?

I want to use an Application Load Balancer to perform a specific action on requests based on the value of a custom HTTP header.

ResolutionCreate an Application Load Balancer.Open the Amazon Elastic Compute Cloud (Amazon EC2) console.On the navigation pane, under Load Balancing, choose Load Balancers.Select your load balancer.Choose the Listeners tab.Select your listener, and then from the Actions dropdown, choose View listener details.Under Rules, choose Manage rules.Choose the Add rules icon (the plus sign), and then choose Insert rule.Choose Add condition, and then choose Http header.Specify a header name based on the desired action. For example, "Accept."Note: The maximum size of each header name is 40 characters. The header name isn't case sensitive. Wildcards aren't supported.Specify the values (comparison strings) of the custom header.Note: The maximum size of each comparison string is 128 characters. The comparison string isn't not case sensitive. The asterisk (*) and question mark (?) wildcard characters are supported.Choose Add action, and then select the required action. For example:Forward – To forward to a different target group.Redirect to - To redirect to a different URL.Return fixed response – To block or provide a custom response to particular clients based on the value of custom header.Choose Save.

Related informationListener rules for your Application Load Balancer
Question: Why do I have running EC2 instances that I didn't launch?

I have instances running in the Amazon Elastic Compute Cloud (Amazon EC2) console that I don't remember launching, and I want to remove them.

ResolutionDetermine whether another AWS service or an authorized user on your AWS account launched the Amazon EC2 instances.Determine whether another AWS service launched the instancesYou can configure some AWS services to launch EC2 instances as part of their function. The following list includes some services that commonly launch instances. Check these services to determine whether they launched any instances:AWS CloudFormation: You can configure a CloudFormation template to launch one or more instances on as part of a stack. For more information, see What is AWS CloudFormation? To delete the stack and all its resources, see Deleting a stack on the AWS CloudFormation console.AWS Elastic Beanstalk: Elastic Beanstalk environments include EC2 instances and Auto Scaling rules by default. Depending on their configuration, an environment's Auto Scaling rules might launch instances. For more information, see What Is Elastic Beanstalk? To terminate an environment and all its resources, see Terminate an Elastic Beanstalk environment.AWS OpsWorks: AWS OpsWorks stacks can launch groups of AWS resources according to the instructions in the stack's cookbook. If you launch an OpsWorks stack, then the cookbook might be configured to launch EC2 instances as part of the stack. To terminate the resources that are associated with a stack, delete the stack.Amazon EMR: Amazon EMR lets you launch clusters and nodes that are groups of EC2 instances. To terminate the instances that are associated with an Amazon EMR cluster, terminate the cluster.Note: Terminating resources in your account might require additional steps. For more information, see How do I terminate active resources that I no longer need on my AWS account?If you're charged for EC2 instances that you previously terminated, then see Why am I being charged for EC2 when all my instances have been terminated? Also, see Why am I charged for Elastic IP addresses when all my Amazon EC2 instances have been terminated?Determine whether other authorized users launched the instancesUse AWS CloudTrail to look for instances of the RunInstances API call. Or, check with other authorized account users to determine whether they launched instances.Note: To manage which account users can launch instances or use AWS services, use AWS Identity and Access Management (IAM).
Question: How do I troubleshoot "ThrottlingException" and "Rate exceeded" errors in Amazon SNS?

When I use an Amazon Simple Notification Service (Amazon SNS) API action, I get a "ThrottlingException" error. The error message says "Rate exceeded." Why am I receiving these errors and how do I resolve them?Short descriptionAmazon SNS API calls can't exceed the maximum allowed API request rate for each AWS account and Region. If API requests exceed this API throttling quota, further API calls are throttled and Amazon SNS returns a ThrottlingException error.To prevent or mitigate ThrottlingException errors in Amazon SNS, you can implement one or more of the best practices outlined in this article.Amazon SNS ThrottlingException error message examples"An error occurred (ThrottlingException) when calling the Subscribe operation: Rate exceeded""An error occurred (ThrottlingException) when calling the ListOriginationNumbers operation: Rate exceeded""An error occurred (ThrottlingException) when calling the ListPhoneNumbersOptedOut operation: Rate exceeded""An error occurred (ThrottlingException) when calling the publish operation: Rate exceeded""An error occurred (ThrottlingException) when calling the GetSMSAttributes operation: Rate exceeded"Note: Amazon SNS API calls are throttled to improve service performance. For more information about Amazon SNS API throttling quotas, see Amazon SNS endpoints and quotas.

ResolutionBest practices for preventing ThrottlingException errors in Amazon SNSReduce the frequency of the API calls.Stagger the intervals of the API calls.Implement error retries and exponential backoff.If you still receive ThrottlingException errors after implementing these best practices, request a service quota increase for the API action that's receiving the error.To request an Amazon SNS service quota increaseFollow the instructions in AWS service quotas. When you enter your Use case description, make sure that you include the time frame of the throttling issue and the reason for the quota increase request.Important: You can request service quota increases for Soft Amazon SNS quotas only. You can't increase Hard Amazon SNS quotas. For more information, see Amazon SNS endpoints and quotas.
Question: Does using the IAM Identity Center affect my IAM identities or federation configuration?

I want to use the AWS IAM Identity Center (successor to AWS Single Sign-On) to provide access for users to our AWS accounts and applications. I want to know if using the IAM Identity Center affects my AWS Identity and Access Management (IAM) identities (users, groups, and roles).

Short descriptionYou can use the IAM Identity Center or IAM to federate your workforce into AWS accounts and applications.IAM federation allows you to activate a separate SAML 2.0 or an OIDC IdP for each AWS account and user attributes for access control. You can use identity providers instead of creating IAM users in your AWS account. For more information, see Identity providers and federation.IAM Identity Center uses IAM service-linked roles. You don't have to manually add permissions with service-linked roles. For more information, see Using service-linked roles for IAM Identity Center.

ResolutionThe IAM Identity Center is independent of identity federation configured using IAM. Using the IAM Identity Center doesn't impact IAM identities or your federation configuration.The IAM Identity Center uses the service-linked role AWSServiceRoleForSSO to grant permissions to manage AWS resources. The AWSServiceRoleForSSO role created in AWS accounts only trusts the IAM Identity Center service that's similar to the following IAM trust policy:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Principal": {        "Service":"sso.amazonaws.com"      },      "Action": "sts:AssumeRole"    }  ]}The IAM roles created by the service-linked role AWSServiceRoleForSSO have an IAM trust policy that's similar to the following:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Principal": {        "Federated": "arn:aws:iam::AWS-account-ID:saml-provider/AWSSSO_ec48a2d3f5dc369d_DO_NOT_DELETE"      },      "Action": "sts:AssumeRoleWithSAML",      "Condition": {        "StringEquals": {          "SAML:aud": "https://signin.aws.amazon.com/saml"        }      }    }  ]}Note: This IAM policy only trusts the SAML provider created automatically by the IAM Identity Center.With IAM federation, you must manually create IAM roles in your AWS accounts using a trust policy that's similar to the following:{  "Version": "2012-10-17",  "Statement": [{    "Effect": "Allow",    "Principal": {"Federated": "arn:aws:iam::ACCOUNT-ID-WITHOUT-HYPHENS:saml-provider/MYIDP"},    "Action": "sts:AssumeRoleWithSAML",    "Condition": {"StringEquals": {      "saml:edupersonorgdn": "ExampleOrg",      "saml:aud": "https://signin.aws.amazon.com/saml"    }}  }]}Note: Only IAM entities in your organization with this policy attached are able to access your AWS accounts.To configure the IAM identity Center, see How do I get started with using IAM Identity Center and access the AWS access portal?Related informationHow to create and manage users within AWS IAM Identity CenterHow do I assign user access to cloud applications in the IAM Identity Center?How do I use IAM Identity Center permission sets?Identity federation in AWS
Question: How do I troubleshoot load balancer errors for Amazon ECS tasks on Fargate?

I'm getting load balancer errors with my Amazon Elastic Container Service (Amazon ECS) task on AWS Fargate.

ResolutionCheck AWS Identity and Access Management (IAM) permissionsThe ecsServiceRole role allows Amazon ECS services to register Amazon ECS containers on Fargate with the load balancer.Confirm that you have the correct ElasticLoadBalancer permissions. For more information, see Service Scheduler IAM Role.Check your container security group ingress rulesIf your container is mapped to port 80, then your container security group must allow inbound traffic on port 80 for the load balancer health checks to pass.Configure your load balancer for all the Availability Zones of the serviceConfigure your load balancer to use all the Availability Zones in an AWS Region, or at least all the Availability Zones for your containers.If a service uses a load balancer and starts a task located in an Availability Zone that the load balancer isn't configured to use, then the task never passes the health check and the task is stopped.Check if your load balancer health check is configured correctlyThe load balancer health check parameters can be too restrictive or point to resources that don't exist. Unhealthy tasks are removed from the load balancer.Confirm that the following parameters are configured correctly for your service load balancer:Ping PortPing PathResponse TimeoutHealth Check IntervalUnhealthy ThresholdFor more information, review the Elastic Load Balancing load balancer health check misconfigured section of Troubleshooting service load balancers.For more information on health check failures caused by load balancers, see How do I troubleshoot health check failures for Amazon ECS tasks on Fargate?
Question: Why can't I find an Amazon EC2 instance that I launched on my account?

I launched an Amazon Elastic Compute Cloud (Amazon EC2) instance, but I can't see it in the Amazon EC2 console.

ResolutionYou can use the AWSSupport-ListEC2Resources AWS Systems Manager Automation document to list your active EC2 resources. This automation document returns information on EC2 instances and related resources. These resources can be Amazon Elastic Block Store (Amazon EBS) volumes, Elastic IP addresses, or Amazon EC2 Auto Scaling groups from specified AWS Regions. By default, the information is gathered from all Regions and appears in the output. To run this automation, follow the instructions in Run an automation.The following are some common reasons why you might not see an EC2 instance in the console:The instance is running, but the console is set to a different Region: Because each EC2 instance is launched in a specific Region, you can view only one Region at a time in the console. Be sure that you select the correct Region based on the output of the automation document.Another account user shut down or terminated the instance: If you don't see the EC2 instance in the automation document, then check with other users of your account to see if they terminated the instance.The instance is running on another AWS account: If you don't see the EC2 instance in the output of the automation document, then run the automation on your other AWS accounts to find the instance.The instance was running, but a process or service shut down the instance: If you don't see the EC2 instance in the output of the automation document, then a process or service might have terminated the instance. Some AWS services, such as AWS Auto Scaling, AWS Elastic Beanstalk, Elastic Load Balancing, or AWS Lambda, can start, stop, and terminate instances automatically. For more information, see the service documentation.The instance was launched as a Spot Instance, and the current Spot price exceeds your bid: If you don't see your Spot Instance in the output of the automation document, then it's possible that the Spot instance was terminated. Spot Instances terminate automatically when your bid price is lower than the current Spot price. For current Spot prices, see Amazon EC2 Spot Instances pricing.

Related informationWhy do I have running EC2 instances that I didn't launch?What do I do if I receive a bill from AWS but can't find the resources related to the charges?