VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I launch an Amazon EC2 instance with my AWS Marketplace subscription?

I have subscribed to an AWS Marketplace product. I want to know how to launch Amazon Elastic Compute Cloud (Amazon EC2) instances using this subscription.

ResolutionYou can launch an EC2 instance from the AWS Marketplace console or directly from the AWS Marketplace.Launch an instance from the AWS Marketplace consoleOpen the AWS Marketplace console.Choose Manage subscriptions.Note: On the Manage subscriptions page, you can view all the product subscriptions on your account.Choose Manage next to the product that you want to launch an instance with, and then choose Actions.Choose Launch new instance.On the Configure this software page, select the required Delivery method, Software version, and Region, and then choose Continue to launch through EC2.You are redirected to the Amazon EC2 console.In the Choose an Instance Type page, select the required instance type, and then choose Next: Configure Instance Details.After you configure the instance, add storage, add tags, and then configure security groups, you can see the Review Instance Launch page.Review the instance details, and then choose Launch.Launch an instance using 1-Click LaunchSign in to AWS Marketplace.Choose the software subscription where you want to launch your instances.On the Launch on EC2 page, choose 1-Click Launch.Review the default settings for Version, Region, EC2 Instance Type, and Firewall Settings, and then update as needed.Expand Key Pair, and then choose an existing key pair or create a new one.Choose Accept Terms & Launch with 1-Click.Launch an instance using launch with EC2 ConsoleSign in to AWS Marketplace.Choose the software subscription where you want to launch your instances.On the Launch on EC2 page, choose Launch with EC2 console.Select an AMI version from the list.Review the default settings for Firewall Settings, Installation Instructions, and Release Notes, and then update as needed.Choose Launch with EC2 console.You are redirected to the Amazon EC2 console.Launch your instance by following the instructions in Getting started with Amazon EC2 Linux instances.The instance might take a few minutes to launch depending on your product subscription. You're charged the subscription price for all your running instances. If your instance is stopped, you might still be charged for storage.

Related informationLaunching softwareGetting started as a buyer in the AWS MarketplaceAWS Marketplace Help and FAQ
Question: "Why isn’t the Start menu, Action Center, or Cortana Search responding after I rebuilt my Windows 10 WorkSpace?"

My Start menu, Action Center, or Windows Search isn't working after rebuilding my Amazon WorkSpaces Windows 10 WorkSpace. How can I fix this?Short descriptionWhen you rebuild a WorkSpace, a new WorkSpace is created from the custom bundle. However, the D:\ drive, which contains the user profile, restores from the latest Amazon Elastic Block Store (Amazon EBS) snapshot of the volume. The user profile's TileDataLayer database is closely integrated with the Start menu, Action Center, and Cortana Search. A WorkSpace rebuild can create a mismatch between the information that the new Operating System has and the modified database within the user profile.This issue can affect WorkSpaces that are launched or rebuilt from a custom bundle created before May 2019.Your Windows 10 WorkSpace might exhibit one of the following symptoms because of the information mismatch:Choosing the Windows Start menu doesn’t produce any effect.Choosing Windows Action Center doesn’t produce any effect.Windows Search doesn’t open from the taskbar.

ResolutionRepair Search functionality1.    Connect to the WorkSpace from another user account using Remote Desktop Protocol (RDP).2.    Navigate to the following location within the assigned user’s profile: D:%userprofile%\Appdata\local\packages3.    Delete the Microsoft.Windows.Cortana_cw5n1h2txyewy folder.4.    Reboot the WorkSpace.5.    Connect to the WorkSpace using the Amazon WorkSpaces client.6.    Open Windows PowerShell as administrator, and then run the following command:Get-AppXPackage -AllUsers -Name Microsoft.windows.cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}Expected output:VERBOSE: Performing the operation "Register package" on target "C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppXManifest.xml".VERBOSE: Operation completed for: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppXManifest.xmlSearch functionality resumes immediately.Repair Start menu and Action Center functionality1.    Navigate to the following location within the assigned user’s profile: D:%userprofile%\AppData\local\packages2.    Delete the Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy folder.3.    Open Windows PowerShell as administrator, and then run the following command:Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\AppXManifest.xml"}Start menu functionality resumes immediately.Custom bundleIf you use a custom bundle, be sure to update the bundle for future rebuilds.

