Wednesday Dec 16, 2009

OpenSolaris as Amazon EC2 VPC customer gateway

OpenSolaris EC2 team continues to explore different possibilities using OpenSolaris in virtualized/cloud environments. The recent addition to that is our VPC Gateway Tool, which lets you seamlessly bridge the connection between your data center and Virtual Private Clouds running within Amazon EC2 infrastructure. 

This eliminates the need for special purpose devices such as router and provide unprecedented security. The deployment is super simplified and the requirement is just an OpenSolaris Box running latest OpenSolaris release. You can do it on an independent machine or you can do it within a VirtulaBox client, simplicity remains the same. The VPC tool is up for further development and interested people should join the Kenai project if you like to get involved. 

More details can be found Glenn's Blog who has led the team to make this possible.

And the tool can be downloaded from Kenai Mercurial repository:

https://kenai.com/hg/osolvpc~source osolvpc


Monday Nov 02, 2009

Security Enhanced OpenSolaris 2009.06 AMP Stack AMI

US AMI Details:
AMI ID :
 ami-e0b05389
 AMI Manifest :
 sun-opensolaris-2009-06/amp_stack_hardened_opensolaris_2009.06_32_1.1.img.manifest.xml
 AKI / ARI ID:
 aki-1783627e / ari-9d6889f4
 License :
Public

Europe AMI Details:
AMI ID :
ami-7a2a010e
AMI Manifest :
sun-opensolaris-2009-06-eu/amp_stack_hardened_opensolaris_2009.06_32_1.1.img.manifest.xml
AKI / ARI ID:
aki-2181a955 / ari-b49fb7c0
License :
Public

Description:

This 32-bit AMI is based on OpenSolaris 2009.06 Hardened Security AMI (ami-e56e8f8c).

Following components are included in this AMI

  • Apache 2.2
  • MySQL 5.1
  • PHP 5.2
  • phpmyadmin 3.2.2

Configurations:

  • Apache and MySQL services are pre-configured to start on boot.
    • Apache Service: svc:/network/http:apache22
    • MySQL Service: svc:/application/database/mysql:version_51
  • If you would like to use phpMyAdmin, you will need to do the following:

# cp /etc/apache2/2.2/samples-conf.d/phpmyadmin.conf /etc/apache2/2.2/conf.d/
# svcadm restart http:apache22

  • DTrace probes are available within Apache and PHP runtime. Sample DTrace scripts are available under /opt/DTT/
  • More details on security information and image usage instructions is provided in to the '/root/ec2sun/README' file.

AMP Stack Files Layout:


 Apache  PHP  MySQL
 Binary Runtime Files
 /usr/apache2/2.2/bin  /usr/php/5.2/bin  /usr/mysql/5.1/bin
 Configuration Files
 /etc/apache2/2.2  /etc/php/5.2  /etc/mysql/5.1
 Web Documents / Data Files
 /var/apache2/2.2  /var/php/5.2  /var/mysql/5.1

Administering AMP Stack

 Command  Apache  MySQL
 Start Service  svcadm enable http:apache22  svcadm enable mysql:version_51
 Stop Service  svcadm disable http:apache22  svcadm disable mysql:version_51
 Restart Service  svcadm restart http:apache22  svcadm restart mysql:version_51


You can reset MySQL 'root' password by running following command:

# /usr/mysql/5.0/bin/mysqladmin -u root -p password '<MySQL password>'


It is highly recommended to secure your MySQL database by following the guidelines mentioned within MySQL 5.1 database documentation: http://dev.mysql.com/doc/refman/5.1/en/security-guidelines.html

Rebundling Changes:

You must disable the auditing during re-bundling. You can execute following commands in your clean up tasks before
executing "ec2-bundle-image" command.

# audit -t
# > /var/log/auditlog
# rm -f /var/audit/\*

As you can see we have introduced the new ARI (ari-9d6889f4) with this AMI, make sure you use the correct ARI with the
"ec2-bundle-image" command as given below.

# ec2-bundle-image -c $EC2_CERT -k $EC2_PRIVATE_KEY \\
--kernel aki-1783627e --ramdisk ari-9d6889f4 \\
--block-device-mapping "root=rpool/56@0,ami=0,ephemeral0=1" \\
--user <userid> --arch i386 \\
-i $DIRECTORY/$IMAGE -d $DIRECTORY/parts

Note: For Europe use "--kernel aki-2181a955 --ramdisk ari-b49fb7c0"

You can restart the audit daemon on the instance where you disabled it temporarily for re-bundling with following
command.

# audit -s

Europe Launch:

To run this AMI in Europe (AMI ID: ami-7a2a010e), change the following environment variables before launching the AMI:

bash # export EC2_URL="https://eu-west-1.ec2.amazonaws.com"
bash # export LOCATION="EU"

The other env variables remain the same as documented in the getting started guide.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Documentation:

Support

  • Register at http://www.sun.com/third-party/global/amazon/ to receive latest news on OpenSolaris AMIs
  • For technical support during Beta period, please send emails to ec2-solaris-support[AT]SUN[DOT]COM.
  • AMP Stack within OpenSolaris are delivered as part of WebStack project. For any questions related to these components, please write to webstack-discuss[AT]opensolaris[DOT]org

Tuesday Oct 27, 2009

Immutable Service Containers on OpenSolaris 2009.06

US AMI Details
AMI ID :
ami-48c32021
 AMI Manifest :
sun-opensolaris-2009-06/ISC_hardened_opensolaris_2009.06_32_V_1.1.img.manifest.xml
 AKI / ARI ID:
aki-1783627e / ari-9d6889f4
 License :
Public

Europe AMI Details
AMI ID :
ami-78567d0c
 AMI Manifest :
sun-opensolaris-2009-06-eu/ISC_hardened_opensolaris_2009.06_32_V_1.1.img.manifest.xml
 AKI / ARI ID:
aki-2181a955 / ari-b49fb7c0
 License :
Public

Description

Immutable Service Container configuration is intended to be used as a virtual single system. The global zone performs administrative and monitoring functions similar to those of a system controller whereas all end-user services and functions should be installed into the non-global zone. In this way, services such as packet filtering, NAT and auditing can operate without being exposed to services or users operating inside of the non-global zone. This enables greater operational integrity as those services and users are not able to alter the configurations or logs associated with these services. Additional non-global zones can be added as needed. This configuration uses a single exposed network interface and IP address for all of its communication even though internally the service is separated to run inside of its own non-global zone.

Organizations can further customize the configuration based upon their requirements to add things such as resource controls, read-only and read-write file systems (to the non-global zone), specific users and services, etc.

More Details

For detailed explanations on Immutable Service Container Configuration, Please Visit

Architecture Diagram

Europe Launch:

To run this AMI in Europe (AMI ID: ami-78567d0c), change the following environment variables before launching the AMI:

bash # export EC2_URL="https://eu-west-1.ec2.amazonaws.com"
bash # export LOCATION="EU"

The other env variables remain the same as documented in the getting started guide.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Documentation

Support

  • Register at http://www.sun.com/third-party/global/amazon/ to receive latest news on OpenSolaris AMIs
  • For technical support during Beta period, please send emails to ec2-solaris-support[AT]SUN[DOT]COM.
  • AMP Stack within OpenSolaris are delivered as part of WebStack project. For any questions related to these components, please write to webstack-discuss[AT]opensolaris[DOT]org

Tuesday Oct 13, 2009

EBS FAQ and how-to's

Previously we posted a blog entry titled “OpenSolaris supports EBS - provides capability to create ZFS” that explains how to use the Amazon's Elastic Block Storage with OpenSolaris EC2 instances. This document combines the EBS with OpenSolaris ZFS technology. While we tried to cover the details needed but there a few questions have been asked several times. In this entry, I will try to explain those details and feel free to ask more questions so we can make it as clear as possible:

  • When an EBS device is attached to OpenSolaris instance, how do I identify these drives from within the instance?
  • Can I use some automated scripts to mount these EBS devices during the instance startup ? is this answered last (below)?
  • Why do I sometimes detach/attach being not successful ?

I will answer these questions in following sections.

When a disk is attached to an OpenSolaris instance it can be viewed in number of ways and the simplest one is to use the format(1M) command. Following is the output of the format command on a default OpenSolaris EC2 instance (without any EBS device being attached) :

root@domU-12-31-39-00-50-A7:~# format

Searching for disks...done

AVAILABLE DISK SELECTIONS:

0. c7d0 <DEFAULT cyl 1274 alt 0 hd 255 sec 63>

/xpvd/xdf@0

1. c7d1 <DEFAULT cyl 19464 alt 0 hd 255 sec 63>

/xpvd/xdf@1

Specify disk (enter its number):

What this tells us is there are two default disks wwhere the controller is 7 and disk is 0(c7d0) and 1(c7d1). It is important to note that this is an OpenSolaris 2009.06 AMI and any AMI which is based on this should have the same controller number. For different OpenSolaris versions the controller number may change and the Getting Started Guide or the format command can be referred to get this information. Any further disk attachment through EBS commands (ec2-attach-volume) will have the same controller ID and a new disk id which will change based on the argument we give to this command. So far it can be easily assumed that -d (a unique number greater than 1) will result in an EBS device appearing as below with the format command within the EC2 instance:

c7d<decimal value of <<a unique number greater than 1> treated as hex number>

eg.

$ ec2-attach-volume vol-63d6250a -d 3 -i i-cf65b5a7

will result in:

c7d3 <DEFAULT cyl 2048 alt 0 hd 128 sec 32>

/xpvd/xdf@3

And so a command like this will result in the following:

$ ec2-attach-volume vol-63d6250a -d 10 -i i-cf65b5a7

will result in:

c7d16 <DEFAULT cyl 2048 alt 0 hd 128 sec 32>

/xpvd/xdf@3


Now if the disk number is already assigned and you try to do that again, it will result in following error:

$ ec2-detach-volume vol-63d6250a -d 2 -i i-cf65b5a7

Client.InvalidAttachment.NotFound: The volume 'vol-63d6250a' is not attached to instance 'i-cf65b5a7' as device '2'.

So it must be unique and unused number.

Also, for detaching a mounted ZFS or regular UFS? file system, we will have to do few things before we can do a clean detach:

For the EBS volumes that is part of ZFS we have to do the following:

Shutdown all applications that are running on top of the ZFS pool.
Export the ZFS pools with:
$ zpool export pool_name
Detach the EBS volumes from the ECS instance.
Also clean up devices with:
$ devfsadm -C -v

For regular UFS? mounted file systems using the newfs(1M) and mount(1M) commands:

Unmount the mounted volume:

$ umount /ebs-vol

Also clean up devices with:
$ devfsadm -C -v

Tuesday Sep 08, 2009

Using Solaris Zones/Container on Amazon EC2

As many of you have requested about how to create and manage Solaris zones/container within an instance of OpenSolaris running in Amazon EC2 environment. Our team member Sean O'Dell was able to put together a series of blog:

which will guide you through step by step instruction on how to create Solaris Zones in an OpenSolaris instance running in EC2. This brings in the best of virtualization features of OpenSolaris in the EC2 environment. If you have used the zones before you may be aware that there are virtually no cost of running zones on OpenSolaris.

We welcome your feedback and comment, if you have any problem following the blog please let us know so we can make it more clear.


Tuesday Aug 18, 2009

Hardened OpenSolaris 2009.06 AMI now available in Europe

We are very happy to announce the availability of the latest Hardened OpenSolaris 2009.06 AMI on Amazon EC2 in the European Region. This AMI is based on the OpenSolaris 2006.09 US AMI and does not need registration.

Following are the details of this new AMI:

Hardened OpenSolaris 2009.06 32-bit AMI:

ami-b69fb7c2 aki-2181a955 / ari-b49fb7c0

Manifest: hardened_opensolaris_2009.06_32_1.2.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Rebundling Changes:

As you can see we have introduced the new ARI (ari-9d6889f4) with this AMI, make sure you use the correct ARI with the "ec2-bundle-image" command as given below.

