VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How can I increase the PHP upload size limit in my Lightsail Bitnami WordPress instance?

I want to upload large files onto my Amazon Lightsail Bitnami WordPress instance. How can I increase the default file upload limit on my instance?Short descriptionUpload_max_filesize is the maximum size of an uploaded file. This is the limit for a single file. Post_max_size, on the other hand, is the limit of the entire body of the request. It's a best practice that you set the post_max_size to be greater than or equal to upload_max_filesize.By default, WordPress limits uploads to 40 MB for both post_max_size and upload_max_filesize.To verify the maximum upload limit on your Lightsail instance, run the following commands:# grep -i "upload_max_filesize" /opt/bitnami/php/etc/php.iniupload_max_filesize = 40M# grep -i "post_max_size" /opt/bitnami/php/etc/php.inipost_max_size = 40MResolutionTo modify the maximum upload size, do the following:1.    Open the /opt/bitnami/php/etc/php.ini file to increase upload_max_filesize and post_max_size. Use a text editor, such as the vi editor to access the /opt/bitnami/php/etc/php.ini file.# sudo vi /opt/bitnami/php/etc/php.ini; Maximum size of POST data that PHP will accept.  post_max_size = 64M; Maximum allowed size for uploaded files.  upload_max_filesize = 64M2.    Press the i button to edit the values. After modifying the values, save the file by pressing the ESCAPE button. Then, enter the command :wq!3.    Verify that the LimitRequestBody parameter is specified in the Apache configuration files using the following command:# grep "LimitRequestBody" /opt/bitnami/apache2/conf/httpd.confIf the parameter isn't specified, then there is no size restriction in the Apache web server configuration limits. However, if the parameter is specified and the value is less than the desired upload size, increase the parameter by doing the following:Open /opt/bitnami/apache2/conf/httpd.conf in a text editor such as the vi editor:# sudo vi /opt/bitnami/apache2/conf/httpd.confSet the LimitRequestBody parameter to a new value in bytes, as shown in the following example:LimitRequestBody 65536Press the ESCAPE button and then enter the command :wq! to save the file.4.    Check the configuration details before restarting the services:sudo apachectl configtestSyntax OK5.    Restart the servers for the changes to take effect.sudo /opt/bitnami/ctlscript.sh restart
Question: How do I troubleshoot high JVM memory pressure on my OpenSearch Service cluster?

My Amazon OpenSearch Service cluster has high JVM memory pressure, and I don't know how to resolve this.

Short descriptionBy default, OpenSearch Service uses 50% of an instance's RAM for JVM heaps up to 32 GiB in size. The JVM memory pressure specifies the percentage of the Java heap in a cluster node. The following guidelines indicate what the JVM memory pressure percentages mean:If JVM memory pressure reaches 75%, then OpenSearch Service initiates the Concurrent Mark Sweep (CMS) garbage collector for x86 Amazon Elastic Compute Cloud (Amazon EC2) instance types. ARM-based Graviton Amazon EC2 instance types use the Garbage-First (G1) garbage collector that uses additional short pauses and heap defragmentation. The garbage collection is a CPU-intensive process. If memory usage continues to grow, then you might encounter ClusterBlockException, JVM OutOfMemoryError, or other cluster performance issues. For more information, see Recovering from a continuous heavy processing load.If JVM memory pressure exceeds 92% for 30 minutes, then OpenSearch Service blocks all write operations.If JVM memory pressure reaches 100%, then OpenSearch Service JVM is configured to exit and eventually restarts on OutOfMemory (OOM).The following reasons can cause high JVM memory pressure:Spikes in the numbers of requests to the cluster.Aggregations, wildcards, and selecting wide time ranges in the queries.Unbalanced shard allocations across nodes or too many shards in a cluster.Field data or index mapping explosions.Instance types that can't handle incoming loads.

ResolutionReduce traffic to the cluster to resolve high JVM memory pressure issues. To reduce traffic to the cluster, follow these best practices:Clear the field data cache with the POST /index_name/_cache/clear?fielddata=true API operation.Note: Clearing the cache can disrupt queries that are in progress.Don't aggregate text fields or change the mapping type to "keyword".Scale the domain so that the maximum heap size per node is 32 GB.Turn on slow logs (OpenSearch website) to determine faulty requests.Note: Verify that the JVM memory pressure is below 90%. For more information about slow Elasticsearch queries, see Advanced tuning: finding and fixing slow Elasticsearch queries on the Elasticsearch website.Choose the correct number of shards to optimize search or indexing. For more information about indexing and shard count, see How do I rebalance the uneven shard distribution in my Amazon OpenSearch Service cluster?Delete old or unused indices to reduce the number of shards.For advanced users, you can update the parent field data cache allocation, or request circuit breaker settings according to your use case. For more information about JVM circuit breakers, see JVM OutOfMemoryError.For more information about how to troubleshoot high JVM memory pressure, see Why did my OpenSearch Service node crash?Related informationTroubleshooting Amazon OpenSearch ServiceHow can I scale up or scale out an Amazon OpenSearch Service domain?Get started with Amazon Elasticsearch Service: How many shards do I need?
Question: Why do accounts in my organization show as "suspended" in the AWS Organizations console?

Some member accounts in my organization show as "suspended" in the AWS Organizations console. Why is this happening, and how can I fix this?ResolutionIf a member account of an organization is closed and remains closed for 90 days, then the account is visible in your organization with the "suspended" state for 90 days after the account closure. After 90 days, the closed member account is permanently removed from your organization and is no longer visible in your organization. The AWS Organizations console no longer displays details about the former member account.Note: The account resources in AWS China (Beijing) and AWS China (Ningxia) Regions are subject to the policies of operating partners (Sinnet in the Beijing Region and NWCD in the Ningxia Region). Account closure procedures in China might take longer than in other AWS Regions.All member accounts, open or closed, count against the account quotas for your organization. To increase the account quota, contact AWS Support. For more information, see How do I manage my AWS Service Quotas?Related informationClosing an AWS account
Question: How can I set up host-based routing using an Application Load Balancer?

I have multiple domains that are served by the same Application Load Balancer. I'm using different target groups for each domain. I want to forward the traffic for each domain to their respective target groups. How can I set up host-based routing using an Application Load Balancer?ResolutionOpen the Amazon Elastic Compute Cloud (Amazon EC2) console.On the navigation pane, choose Load Balancers under Load Balancing.Select your load balancer, and then choose Listeners.Choose View/edit rules for the load balancer listener that you want to use.Choose the Add rule icon (the plus sign).Choose Insert Rule.Choose Add condition.Choose Host header.Enter the hostname for your domain (for example, example1.com).Choose the checkmark icon to save the condition.Choose Add action to add the desired actions for your condition. To save the actions, choose the checkmark icon.Choose Save.Repeat steps 5-12 to add additional rules to route different domains to different target groups.Notes:To use the same set of target groups to serve multiple domains, add multiple hostnames for your domains.Rules are prioritized based on their position in the rule list. If necessary, you can reorder rules to modify the rule priorities.If a request's host header doesn't match the host headers in any of the rules, the actions configured in the listener's default rule are performed.

Related informationListener rules for your Application Load Balancer
Question: What do I do if I get an "It looks like you aren't authorized" error when trying to use Amazon Lightsail?

When I try to use the Amazon Lightsail console, I get an error message:"There might be a problem. It looks like you aren't authorized. Try refreshing or signing out of this account and using an account that has access to Lightsail."ResolutionThis error appears when the Lightsail service isn't active on your AWS account. Check the following:Your AWS account is fully activated. New AWS accounts can take up to 24 hours to activate. Wait for 10 to 15 minutes, and then try to access Lightsail again.You completed the sign-up process for your AWS account. For more information, see How do I create and activate a new AWS account? Then, enter all necessary account information, verify your phone number, and then add a valid payment method.Your payment method is valid. Your default payment method must be valid. If necessary, update the default payment method, and then try to access Lightsail again.If you still can't access Lightsail, contact AWS Support.

