![]() On the “Add tags” page, add tags if required (optional). On the “Attach permissions policies” page, select the “CloudWatchAgentServerPolicy”. Click the “Next: Permissions” button to proceed. On the “Select type of trusted entity” page, select “EC2” as the service to be associated with the new role. Log in to the AWS IAM console and select the “Roles” menu item. NOTE: Learn more about using the Amazon CloudWatch configuration wizard in the official documentation. The resulting configuration file will be stored as /opt/aws/amazon-cloudwatch-agent/bin/config.json. However, when asked whether to store the final configuration SSM parameter store, select “No” to have the configuration file stored locally. In most cases, the default settings are fine. The wizard will prompt you to answer various questions. bĭownload and install the collectd daemon: $ sudo apt-get update & sudo apt-get install collectdĬreate the Amazon CloudWatch configuration file by running the Amazon CloudWatch configuration wizard: $ sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-config-wizard Run the following commands at the console to download and install the Amazon CloudWatch agent: $ wget To install and use the Amazon CloudWatch agent with your Bitnami application instance running on AWS, follow these steps: Install and use the Amazon CloudWatch agentĪmazon CloudWatch makes it easy to track performance and health metrics for your Amazon Web Services (AWS) instances in real time. Troubleshoot server performance problems.Enable SSL access over HTTPS with Cloudflare.Understand the message "AWS instance scheduled for retirement".Modify the AWS instance type or CPU/memory configuration.Auto-configure a Let's Encrypt certificate.Manage Bitnami Launchpad instances through the AWS Console.Launch T2, C4 or M4 AWS instances using the Bitnami Launchpad for AWS Cloud.Install and use the Amazon CloudWatch agent. ![]() Give SSH access to another person, such as a customer.Learn about the Bitnami Configuration Tool.Move AWS instances between the AWS Console and the Bitnami Launchpad for AWS Cloud.Configure third-party SMTP for outbound emails.Reassociate an existing IP address with a new AWS instance.Understand what data Bitnami collects from deployed Bitnami stacks.Learn about Bitnami PHP application modules deprecation.Understand the default directory structure.Learn about the SSH warning 'REMOTE HOST IDENTIFICATION HAS CHANGED'.In this care you need the following statement preconfigured by the sysadmin in the nf file. htaccess file under /opt/bitnami/apps/wordpress/htdocs and put your pagespeed statements there. There's another option, but not necessarily popular if you have access to the main apache configuration files. You can also add the pagespeed configs directly to the nf file if you'd like to inside the Directory directive too. Include /opt/bitnami/apps/wordpress/conf/nf ![]() Make sure your Include statement is within the Directory directive and in the nf file you don't need to have the Directory directive: ![]() ![]() So the option what you are describing: creating and nf file and then adding it as an Include statement in the nf file under /opt/bitnami/apps/wordpress/conf/ is correct. Do I make my changes in the nf file?Īlternatively I saw a few other resources out there with a line to include the nf file added to nf - something like Include /opt/bitnami/apps/wordpress/conf/nfĭo I add this to the nf file and then create nf and work there? Sorry for the confusion, just looking for some direction as I try to do my typical performance boost work. Following this tutorial ( ) I was looking for the nf file in my opt/bitnami/apps/wordpress/conf/ folder, however none existed. I'm trying to modify the expires headers to improve the speed of the client's site. I didn't put this together, and for background I am a Front-end Developer who is used to cPanel and has limited knowledge for the command line. I'm working with a client who has a Wordpress installation (via Bitnami) set up on an Amazon EC2. ![]()
0 Comments
Leave a Reply. |