bash # ec2-bundle-image -c $EC2_CERT -k $EC2_PRIVATE_KEY \\
 --kernel aki-661c3412 --ramdisk ari-601c3414 \\
 --block-device-mapping "root=rpool/56@0,ami=0,ephemeral0=1" \\
 --user <userid> --arch i386 \\
 -i $DIRECTORY/$IMAGE -d $DIRECTORY/parts

In addition if you want to disable auditing during re-bundling, you can execute following commands in your clean up tasks before executing "ec2-bundle-image" command.

bash # audit -t
bash # > /var/log/auditlog
bash # rm -f /var/audit/\*

Friday Aug 14, 2009

Hardened OpenSolaris 2009.06 on Amazon EC2 Released

AMI ID: ami-e56e8f8c
AMI Manifest: sun-opensolaris-2009-06/hardened_opensolaris_2009.06_32_1.2.img.manifest.xml
AKI/ARI ID:
aki-1783627e / ari-9d6889f4
License: Public

Description:

Sun Microsystems Inc. is pleased to announce the release of Hardened OpenSolaris 2009.06 on Amazon EC2's cloud computing service. This 32-bit AMI gives you the power and security of OpenSolaris combined with the flexibility of Amazon's cloud computing service, and is optimized for Amazon EC2's cloud computing environment.

The OpenSolaris system configuration has been adjusted to comply with the recommendations published by Sun and the Center for Internet Security, a non-profit organization chartered to develop and encourage widespread use of security configuration benchmarks developed through a global consensus process involving participants from academia, industry and government. 

Working together for more than six years, Sun and the Center for Internet Security have consistently developed best-in-class, supportable and complete security hardening guidance for the Solaris operating system.

The latest version developed for the Solaris 10 operating system was completed with substantial contributions from Sun, CIS, the U.S. National Security Agency (NSA), as well as the U.S. Defense Information Systems Agency (DISA).

Building upon this foundation, Sun and the Center for Internet Security collaborated to adapt the security recommendations published in the Solaris 10 Benchmark to the OpenSolaris operating system and document those changes specific to virtual machine images such as those available on Amazon EC2. 

All of the specific changes made to the base OpenSolaris 2009.06 AMI are discussed on the Sun OpenSolaris AMI Hardening Wiki : http://wikis.sun.com/display/ISC/OpenSolaris+Security+Hardening

For more information on the Center for Internet Security's Solaris 10 Benchmark, see:
http://www.cisecurity.org/bench_solaris.html

New features introduced with this latest release of Hardened Security AMI are "Encrypted swap memory" and "auditing".

More information on "Encrypted Swap Memory" feature is available at
http://blogs.sun.com/gbrunett/entry/encrypted_swap_in_opensolaris_2009 


This project is affiliated with the Immutable Service Container project whose goal is to develop security reinforced virtual machine images. The Immutable Service Container project developed the code used by this AMI to implement hardening, encrypted swap and auditing.  Additional information regarding Immutable Service Containers can be found at:
http://kenai.com/projects/isc/pages/OpenSolaris


The root file system is ZFS in this AMI and includes the pre-installed packages and tools necessary to get started with using OpenSolaris on Amazon EC2. You can obtain more details about the OpenSolaris project at http://www.opensolaris.org.

Also, just like in our previous AMIs, the "pkg image-update" command updates the kernel and ramdisk which is not allowed in Amazon EC2. Therefore, in order to prevent your instances from becoming non-compatible with the Amazon EC2 environment, we have disabled this command.

More details including re-bundling instructions can be found in the Getting Started Guide.

Rebundling Changes:

 You must disable auditing during re-bundling. You can execute following commands in your clean up tasks before executing "ec2-bundle-image" command.

bash # audit -t
bash # > /var/log/auditlog
bash # rm -f /var/audit/\*

 As you can see we have introduced the new ARI (ari-9d6889f4) with this AMI, make sure you use the correct ARI with the "ec2-bundle-image" command as given below.

bash # ec2-bundle-image -c $EC2_CERT -k $EC2_PRIVATE_KEY \\
 --kernel aki-1783627e --ramdisk ari-9d6889f4 \\
 --block-device-mapping "root=rpool/56@0,ami=0,ephemeral0=1" \\
 --user <userid> --arch i386 \\
 -i $DIRECTORY/$IMAGE -d $DIRECTORY/parts