Related informationManaging your payments
Question: How do I resolve "Page AC_LightningAdapter does not exist" errors and "You can't access Lightning Experience" errors when using the Amazon Connect CTI Adapter?

I receive one of the following errors whenever I try to open the Amazon Connect Contact Control Panel (CCP) in Salesforce: "Page AC_LightningAdapter does not exist" or "You can't access Lighting Experience." Why is the Amazon Connect CTI Adapter returning these errors, and how do I resolve the issue?Short descriptionIf the CTI Adapter URL that's configured in your Salesforce call center is incorrect, then the Salesforce service console doesn't display the Amazon Connect CCP. Instead, Salesforce displays one of the following errors:"Page AC_LightningAdapter does not exist""You can't access Lightning Experience"To resolve these errors, copy the full URL of the Lightning Adapter Visualforce page (CTI Adapter URL) into your Salesforce call center.

ResolutionVerify your Lighting Adapter URL1.    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.Example Lightning Adapter Visualforce page URLhttps://yourdomain-dev-ed--amazonconnect.visualforce.com/apex/AC_LightningAdapterAdd the Lighting Adapter URL to your Salesforce call center1.    In the Salesforce service console, choose Setup.2.    In the Quick Find text box, enter call. Then, choose Call Centers.Note: If this is your first time opening the Call Centers page, then the Say Hello to Salesforce Call Center page opens. Choose Continue if this happens.3.    Choose AC Lightning Adapter.4.    Choose Edit.5.    In the General Information section, for CTI Adapter URL, enter the Lighting Adapter URL that you copied previously.6.    Choose Save.Test the setupRefresh the Salesforce service console page in your browser. If the CTI Adapter URL is configured correctly, then the CCP appears in the Salesforce service console.

Related informationAmazon Connect Salesforce CTI Adapter Installation Guide
Question: Why does CloudWatch show that my Amazon SageMaker endpoint's CPU or GPU utilization is greater than 100%?

The Amazon CloudWatch CPU or GPU utilization metric for my Amazon SageMaker endpoint is greater than 100%.

ResolutionThe CloudWatch CPUUtilization and GPUUtilization metrics show the percentage of CPU or GPU units that the containers are using. The value is multiplied by the number of CPUs or GPUs, which is why the value can be greater than 100%.Here are some examples:For a non-GPU instance such as ml.m4.xlarge, CPUUtilization can range from 0 to 400% because the instance has four vCPUs.For a GPU instance such as ml.p3.8xlarge, CPUUtilization can range between 0 to 3200%. GPUUtilization can range between 0 to 400%. This is because the instance has 32 vCPUs and 4 GPUs.For multiple instances, the default view in CloudWatch shows the average CPU or GPU utilization across all instances. For example, if you have five ml.m4.xlarge instances, CPUUtilization can range from 0 to 400% because each instance has four vCPUs.For more information about the CPUUtilization and GPUUtilization metrics, see Monitor Amazon SageMaker with Amazon CloudWatch. For a list of how many vCPUs or GPUs are in each instance type, see Amazon SageMaker pricing.
Question: How can I use the reputation dashboard to find out when my Amazon SES bounce rate is high?

I want to be notified if my Amazon Simple Email Service (Amazon SES) bounce or complaint rate gets high, so that I can prevent my account from being reviewed or placed on a sending pause.

