Auf der Go DevOps 2019 am 2. und 3. September in Berlin dreht sich alles um Infrastruktur, Security und kulturelle Aspekte von DevOps. In drei laufenden Streams wird viel Know-how geboten, um allerlei Herausforderungen im IT-Umfeld bewältigen zu können. Beugen Sie verzögerten Projekten oder verpassten Deadlines vor und tauschen Sie sich mit Gleichgesinnten aus. Melden Sie sich jetzt an: GoDevOps
In this blogpost about the Oracle Cloud Infrastructure I will describe how to administer user, groups etc. Refer to the first blogpost Getting started with the Oracle Cloud Infrastructure for explain the first steps with the OCI.
A user in the OCI can access, create and administer cloud services. The permissions for users can be consolidated in groups as policies. Policies define the allowed actions for group members and in which department.
A Compartment is logical group of resources that represents an organizational unit. Resources will be created in a compartment. You cannot move the cloud resources from one compartment into another…Weiterlesen „Oracle OCI : Administer User, Groups, Compartments in the Oracle Cloud Infrastructure“
Every cloud administrator wants to administer and monitor their cloud resources from a central location. The Cloud (OCI) Command-Line interface OCI CLI enables this. In this blog post I will describe the installation and configuration of the Cloud CLI on an Linux Server with OS Oracle Enterprise Linux.
To install and use the Cloud CLI you must have the following data:
- OCI User: Users for connecting to cloud services
- A SSH Keypair used for signing API requests, with the public key uploaded to Oracle OCI
- Python version 2.7.5 or 3.5 or later
I’m about to start a series of blog posts about Oracle Cloud Infrastructure (OCI). In this Blogpost, I will describe following topics:
- How to sign-in into the Cloud
- The first steps in the OCI
Sign-In in to the Cloud Console and administer the Cloud Account
To sign in to the Console, you need the following data:
- Tenant, User name and Password
- URL for the Cloud Console: in my case: https://console.eu-frankfurt-1.oraclecloud.com
- Any browser from the supported browsers list: I will use the Firefox
You will receive the email with access data as soon as your cloud administrator has created a user for you in the cloud.
Connect to the Cloud Console:Weiterlesen „Getting started with the Oracle Cloud Infrastructure“
This blog entry is the third and last part of the series „Create APEX in AWS“. Here I describe the installation and configuration of Apache Tomcat and the deployment of the ORDS application in Tomcat. Later I will explain the installation of the Webserver Nginx and configure it to access APEX via Apache Tomcat and ORDS.
Installation Apache Tomcat on the EC2 Container
As root: Download and extract the software:
This is the second part of my blog series about the installation and configuration an APEX database in the Amazon Cloud. Refer to following posts for the explanation of the whole solution:
- Create Oracle APEX Environment in the Amazon Cloud with RDS: Part 1 – Overview
- Part 3: Configure APEX with Oracle Rest Data Service (ORDS) in the EC2 Container
- Part 4: Configure APEX with ORDS, Apache-Tomcat und Nginx
Create the Virtual Private Cloud (Network) in AWS
At first, I will create my customer network in AWS.
In the AWS Console navigate to VPC and click on „Create VPC“. Specify the IPv4 IP Range (CIDR Block) and try „Create“:
In this article I will describe the installation of APEX Environment in Amazon Web Service (AWS).
The whole environment includes following components:
- AWS RDS: Oracle Database with activated APEX
- VM (EC2 Container) with:
- Oracle Rest Data Service (ORDS)
- Apache Tomcat for the Hosting of the ORDS
- Nginx: http Server
The major challenge is to install APEX without SYSDBA privilege, because the Oracle Database in the RDS is Vendor-Managed. Users cannot access the OS and do not have the database DBA role.
Blue Print of the APEX environment in the AWS:
In my next Posts I will cover the following topics: