Вопрос Amazon Web Services для новичков

• phpMyAdmin для RHEL
• Red Hat Enterprise Linux 7.1 - базовая настройка apache
• и ряд других

Amazon Linux AMI
Amazon Linux AMI – это поддерживаемый и обслуживаемый образ Linux, предоставляемый сервисом Amazon Web Services для использования в Amazon Elastic Compute Cloud (Amazon EC2). Он предназначен для обеспечения стабильной, безопасной и высокопроизводительной среды для выполнения приложений, работающих в Amazon EC2. Он также включает в себя пакеты, которые позволяют обеспечить простую интеграцию с AWS, среди которых инструменты конфигурации запуска, а также многие популярные библиотеки и инструменты AWS. Amazon Web Services с целью обеспечения текущей безопасности и обслуживания обеспечивает обновление всех инстансов, на которых используется Amazon Linux AMI. Amazon Linux AMI предоставляется пользователям Amazon EC2 без дополнительной оплаты.

sudo yum update

sudo yum install httpd

sudo systemctl enable httpd.service

sudo systemctl start httpd.service

sudo yum install mariadb-server

sudo systemctl enable mariadb

$ sudo service mariadb start
Redirecting to /bin/systemctl start  mariadb.service
[ec2-user@ip-XXX-XX-XX-XX ~]$ systemctl status mariadb
mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled)
   Active: active (running) since Ср 2015-04-15 12:21:32 EDT; 7s ago
  Process: 11068 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
  Process: 10989 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
 Main PID: 11067 (mysqld_safe)
   CGroup: /system.slice/mariadb.service
           ├─11067 /bin/sh /usr/bin/mysqld_safe --basedir=/usr
           └─11226 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --...

mysql -u root
> use mysql
> select host,user from user;

+---------------------------------------------+------+
| host                                        | user |
+---------------------------------------------+------+
| 127.0.0.1                                   | root |
| ::1                                         | root |
| ip-XXX-XX-XX-XX.us-west-2.compute.internal |      |
| ip-XXX-XX-XX-XX.us-west-2.compute.internal | root |
| localhost                                   |      |
| localhost                                   | root |
+---------------------------------------------+------+
6 rows in set (0.00 sec)

MariaDB [mysql]> quit

$ sudo /usr/bin/mysql_secure_installation
/usr/bin/mysql_secure_installation: line 379: find_mysql_client: команда не найдена

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none): 
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.

Set root password? [Y/n] Y
New password: 
Re-enter new password: 
Password updated successfully!
Reloading privilege tables..
 ... Success!


By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n] Y
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n] Y
 ... Success!

By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n] Y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n] Y
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.

Thanks for using MariaDB!

$ sudo mysql -u root -p

> select host,user from user;
ERROR 1046 (3D000): No database selected

MariaDB [mysql]> show databases;

1. Увеличиваем в файле php.ini значение параметра upload_max_filesize.
2. Увеличиваем в файле php.ini значение параметра post_max_size.
3. sudo service httpd restart

Aleksej пишет: Amazon Web Services для новичков.

superlamer пишет: а вот сколько хостинг на Амазоне будет стоить через год, когда бесплатности кончатся, кто бы сказал.....

How to restore EC2 Instance from Snapshot

To restore EC2 Instances from the snapshot(s) in the same or different AWS region follow these steps:

1. Create a new EC2 Instances with parameters similar to the instance from which the snapshot(s) was taken. If possible, the best practice would be to take an AMI of the existing EC2 and create a new instance based on that AMI. The new instance can be created in any AWS region.

2. Identify the snapshot that was taken from the root (C: drive) EBS volume:

• To identify root snapshot go to the AWS Management Console
• Under EC2 section, click “Instances”
• Select the source instance
• In the Description section, click “Root device type”
• Copy or Note EBS ID
• Restore EC2 Instance from Snapshot
• Go to Snapshots section
• In the Search field type or paste the EBS ID
• On the list you should see the snapshots created from the root volume
• Restore EC2 Instance from Snapshot

3. If the new instance will be launched in different AWS region, copy the root snapshot to destination region, otherwise skip this step:

• To copy a snapshot to a different region go to the AWS Management Console
• Under EC2 section go to Snapshots and select the “root snapshot”
• From the menu, select “Copy”
• Restore EC2 Instance from Snapshot
• Choose the destination region and click “Copy”
• Restore EC2 Instance from Snapshot

4. Stop the new EC2 Instance.