You can restart the audit daemon on the instance where you disabled it temporarily for re-bundling with following command.

bash # audit -s


Support:

Thursday Jul 30, 2009

SailFin AMI on OpenSolaris 2008.11 now available in Europe

We are very happy to broaden the availability of the latest SailFin AMI on OpenSolaris 2008.1 AMI on Amazon EC2 in the European Region. This AMI is based on the OpenSolaris 2008.11 base AMI US AMI and does not need registration.

Following are the details of this new AMI:

SailFin 32-bit AMI:

ami-3282aa46 aki-661c3412 / ari-601c3414

Manifest: sailfinv2-opensolaris-2008.11.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Wednesday Jul 29, 2009

32-bit OpenSolaris 2009.06 Base AMI now available in Europe

We are very happy to broaden the availability of the latest OpenSolaris 2009.06 AMI on Amazon EC2 in the European Region. This AMI is based on the OpenSolaris 2006.09 US AMI and does not need registration.

Following are the details of this new AMI:

OpenSolaris 2009.06 32-bit AMI:

ami-2381a957 aki-2181a955 / ari-2581a951

Manifest: opensolaris_2009.06_32_6.1.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

64-bit OpenSolaris 2009.06 Base AMI now available in Europe

We are very happy to broaden the availability of the latest 64-bit OpenSolaris 2009.06 AMI on Amazon EC2 in the European Region. This AMI is based on the 64-bit OpenSolaris 2006.09 US AMI and does not need registration.

Following are the details of this new AMI:

OpenSolaris 2009.06 64-bit AMI:

ami-3981a94d aki-4d81a939 / ari-4181a935

Manifest: opensolaris_2009.06_64_6.1.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Friday Jul 24, 2009

32-bit OpenSolaris 2009.06 base AMI Released on Amazon EC2

Sun Microsystems Inc. is pleased to announce the new release OpenSolaris 2009.06 on Amazon EC2's cloud computing service. This 32-bit AMI gives you the power and security of OpenSolaris combined with the flexibility of Amazon's cloud computing service, and is optimized for for Amazon EC2's cloud computing environment.

AMI ID: ami-8f30d1e6
AMI Manifest: sun-opensolaris-2009-06/opensolaris_2009.06_32_6.1.img.manifest.xml
AKI/ARI ID:
aki-1783627e / ari-858362ec
License: Public

Description:

OpenSolaris 2009.06 is the latest release of the OpenSolaris Operating System, a powerful and complete operating environment for users. developers and deployers. OpenSolaris prides itself on being a secure, stable, and highly scalable system. The OpenSolaris OS is open source software, and freely re-distributable and provides all the tools users expect from a modern computing environment both installed by default and available on our online network package repositories.

Information on "What's new in OpenSolaris 2009.06" is available at
http://www.opensolaris.com/learn/features/whats-new/200906/


The root file system is ZFS in this AMI and includes the pre-installed packages and tools necessary to get started with using OpenSolaris on Amazon EC2. You can obtain more details about the OpenSolaris project at http://www.opensolaris.org.

Also, just like in our previous AMIs, the "pkg image-update" command updates the kernel and ramdisk which is not allowed in Amazon EC2. Therefore, in order to prevent your instances from becoming non-compatible with the Amazon EC2 environment, we have disabled this command.

The "Getting Started Guide" has been updated with instructions for Re-bundling OpenSolaris 2009.06 based 32-bit AMI on Amazon EC2.


Rebundling Changes:

For new 32-bit OpenSolaris 2009.06 AMI re-bundling use following "ec2-bundle-image" command. For more detail look into the Getting Started Guide (Page 10).

ec2-bundle-image -c $EC2_CERT -k $EC2_PRIVATE_KEY   \\
  --kernel aki-1783627e --ramdisk ari-858362ec \\
  --block-device-mapping "root=rpool/56@0,ami=0,ephemeral0=1" \\
  --user <user-id> --arch i386 \\
  -i $DIRECTORY/$IMAGE -d $DIRECTORY/parts