Related informationWhy isn't the Start menu, Action Center, or Cortana Search responding after I rebuilt my Windows 10 BYOL WorkSpace?
Question: How do I use Overview details to access my AWS DMS task information?

How can I use the Overview details section to view and access my AWS Database Migration Service (AWS DMS) task information?ResolutionNote: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.Open the AWS DMS console.Choose Database migration tasks from the navigation pane.Choose the name of your task, and then review the Overview details section.The Overview details section contains information about your task. This includes the basic configuration, such as Task ARN, Status, Migration type, Last failure message, Migration task logs, and Task settings. For more information, see Monitoring AWS DMS tasks.You can modify a task to change the table mapping, task settings, or other properties. For example, to modify the target table preparation mode, choose the task in the AWS DMS console, and then choose Modify.To modify other task settings, such as logging, use the AWS CLI to modify a replication task. For more information, see Specifying task settings for AWS Database Migration Service tasks.

Related informationHow can I monitor an AWS DMS task?
Question: How do I diagnose high CPU utilization on an EC2 Windows instance?

My Amazon Elastic Compute Cloud (Amazon EC2) Windows instance is experiencing high CPU utilization, and I want to understand why.

ResolutionFirst, determine your Amazon EC2 instance type to identify the correct resolution:Open the Amazon EC2 console, and then choose Instances from the navigation pane.Select the instance that you want to troubleshoot. On the Description tab, note the Instance type.(T2 or T3 instances only) For Actions, choose Instance Settings, Change T2/T3 Unlimited. Note whether T2/T3 Unlimited is enabled or disabled.Follow the instructions in the section below that corresponds to your instance type and use case.After you determine the specific process causing high CPU utilization, you can troubleshoot that application.T2/T3 Unlimited is disabled on my T2 or T3 instance, and I'm not sure if my CPU is being throttledYou can check the CPU Credit Balance and the CPU within the operating system (OS) to verify if your CPU is being throttled. For instructions, see How can I find out if the CPU on my T2 or T3 EC2 Windows instance is being throttled?T2/T3 Unlimited is disabled on my T2 or T3 instance, and I know that my CPU is being throttledIf your CPU is throttled, you can either activate T2/T3 Unlimited, or change the instance type. For more information, see How can I resolve high CPU utilization on my T2 or T3 EC2 Windows instance if my CPU is being throttled?T2/T3 Unlimited is enabled on my T2 or T3 instance-or-My T2 or T3 instance isn't being throttled, and I need help with investigating at the OS level-or-My instance type isn't T2 or T3When CPU throttling isn't the source of the problem, you can investigate at the OS level. For instructions, seeHow do I diagnose high CPU utilization on my EC2 Windows instance when my CPU is not being throttled?Related informationAmazon EC2 instance typesWhat steps do I need to take before changing the instance type of my EC2 Linux instance?
Question: How can I configure CloudFront to forward the Authorization header to the origin?

The origin of my Amazon CloudFront distribution requires that requests include the Authorization header. Because of this, my distribution must forward the Authorization header to the origin.

Short descriptionConfigure your distribution to forward the Authorization header to the origin in one of these ways:Create a cache policy. Then, associate the cache policy with the cache behavior that must forward the Authorization header.Note: You can't use an origin request policy to forward the Authorization header. The header must be a part of the cache key to prevent the cache from satisfying unauthorized requests. CloudFront returns an HTTP 400 error if you create an origin request policy that forwards the Authorization header.Edit an existing cache behavior with legacy cache settings.Important: For Amazon Simple Storage Service (Amazon S3) origins, caching based on the Authorization header isn't supported. For more information, see Selecting the headers to base caching on.