ResolutionYou can open the reputation dashboard to review your bounce or complaint rate. However, the dashboard doesn't send you notifications when the bounce or complaint rate reaches a certain threshold.To get notifications for a bounce or complaint rate threshold, set up an Amazon CloudWatch alarm with an Amazon Simple Notification Service (Amazon SNS) topic. You can set the CloudWatch alarm to notify the SNS topic whenever your bounce or complaint rate reaches a threshold that you specify. Then, the SNS topic sends a notification to the endpoint (such as an email address) that you subscribed to the topic. For instructions on setting up this notification system, see Creating Reputation Monitoring Alarms Using CloudWatch.Keep in mind the following recommendations when you set your CloudWatch alarm thresholds:Amazon SES recommends that you maintain a bounce rate under 5%. Amazon SES might pause your account's ability to send emails if your bounce rate is greater than 10%. We recommend that you set the bounce rate threshold at 0.05 (5%).Amazon SES recommends that you maintain a complaint rate under 0.1%. Amazon SES might pause your account's ability to send emails if your complaint rate is greater than 0.5%. We recommend that you set the complaint rate threshold at 0.001 (0.1%).Note: The metrics for bounces and complaints are available in the CloudWatch metrics only if your account has had a bounce or complaint event. To see the bounce and complaint metrics in the CloudWatch console, you can send test emails to the designated mailbox simulator email addresses.
Question: How can I capture Amazon DynamoDB global table stream events with AWS Lambda?

I want to create an AWS Lambda trigger to process a stream from an Amazon DynamoDB global table.

ResolutionA DynamoDB global table is a collection of replicas across Regions in a single account. Global tables use DynamoDB Streams to replicate data across different Regions. When you create a replica for a global table, a stream is created by default. Any changes to a replica are replicated to all the other replicas within the same global table within a second using DynamoDB Streams.Note: Having a single consumer on any of the global table replicas in any one Region is enough to retrieve the modification records for all items.You can configure an AWS Lambda trigger to process a stream from a global table replica by doing the following:Be sure that AWSLambdaDynamoDBExecutionRole has the necessary AWS Identity and Access Management (IAM) permissions.Note: The AWSLambdaDynamoDBExecutionRole IAM policy doesn't have permissions for Lambda to communicate with other services, such as Amazon Simple Notification Service (Amazon SNS), by default. This means that you must add the required additional permissions based on the Lambda target.Create a Lambda function using the blueprint dynamodb-process-stream. You can modify the Lambda code according to your requirement to process the stream data.After creating the Lambda function successfully, open the DynamoDB console, and select the global table replica. In the Exports and streams tab, choose Create trigger. Then, select the Lambda function that you created in the previous step. Be sure to select Enable trigger so that the trigger is activated after it's created.The Lambda function is now configured as a trigger for your global table replica. Any changes to the replica are captured by the stream, and the trigger is invoked.

Related informationDynamoDB Streams and AWS Lambda triggers
Question: How do I resolve the errors "Cannot access: s3a://" and "certificate verify failed" when using Hue on Amazon EMR?

My Amazon EMR cluster uses a security configuration that has in-transit data encryption enabled. When I try to access Amazon Simple Storage Service (Amazon S3) buckets on the cluster using Hue (Hadoop User Experience), I get one of the following errors:"Cannot access: s3a://.""Cannot access: s3a://. The HDFS REST service is not available.""bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')])"Resolution"Cannot access: s3a://." and "Cannot access: s3a://. The HDFS REST service is not available."When you launch an encrypted cluster, Amazon EMR expects all connections to be secure. However, the default protocol is HTTP, not HTTPS. To resolve these errors:1.    Open the /etc/hue/conf/hue.ini file.2.    In the webhdfs_url property, be sure that the protocol is https and that the port is 50470. Example:webhdfs_url = https://master-node-private-ip-address:50470/webhdfs/v13.    Run the following commands to restart the Hue service:$ sudo stop hue$ sudo start hue"bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')])"If you're using a self-signed certificate, you might also get the error "bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')])." This happens when Hue tries to verify the certificate with a certificate authority (CA), which isn't possible when you use a self-signed certificate. To resolve this error:1.    Open the /etc/hue/conf/hue.ini file.2.    Change the ssl_cert_ca_verify property from true to false:ssl_cert_ca_verify=false3.    Run the following commands to restart the Hue service:$ sudo stop hue$ sudo start hue