IMPORTANT NOTICE:  AMI Refresh of OpenSolaris 2009.06 32-bit on Amazon EC2

After the launch of the OpenSolaris 2009.06 32-bit AMI (AMI ID ami-4133d528) at the beginning of June, an infrequent launch hang upon AMI startup was discovered.  This issue has been submitted as CR 6840704 and has been fixed in an AMI Refresh.

New launches of the old OpenSolaris 2009.06 AMI (ami-4133d528) will be disabled and current users will still be able to use the old ari and aki (aki-b128ced8 / ari-d336d0ba) with their rebundled AMI based on ami-4133d528.

Support:

For technical support during the Beta period, please contact ec2­-solaris­-support[AT]SUN[DOT]COM.

Please check OpenSolaris on Amazon EC2 blog for latest updates and new information about OpenSolaris AMIs.

The "OpenSolaris on Amazon EC2 Getting Started Guide" is located at:
http://www.sun.com/third-party/global/amazon/Sun_AmazonEC2_GettingStartedGuide.pdf


Register for OpenSolaris AMIs here

64-bit OpenSolaris 2009.06 Base AMI Released On Amazon EC2

Sun Microsystems Inc. is pleased to announce the release of 64-bit OpenSolaris 2009.06 base AMI On Amazon EC2's cloud computing service. This 64-bit AMI gives you the power and security of OpenSolaris combined with the flexibility of Amazon's cloud computing service, and is optimized for for EC2's cloud computing environment.

AMI Details:

AMI ID: ami-9903e2f0
AMI Menifest: sun-opensolaris-2009-06/opensolaris_2009.06_64_6.1.img.manifest.xml
AKI/ARI ID: aki-fb3ddc92 / ari-fd3ddc94

This AMI supports 64-bit Instance sizes including m1.large (Large Instance Type), m1.xlarge (Extra Large Instance Type) and c1.xlarge (High CPU Extra Large Instance Type).

For more details on these instance types visit

To run the AMI with Large Instance type, execute following command.
ec2-run-instances ami-9903e2f0
-k <your-keypair> --instance-type m1.large

To run the AMI with Extra Large Instance type, execute following command.
ec2-run-instances ami-9903e2f0
-k <your-keypair> --instance-type m1.xlarge

To run the AMI with High CPU Extra Large Instance type, execute following command.
ec2-run-instances ami-9903e2f0
-k <your-keypair> --instance-type c1.xlarge

For OpenSolaris 2009.06 32bit base AMI, Please see
http://blogs.sun.com/ec2/entry/opensolaris_2009_06_on_amazon

For Other AMIs provided by Sun Microsystems, Please see
http://blogs.sun.com/ec2/entry/opensolaris_based_ami_catalog_on

Configuring Swap Memory

OpenSolaris 2009.06 64-bit AMI Instance comes with default 1 GB of swap memory.
Follow below given steps to increase the swap memory size by 15gb.

# zfs create -V 15g mnt/swap
# swap -a /dev/zvol/dsk/mnt/swap

You can make this change permanent by changing the lines for swap in “/etc/vfstab” file.
change “/dev/zvol/dsk/rpool/swap” to “/dev/zvol/dsk/mnt/swap” and save the file.

Finally Reboot the instance.

64-bit AMI Rebundling Changes:

For 64-bit OpenSolaris 2009.06 AMI re-bundling use following "ec2-bundle-image" command. For more detail look into the Getting Started Guide (Page 10).

ec2-bundle-image -c $EC2_CERT -k $EC2_PRIVATE_KEY   \\
  --kernel aki-fb3ddc92 --ramdisk ari-fd3ddc94 \\
  --block-device-mapping "root=rpool/56@0,ami=0,ephemeral0=1,ephemeral1=2,ephemeral2=3,ephemeral3=4" \\
  --user <user-id> --arch x86_64 \\
  -i $DIRECTORY/$IMAGE -d $DIRECTORY/parts

Support:

Monday Jun 29, 2009

OpenESB v3 AMI now available in Europe

We are very happy to broaden the availability of the latest OpenESB AMI on Amazon EC2 in the European Region. This AMI is based on the OpenSolaris 2008.11 base AMI and does not need registration.

Following are the details of this new AMI:

OpenESB 32-bit AMI:

ami-cfb199bb aki-661c3412 / ari-601c3414

Manifest: OpenSolaris_2008.11_32_OpenESB_v3.0.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

Thursday Jun 18, 2009

OpenESB v3 AMI On OpenSolaris 2008.11


AMI ID:

ami-5d2cca34

AMI Manifest:

sun-osol-2008-11/OpenSolaris_2008.11_32_OpenESB_v3.0.img.manifest.xml

License:

Public

Description:

This 32 bit AMI is based on OpenSolaris 2008.11 base AMI

OpenESB is an Open Source project creating a platform for Business Integration, Enterprise Application Integration, and SOA. The license is CDDL. A large number of components is being developed in the OpenESB community: e.g. for accessing back-end systems and other ESBs or SOA platforms, for message transformation, etc. Unlike proprietary ESBs, OpenESB is purely based on open standards (e.g. JBI and Java EE). This prevents vendor lock-in.

The following components are included in the AMI.

  • OpenESB v3 (pre-configured state) contains the following:

    • The OpenESB v3 Runtime

    • Service Engines

      • Sun JRuby Engine

      • POJO SE Component

    • Binding Components

      • FTP Binding Component

      • Email Binding Component

      • File Binding Component

      • Sun Database Binding

      • Scheduler Binding Component

      • REST Binding Component

      • RSS Binding Component

      • XMPP Binding Component

    • Shared Libraries

      • Sun WSDL Shared Library

      • Sun Encoder Library

      • Sun Shared Util Library

    • The Aspect Framework

    • Log Aspect

    • Policy Aspect

    • A Web-Based Tooling Editor (accessible from http://<DNS host name associated with the instance>:8080/fuji/editor)

  • Apache Derby

  • Apache Felix

The OpenESB Web Editor can be accessible using public DNS address associated with the instance. It can be accessed from http://<DNS host name associated with the instance>:8080/fuji/editor in their browser.

Configuration:

  • OpenESB v3 (bundled within this AMI in pre-configured state) is available under location /usr/fuji

  • Users can launch the OpenESB editor from http://<DNS host name associated with the instance>:8080/fuji/editor in their browser.

  • Apache Felix and Derby services are pre-configured to start on automatically

For more details on security information and image usage instructions, please refer to the '/root/ec2sun/
README' file.

File Layout


OpenESB v3

Binary Runtime Files

/usr/fuji

Configuration Files

/usr/fuji/conf


To start the OpenESB v3 instance:

cd /usr/fuji

java -jar ./bin/felix.jar


The instance uses up 3 ports:

  • 1600 - Apache Derby

  • 8699 - RMI/JRMP Port

  • 8080 - Http Port used by the OSGi/Felix Http Service

The web application should be accessible from:

http://<DNS host name associated with the instance>:8080/fuji/editor



Documentation:

Support

OpenSolaris AMI License for Amazon EC2
http://www.sun.com/third-party/global/amazon/license/ami/

OpenSolaris is a trademark or registered trademark of Sun Microsystems, Inc. or its subsidiaries in the US and other countries.


Sunday Jun 14, 2009

Wordpress AMI now available in Europe

We are very happy to broaden the availability of the latest Wordpress AMI on Amazon EC2 in the European Region. This AMI is based on the OpenSolaris 2008.11 base AMI and does not need registration.

Following are the details of this new AMI:

Wordpress 32-bit AMI:

ami-ffa78f8b aki-661c3412 / ari-601c3414

Manifest: WordPress_2008.11_32_1.0.img.manifest.xml

To run this AMI in Europe, change the following environment variables before launching the AMI:

EC2_URL="https://eu-west-1.ec2.amazonaws.com"
LOCATION="EU"

The other env variables remain the same.

NOTE:  a unique <your-keypair-name> must be generated for each region before launching an AMI.(Use ec2-add-keypair <name> > keypairfile after setting the above env variables).

About

Information about Solaris and OpenSolaris on Amazon Web Services (AWS) EC2. Look here for the latest information on the program and any late breaking information on (Open)Solaris on EC2.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today