ResolutionCreate a cache policyFollow the steps to create a cache policy using the CloudFront console.Under Cache key settings, for Headers, choose Include the following headers. Then, under Add Headers, select Authorization.Complete all other settings of the cache policy based on the requirements of the behavior that you're attaching the policy to. Then, choose Create.After you create the cache policy, follow the steps to attach the policies to the relevant behavior of your CloudFront distribution.Edit an existing cache behavior with legacy cache settingsOpen the CloudFront console, and then choose your distribution.Choose the Behaviors tab, and then select the path that you want to forward the Authorization header to.Choose Edit.Under Headers, choose Include the following headers. Then, under Add Headers, select Authorization.Choose Save changes.
Question: Why did my Secrets Manager Lambda function rotation fail with a “pg module not found“ error?

My AWS Secrets Manager AWS Lambda function failed with a “pg module not found“ error in Amazon CloudWatch Logs.

Short descriptionYou might receive this error if you're running an earlier Lambda function that was automatically upgraded from Python 3.7 to a newer version of Python.

ResolutionChange the Lambda function version back to Python 3.7, and redeploy the Lambda function.Check the Lambda function Python version1.    Open the Lambda console.2.    In the navigation pane, choose Functions, and then select the Lambda function name that failed to rotate.3.    Choose the Code tab.4.    In Runtime settings, note the Python version.5.    Choose Actions, choose Export function, and then choose Download deployment package.6.    Run the following Linux find command from the directory of the uncompressed .zip file:find ./ -name “*cpython-*-x86_64-linux-gnu.so”7.    Check that the version of the Python runtime is in the name of the .so file. For example _cffi_backend.cpython-37m-x86_64-linux-gnu.so.If the .so version isn't Python 3.7, then Lambda can't import the library.Modify the AWS Cloudformation templateTo resolve the Lambda function failure, modify the CloudFormation template that you used to create the Lambda function. Add the Runtime property to the HostedRotationLambda object in AWS::SecretsManager::RotationSchedule. Then, redeploy the CloudFormation stack. CloudFormation changes the Lambda rotation function back to Python 3.7.Note: For Python 3.7, the Runtime key value must be python3.7.

Related informationTroubleshooting AWS Secrets Manager
Question: Why doesn't the Amazon Connect CCP open in Salesforce after I've set up the Amazon Connect CTI Adapter?

When I try to open the Amazon Connect Contact Control Panel (CCP) in Salesforce, the CCP opens in a separate window only. The Amazon Connect CTI Adapter's softphone layout also prompts me to "Sign in to CCP." Why isn't the CCP opening in Salesforce after I've set up the Amazon Connect CTI Adapter, and how do I resolve the issue?Short descriptionIf the following domains aren't included on your Amazon Connect instance's Approved Origins list, then you can't embed the CCP into the Salesforce service console:The URL of the Salesforce page where the CCP is imbeddedThe URL of the Lightning Adapter Visualforce page (CTI Adapter URL)To allow list these domains, do the following.

ResolutionVerify the URL of the Salesforce page where the CCP is imbedded1.    Open the Salesforce service console.2.    Choose Setup. The Salesforce service console Setup page opens.3.    Copy the Setup page's URL, and then paste it to a text document.Verify the URL of your Lightning Adapter Visualforce page (CTI Adapter URL)1.    Open the Salesforce service console.2.    Choose Setup.3.    In the Quick Find text box, enter visual. Then, choose Visualforce Pages.4.    In the Name column, select the AC_LightningAdapter link.5.    Choose Preview. A new browser tab opens that contains your Lighting Adapter Visualforce page's URL.6.    Copy the URL, and then paste it to a text document.Add the URLs to your Amazon Connect instance's Approved Origins list1.    Open the Amazon Connect console.2.    Verify that you're in the correct AWS Region for your Amazon Connect instance.3.    In the Instance Alias column, select your instance's alias.4.    In the left navigation pane, choose Approved origins. Then, choose Add domain.5.    In the Enter domain URL text box, enter the URL of the Salesforce page where the CCP is imbedded.Important: Enter the URL through the .com only.Example Salesforce page URL formathttps://XXXXXXXX-dev-ed-.lightning.force.com6.    Choose Add. Your Salesforce page domain appears in the Approved origins section.7.    In the Enter domain URL text box, enter the URL of your Lighting Adapter Visualforce page. Then, choose Add domain.Important: Enter the URL through the .com only.Example Lighting Adapter Visualforce page URL formathttps://yourdomain-dev-ed--amazonconnect.visualforce.com8.    Choose Add. Your Lighting Adapter Visualforce page domain appears in the Approved origins section.Test the setupRefresh the Salesforce service console page in your browser. If your Amazon Connect instance's allow list is configured correctly, then the CCP appears in the Salesforce service console.

Related informationAmazon Connect Salesforce CTI Adapter Installation Guide
Question: How do I gather the Amazon S3 request ID values requested by AWS Support?

I have contacted AWS Support to help resolve an issue with Amazon Simple Storage Service (Amazon S3). I want to provide information to help them troubleshoot the issue.

Short descriptionAmazon S3 generates a pair of request IDs for each request that it processes. When you contact AWS Support for help troubleshooting Amazon S3, you must provide the values of the S3 request ID pair associated with failed actions. This information helps AWS Support identify and troubleshoot your issue as quickly as possible.

ResolutionAmazon S3 request ID pairs are accessible from HTTP headers and verbose logs by using several methods. This includes using AWS CloudTrail to log S3 API calls. For more information about how to retrieve Amazon S3 request ID pairs, see Getting Amazon S3 request IDs for AWS Support. The names used to describe each half of an S3 request ID pair can vary, depending on how the S3 request ID pairs are retrieved. This table lists three commonly used methods for retrieving S3 request ID pairs and the corresponding names used for each half:Access methodFirst name in pairSecond name in pairHTTP response headerx-amz-request-idx-amz-id-2HTTP response body (returned on errors only)RequestIdHostIdAWS SDK requestAWS Request IDS3 Extended Request IDFor example, an S3 request ID pair returned in an HTTP request header resembles the following:x-amz-request-id: 79104EXAMPLEB723x-amz-id-2: IOWQ4fDEXAMPLEQM+ey7N9WgVhSnQ6JEXAMPLEZb7hSQDASK+Jd1vEXAMPLEa3Km=Important: Make sure to provide both values of an S3 request ID pair when requested by AWS Support.For more information about using CloudTrail data event logging to retrieve request ID pairs, see Logging Amazon S3 API calls using AWS CloudTrail. CloudTrail data event logging for S3 objects retrieves both Request ID and Extended request ID data.

Related informationResponse logging in AWS Tools for Windows PowerShellTroubleshootingTutorial: Log Amazon S3 object-level operations using CloudWatch Events
Question: How do I resolve “ERR_SSL_PROTOCOL_ERROR” and "The request could not be satisfied" errors in CloudFront?

I'm using an Amazon CloudFront distribution to serve content. However, viewers receive one of the following errors when they try to access the content through a web browser: "ERR_SSL_PROTOCOL_ERROR" or "The request could not be satisfied". Why is this happening, and how do I resolve the issue?Short descriptionCloudFront can return "ERR_SSL_PROTOCOL_ERROR" and "The request could not be satisfied" errors for two reasons:The CloudFront distribution's alternate domain name is incorrect or has an empty value.(For HTTPS only) The CloudFront distribution's security policy doesn't support the SSL/TLS protocol that's used by the web browser.To resolve the issue, first verify that your distribution's alternate domain name is configured correctly. Then, review your distribution's security policy to confirm that the policy supports the SSL/TLS protocols used by your viewers' web browsers.

ResolutionVerify that the distribution's alternate domain name is configured correctly1.    Open the CloudFront console.2.    In the left navigation pane, choose Distributions. The Distributions page opens.3.    In the ID column, Choose the ID of the distribution that's returning the error.4.    In the Settings section, review the Alternate domain names value. Make sure that the value listed matches domain name that you want to use for your distribution's alternate domain name.5.    If the Alternate domain names value is incorrect, update your distribution's alternate domain name. For instructions, see Adding an alternate domain name in the CloudFront Developer Guide.Note: If the errors persist and your serving content over HTTPS, make sure that you also review the distribution's security policy.(For HTTPS only) Review the distribution's security policy to confirm that the policy supports the SSL/TLS protocols used by your viewers' web browsers1.    Open the CloudFront console.2.    In the left navigation pane, choose Distributions. The Distributions page opens.3.    In the ID column, choose the ID of the distribution that's returning the error.4.    In the Settings section, review the Security policy value. Make sure that policy that's listed supports the SSL/TLS protocols used by your viewers' web browsers. For more information, see Supported protocols and ciphers between viewers and CloudFront.5.    If the distribution's security policy doesn't support the SSL/TLS protocols used by your viewers' web browsers, then update your distribution's security policy. For instructions, see Updating a distribution in the CloudFront Developer Guide.

Related informationConfiguring alternate domain names and HTTPS
Question: Why doesn't my Amazon DynamoDB GetItem operation return the latest data even though PutItem is successful?

When I write a record to a table, PutItem returns a successful HTTP 200 response. However, when I try to fetch the item in a read request, Amazon DynamoDB doesn't return the record.

ResolutionThis usually happens when you use an eventually consistent read to access an item immediately after writing the item to a table. GetItem provides an eventually consistent read by default. If you repeat your read request after a short time, the response should return the latest data in the table for that item.If you want to retrieve the latest data as soon as the write request is successful, set the ConsistentRead parameter to true. This enables strongly consistent reads. Note the following about strongly consistent reads:Strongly consistent reads might have higher latency.Strongly consistent reads aren't supported on global secondary indexes.Strongly consistent reads require twice as much throughput as eventually consistent reads. This means that strongly consistent reads cost twice as much as eventually consistent reads. For more information, see Pricing for provisioned capacity or Pricing for on-demand capacity.For an example request that uses strongly consistent reads, see Retrieve item attributes.

Related informationPutItemRead consistency
Question: Why are my Amazon Aurora cluster endpoints in the Creating status?

I created an Amazon Aurora cluster and my Aurora cluster endpoints are in the Creating status. How can I resolve this issue?Last updated: 2020-08-31Short descriptionWhen you create an Aurora cluster using the Amazon RDS console, the cluster populates with an Aurora DB instance (or two instances if you choose Multi-AZ configuration). This DB instance is implicitly created for the RDS console. After you create the cluster successfully, and the Aurora DB instances are in Available status, the Aurora endpoints are also in the Available status.If you run create-db-cluster  using AWS Command Line Interface (AWS CLI) or use CreateDBCluster API calls to create your Aurora cluster, then you create an empty Aurora cluster without any DB instances. The statuses of your Aurora endpoints in the Amazon RDS console are in the Creating status, because the Aurora cluster does not have any DB instances.To create DB instances for the cluster, use the create-db-instance or the CreateDBInstance API.

ResolutionNote: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.Invoke create-db-instance using the AWS CLI or use the CreateDBInstance API to populate the existing Aurora cluster with Aurora DB instances.The following example command uses AWS CLI to create an Aurora DB instance for an existing Aurora cluster:aws rds create-db-instance --db-instance-identifier sample-instance     --db-cluster-identifier sample-cluster --engine aurora-mysql --db-instance-class db.r4.large --db-parameter-group aurora_pg --port 3306 --publicly-accessibleAfter you have created the Aurora DB instance, and your Aurora DB instance is in the Available status, the Aurora endpoints are also in the Available status.

Related informationCreating an Amazon Aurora DB clusterTools to build on AWS