Related informationCreate keys and certificates for data encryptionHue
Question: Why aren't the users specified in my CRL revoked by Client VPN?

I revoked a certificate, generated a certificate revocation list (CRL), and then imported the CRL to AWS Client VPN. I completed these steps to revoke access for specific users. However, the specified users aren't being revoked by Client VPN. How can I fix this?Short descriptionConfirm that you've used the following commands to revoke your certificate and generate the CRL:$ ./easyrsa revoke revoked.learnaws.local$ ./easyrsa gen-crlThen, complete the following steps to continue troubleshooting.

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.1.    Using the AWS CLI, export the CRL and then save it as a "crl.pem" file. Be sure to remove the STATUS at the end of the command output.$ aws ec2 export-client-vpn-client-certificate-revocation-list --client-vpn-endpoint-id cvpn-endpoint-07ff8ba3d5d3b5188 --output text --region eu-central-12.    Create a PEM file for the certificate authority (CA) using the .crt and .key files:$ openssl pkcs12 -export -in ca.crt -inkey ca.key -out ca.p12$ openssl pkcs12 -in ca.p12 -nodes -out ca.pem3.    Create a PEM file for the certificate that must be revoked using the .crt and .key files:$ openssl pkcs12 -export -in revoked.learnaws.local.crt -inkey revoked.learnaws.local.key -out revoked.learnaws.local.p12$ openssl pkcs12 -in revoked.learnaws.local.p12 -nodes -out revoked.learnaws.local.pem4.    Concatenate the "ca" and "crl" PEM files using the cat command:$ cat ca.pem crl.pem > crl_ca.pem5.    Verify the revocation.If the output is "OK", then it's not revoked as intended. The expected output is "error 23 at 0 depth lookup:certificate revoked".$ openssl verify -crl_check -CAfile crl_ca.pem revoked.learnaws.local.pemrevoked.learnaws.local.pem: CN = revoked.learnaws.localerror 23 at 0 depth lookup:certificate revoked-or-Find the serial number of the certificate, and then look for the number in the output. If the serial number is present, then the certificate is revoked.Example:client cert: CN=abc.corp.xyz.com, "CertificateArn": "arn:aws:acm:us-east-1:xxxx:certificate/xxxxx-f692-4026-b26f-cfb361cf1b66", "Serial": "b5:99:e8:b9:5d:39:85:5f:8e:a9:b9:2c:10:9f:8b:c3"$ cd /home/ec2-user/easy-rsa/easyrsa3/pki$ openssl crl -in crl.pem -text -noout | grep B599E8B95D39855F8EA9B92C109F8BC3
Question: Why can't I see the phone icon that opens the CCP in my Amazon Connect contact center?

The phone icon in my Amazon Connect contact center that opens the Contact Control Panel (CCP) isn't appearing. How do I resolve the issue?ResolutionUpdate the user permissionsTo access the CCP, a logged in user must have Access Contact Control Panel access granted in their security profile permissions. If you don't see the phone icon when you're logged in to your contact center, then do either of the following:Assign the user a security profile with sufficient permissions.-or-Update the user's security profile to add the required permissions.Note: On the Edit security profile page, expand Contact Control Panel (CCP) to find the Access Contact Control Panel permission setting.For more information, see Launch the CCP and Provide access to the contact control panel.(Optional) Use the CCP access URLsYou can also access the CCP with either of the following URLs:Important: Replace connectInstanceName with the name of your Amazon Connect instance.CCP v2: https://connectInstanceName.awsapps.com/connect/ccp-v2CCP v1: https://connectInstanceName.awsapps.com/connect/ccpYou must still log in as a user with sufficient permissions. If you use these URLs to log in as a user without access, then Amazon Connect returns the following error:Access deniedYou do not have permission to access the Contact Control Panel (CCP). To request access, contact your administrator.

Related informationAgent training guide