5. Detach the root volume from the Instance:

• To identify root volume follow steps [a-d] from #2
• Go to volumes
• Type the volume ID in “Search Volumes” field
• Restore EC2 Instance from Snapshot
• Check the root volume on the list
• From “Action” select “Force Detach Volume”
• Restore EC2 Instance from Snapshot

6. Create a new volume based on the snapshot identified in #2:

• Go to snapshots
• Find the new snapshot
• From “Actions” select “Create Volume”
• Restore EC2 Instance from Snapshot
• Select appropriate type of Volume (Standard or IOPS)
• You can enter the bigger size if needed
• Availability zone must be the same as the one where a new EC2 instance was launched in
• Click “Create”
• Restore EC2 Instance from Snapshot

7. Attach the new volume:

• Go to volumes
• Select the volume that was created in #6
• From “Actions” select “Attach volume”
• Restore EC2 Instance from Snapshot
• In Instance field select the instance created in #1
• In Device field type /dev/sda1
• Click “Attach”
• Restore EC2 Instance from Snapshot

8. Start Instance.

serge пишет: И тем не менее, продолжаем палить тему. Итак:

superlamer пишет: можно ли будет заплатить Maestro?

Version 3.4.7 Joomla is released to address two reported security vulnerabilities and includes security hardening of the MySQLi driver to help prevent object injection attacks.
The Joomla Security Strike team has been following up on the critical security vulnerability patched last week. Since the recent update it has become clear that the root cause is a bug in PHP itself. This was fixed by PHP in September of 2015 with the releases of PHP 5.4.45, 5.5.29, 5.6.13 (Note that this is fixed in all versions of PHP 7 and has been back-ported in some specific Linux LTS versions of PHP 5.3). The only Joomla sites affected by this bug are those which are hosted on vulnerable versions of PHP. We are aware that not all hosts keep their PHP installations up to date so we are making this release to deal with this issue on vulnerable PHP versions.

$ sudo yum info php
Загружены модули: amazon-id, rhui-lb, search-disabled-repos
Доступные пакеты
Название: php
Архитектура: x86_64
Версия: 5.4.16
Выпуск: 36.3.el7_2
Объем: 1.4 M
Источник: rhui-REGION-rhel-server-releases/7Server/x86_64
Аннотация: PHP scripting language for creating dynamic web sites
Ссылка: http://www.php.net/
Лицензия: PHP and Zend and BSD
Описание: PHP is an HTML-embedded scripting language. PHP attempts to make it
        : easy for developers to write dynamically generated web pages. PHP also
        : offers built-in database integration for several commercial and
        : non-commercial database management systems, so writing a
        : database-enabled webpage with PHP is fairly simple. The most common
        : use of PHP coding is probably as a replacement for CGI scripts.
        : 
        : The php package contains the module (often referred to as mod_php)
        : which adds support for the PHP language to Apache HTTP Server.

sudo subscription-manager repos --list | egrep rhscl

Павел Алексеев (aka Pahan-Hubbitus):: ну поддержки не было на бесплатном периоде, а потом я уже и не спрашивал. А на форуме они не ответили по проблеме.

innodb_use_sys_malloc
Description: If set the 1, the default, XtraDB/InnoDB will use the operating system's memory allocator. If set to 0 it will use its own. Deprecated in MariaDB 10.0 and removed in MariaDB 10.2 along with InnoDB's internal memory allocator.
Commandline: --innodb-use-sys-malloc=#
Scope: Global
Dynamic: No
Data Type: boolean
Default Value: ON
Deprecated: MariaDB 10.0
Removed: MariaDB 10.2.2

File /etc/my.cnf.d/auth_gssapi.cnf contains the line

plugin-load-add=auth_gssapi.so

Comment it out and restart the service. The server should stop loading the plugin, it will make the errors go away.
If you don't need the plugin at all, you can also uninstall MariaDB-gssapi packages

MariaDB-gssapi-server-10.1.19-1.el7.centos.x86_64
MariaDB-gssapi-client-10.1.19-1.el7.centos.x86_64

// Создаем файл конфигурации для всех пользователей
mcedit /etc/profile.d/locale.sh

//Пишем следующие значение и сохраняем файл
export LANG=en_US.UTF-8
export LANGUAGE=en_US.UTF-8
export LC_COLLATE=C
export LC_CTYPE=en_US.UTF-8

//Загружаем настройки
source /etc/profile.d/locale.sh