Cloud9 Development Environments - Report Sample

Introduction

Creating AWS in the cloud9 environment involves launching the Amazon Elastic Compute Cloud (Amazon EC2) and connecting the creating instance to the environment (Rahman, 2019). Therefore, the following steps were adopted.

Is your time best spent reading someone else’s essay? Get a 100% original essay FROM A CERTIFIED WRITER!

Save 25%

The first step is to create a cloud environment for provisioning. The environment variable takes the name-value instance, the description, and the client request token. On the other hand, connection –type value and tags are specified to make the created environment distinct from different cloud environments (Rahman, 2019).

Description

Name input in the form of the string represents the environment to be created. It is visible in all AWS IAM users using a similar account. The description attribute describes the domain being created. Therefore, we can create the AWS cloud in the following manner.

To verify that the stack is provisioned, go back to the AWS console, select the "VPC service" from the "Networking & content" delivery section, and click on the "Your VPCs" label on the left.

Cloud APIs

Cloud Application Programming Interface (Cloud API) refers to a particular API type, which allows the development of services and applications for cloud software and hardware platforms provisioning (Nelson-Smith, 2013). Therefore, administrators can integrate multiple applications and other workloads in the cloud computing environment through Cloud APIs. With the cloud environment's growing complexity, various developments of cloud-based software or integrated development are required. Therefore, cloud API allows for cross-platform and cloud experience compatibility across multiple developers, forming a cloud API environment. The administrators can integrate various workloads and applications through cloud API.

In cloud computing, four distinct areas require integration with other cloud providers and other related platforms such as:

• Platform as a service (Service-level): PaaS APIs' function is to provide functionality and access for a cloud environment, primarily through integrating essential aspects such as storage components, portals, messaging systems, and databases.
• Software as a service (SaaS): Software as a service APIs are crucial at the application level since they help connect the application layer with the related IT infrastructure. For the case of Ballot Online, it needs to integrate the ERP and CRM software application extension for its environment to the cloud.
• Infrastructure as a Service (IaaS): the API operates at the Infrastructure level, hence controlling specific cloud resources and determining their distribution. Ballot Online will require rapid cloud resource provisioning and de-provisioning. Consequently, other areas of applications would be in workload (VM) and network configuration application areas.

Cross Platforms

Ballot Online aims to provide an online voting solution to global clients. Hence, it requires a robust system that allows multiple developers from different geographical positions to collaborate in attaining customized client software needs.

Cross-platform and cloud provider APIs: the current computing environments uses multiple platforms that require more excellent compatibility. Consequently, most cloud service providers consider offering HTTPS and HTTP API integration allowing greater versatility in the cloud for their customers(Rahman, 2019). Therefore, cloud tenant's accessed their resources from different cloud providers apart from their primary providers. Ballot Online Company will need to provide the ability to access information from different cloud providers to achieve data reliability and accessibility.

Ballot Online

Ballot Online should consider using APIs such as WS Cloud Formation to define the company's AWS infrastructure in YAML and JSON files, which can be managed within the source code repository similarly to other forms of Code (Jerry, 2016). Implementing the WS Cloud Formation will be easier to code reviews and requests from the cloud (Mathew, 2014). Once everything is functioning correctly, the various files can automate multiple processes that help in infrastructure changes deployment.

Conclusion

AWS Cloud formation is the foundation on which CDK is built using its engine in AWS resource provisioning. Instead of adopting declarative languages such as YAML or Jason in defining the cloud infrastructure. CDK helps in achieving the ability to use standard or most preferred programming languages in the design. Therefore, robust yet straightforward scripting languages such as Python can be used instead.

References

Jerry, N. P. (2016). AWS Command Line Interface: Easy Guide on AWS CLI. CreateSpace Independent Publishing Platform.
https://dl.acm.org/citation.cfm?id=3133387

Mathew, S. (2014). Overview of amazon web services. Amazon Whitepapers. https://www.sysfore.com/Assets/PDF/aws-overview.pdf

Nelson-Smith, S. (2013). Test-Driven Infrastructure with Chef: Bring Behavior-Driven Development to Infrastructure as Code. " O'Reilly Media, Inc.".
https://books.google.com/books?hl=en&lr=&id=fT1PAQAAQBAJ&oi=fnd&pg=PR2&dq=infrastructure+as+code+security&ots=QYh4LeN3Ht&sig=6edWP8YSKcQRj2WavU4l5VKU1I4

Rahman, A. (2019). A systematic mapping study of Infrastructure as code research. Information and Software Technology, 108, 65-77.
https://www.sciencedirect.com/science/article/pii/S0950584918302507

Rahman, A. (2019, May). The seven sins: security smells in Infrastructure as code scripts. In 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) (pp. 164-175). IEEE. https://ieeexplore.ieee.org/abstract/document/8812041/?casa_token=zwKnCyrJbkgAAAAA:Cv7rbkSf5IE3zhS2CoGBlhRV4w4A2mq69arXkLApKG7-XkbKZm7TvSeH57j2UZfpXkYNcVieJOuhOA.